01-04-2018, 02:16 PM
01-04-2018, 02:30 PM
This is a hardware bug and affects Intel CPU so AMD are safe. Microsoft have released patch to try and fix the issue. Hardware bugs are very hard to fix.
Here are some articles you can readÂ
Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs
How to protect yourself from Meltdown and Spectre CPU flaws
Serious Intel CPU design flaw require's a Windows patch
Here are some articles you can readÂ
Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs
How to protect yourself from Meltdown and Spectre CPU flaws
Serious Intel CPU design flaw require's a Windows patch
01-04-2018, 03:56 PM
01-04-2018, 10:38 PM
i have downloaded on: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056897
and see if it's fix or not
https://forum.avast.com/index.php?topic=212648.msg1439270#msg1439270
https://speccy.piriform.com/results/yYexxJ4N8I7jbWqwDxUa3mb
[attachment=3250]
i have clean reinstall windows 7 on december 25 due to 3rd party themes
and see if it's fix or not
https://forum.avast.com/index.php?topic=212648.msg1439270#msg1439270
https://speccy.piriform.com/results/yYexxJ4N8I7jbWqwDxUa3mb
[attachment=3250]
i have clean reinstall windows 7 on december 25 due to 3rd party themes
01-05-2018, 03:39 PM
Code:
if (c->x86_vendor != X86_VENDOR_AMD)
setup_force_cpu_bug(X86_BUG_CPU_INSECURE);
01-05-2018, 03:48 PM
do i need to type in command prompt guiltyspark?
01-05-2018, 03:51 PM
(01-05-2018, 03:48 PM)f23948 Wrote: [ -> ]do i need to type in command prompt guiltyspark?
No it's just 'tongue n cheek' from AMD.
01-05-2018, 04:00 PM
oh lol
01-05-2018, 09:29 PM
when i type in windows powershell as administrator, it gives me error
https://www.bleepingcomputer.com/news/microsoft/how-to-check-and-update-windows-systems-for-the-meltdown-and-spectre-cpu-flaws/
[attachment=3252]
https://www.bleepingcomputer.com/news/microsoft/how-to-check-and-update-windows-systems-for-the-meltdown-and-spectre-cpu-flaws/
[attachment=3252]
01-06-2018, 12:20 AM
Hi f23948,
First, type in the following code into PowerShell and press Enter (This will change the policy, disabling restricted mode, allowing us access to install this module)
When prompted for any action, type "Y" and press Enter. For this command, you will get prompted at least twice.
Once that has finished, type in the next command and press enter to install the module:
You should be prompted once, again, type "Y" and press Enter
Once that has finished, you can enter this command to check if you have been affected by this bug:
If the command has worked, you should get something like this, displaying information:
[attachment=3253]
[b Image ]Source:[/b]
https://www.bleepstatic.com/images/news/u/986406/Microsoft/Windows10/Meltdown+Spectre-Powershell.png
Remember after you have finished sorting this out, type the following command to re-enable the restricted mode, in order to keep your system safe:
Hope this helps
First, type in the following code into PowerShell and press Enter (This will change the policy, disabling restricted mode, allowing us access to install this module)
Code:
Set-ExecutionPolicy Bypass
When prompted for any action, type "Y" and press Enter. For this command, you will get prompted at least twice.
Once that has finished, type in the next command and press enter to install the module:
Code:
Install-Module SpeculationControl
You should be prompted once, again, type "Y" and press Enter
Once that has finished, you can enter this command to check if you have been affected by this bug:
Code:
Get-SpeculationControlSettings
If the command has worked, you should get something like this, displaying information:
[attachment=3253]
[b Image ]Source:[/b]
https://www.bleepstatic.com/images/news/u/986406/Microsoft/Windows10/Meltdown+Spectre-Powershell.png
Remember after you have finished sorting this out, type the following command to re-enable the restricted mode, in order to keep your system safe:
Code:
Set-ExecutionPolicy Restricted
Hope this helps