KitGuru KitGuru.net – Tech News | Hardware News | Hardware Reviews | IOS | Mobile | Gaming | Graphics Cards
Following on from last week's news of a kernel bug affecting x86 systems, OS makers began preparing patches. Microsoft's Windows 10 patch to mitigate this issue was due to arrive today but it seems that it caused issues with AMD systems. As a result, the patch is being halted on Windows systems running AMD processors.
This particular patch targets the Meltdown and Spectre security bugs that rose to prominence last week. After the patch began rolling out, Microsoft's support forums were hit with many complaints from AMD system users saying that their PC would no longer boot. In a statement given to The Verge, a Microsoft spokesperson explained the situation: “Microsoft has reports of customers with some AMD devices getting into an unbootable state after installing recent Windows operating system security updates. After investigating, Microsoft has determined that some AMD chipsets do not conform to the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown.”
Microsoft will be preventing AMD PCs from receiving the update for now. If you own an AMD system and Windows 10 is telling you to update, perhaps hold off on that for another week or so, otherwise your system may enter an unbootable state. If you do happen to install the update, then Microsoft's support page has a fix that should help.
KitGuru Says: AMD's CPUs aren't quite as vulnerable to these bugs as it is, but installing security patches is always a good idea to remain secure. That said, in this instance, AMD PC owners should hold off while Microsoft addresses the boot failing issue.
How lucky we are able to hold-off on updates in Windows.
Oh wait….
LOLOLOL https://uploads.disquscdn.com/images/36bf9cdbf645140b000151b34594ffa3635d70db354fa1378f283570c4f5cc3b.jpg
This shit installed itself this morning in the office and it was waiting for restart to apply, when I first read the news… I called in full panic in the local MS department for help because this is my workstation and my deadlines can’t wait for a couple of hours, let alone wait for me to reinstall windows…
At least they have very good customer service and the guy in the other side of the line stopped the upgrade from happening and showed me how to stop future updates myself from applying if I want to.
You can, go to this page and look around the middle for the link to the tool to hide or stop updates you want.
I didn’t knew it either, the guy in MS support told me about it.
https://support.microsoft.com/en-us/help/3183922/how-to-temporarily-prevent-a-windows-update-from-reinstalling-in-windo
Except you need physical access to exploit AMD systems. The usual Microsoft bollocks. It might be an idea to test these things on actual hardware, eh? It isn’t that crucial an update for AMD users, so it is not as if it is needed lickety-spit. Numpties.
you need physical access to exploit Intel systems as well, can be through a virus, click on some browser pop-up, or some malicious extension in the browser, there are many ways but the threat can not magically enter the pc, is just like any other threat, needs interaction with the user
what a mess this all is. all this money you pay for this stuff. and no one will be held accountable.
you can delay updates but it involves digging deep into the services n stuff. I get notices updates are available but they don’t install till I tell them. I usually image my drive before any big updates because they can be pretty nasty. Had one kill my samsong EVO SSD. Double sucks cuz when you RMA it they send you a refurbished one.
https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10
injecting java script in to web browsers don’t need physical access wo0rks great
My server pc with windows 10 updated and would not get past blue windows logo after reboot. Literally stripped pc until giving up and installing Windows 7. Now pc boots just fine. Shame on you Microsoft