Monday, January 29th 2018

Microsoft Issues Update to Rollback Intel Spectre, Meltdown Problematic Patches

Multiple reports pegged some issues on Intel's rapid-fire, microcode and software response towards addressing the Spectre and Meltdown vulnerabilities, with Intel themselves coming forward, admitting to the problems' existence, and urging users not to perform said updates. However, Intel's press release wasn't very clear on whether or not users would be able to rollback changes in order to recover their machines' stability. Microsoft has taken the matter into its own hands, via an out of band update for Windows, KB4078130, that specifically disables only the mitigation against CVE-2017-5715 - "Branch target injection vulnerability."

In Microsoft's testing, this particular update is the one that the company has found to be associated the most with stability issues on host machines, and their out of band update seems to mitigate these completely. Microsoft is also adding the possibility for users to either disable or enable the troublesome mitigation themselves, manually, via registry changes. Microsoft seems to have taken the job of cleaning house on themselves, after Intel's apparent hasty move to restore security to systems based on their CPUs.
Source: Microsoft Support
Add your own comment

15 Comments on Microsoft Issues Update to Rollback Intel Spectre, Meltdown Problematic Patches

#1
Slizzo
One of their updates had started to prevent my machine from booting properly. I had been ignoring it as long as I can.

Looks like this update was the one that was at issue. Thanks Microsoft...
Posted on Reply
#2
the54thvoid
Tried to install Asus AI suite (for fan control). The recent update borked it. Tried new version and bloody hell, thought I'd lost my PC to reboot hell.
Talk about knock on effects. Currently running Prime after having to reset bios and retune. Thanks MS or AMD or whoever.
Posted on Reply
#3
raptori
That trash update destroyed my windows and I had to reset it and turn-off the damn windows update which always degraded PC performance , I used to delay windows update for as long as I can for the sake of stability and my PC was always clean and stable , guess I'm back to main updates only as it is always the right way to go for me.
Posted on Reply
#4
Vayra86
In some weird way I always seem to avoid all these problems while letting auto updating do its thing.

Perhaps its my great looks... weird stuff
Posted on Reply
#5
INSTG8R
the54thvoid said:
Tried to install Asus AI suite (for fan control). The recent update borked it. Tried new version and bloody hell, thought I'd lost my PC to reboot hell.
Talk about knock on effects. Currently running Prime after having to reset bios and retune. Thanks MS or AMD or whoever.
This is the reason I have been blocking it. I can't use the new version it doesn't even see my sensors so useless for fan control...
Posted on Reply
#6
Tomgang
I dit not get in trouble, but thats is properly because i have disable windows update for now and awaiting those meldown/spectra problems to be solved.

Back in december 2017 windows update completly fucked up my install so had to waste two freaking days of my vacation to get it up and run again. So take no chances this time around. But maybe its time to update now with this fix.
Posted on Reply
#7
lemonadesoda
And this is why I hate W10 forced updates. For those who have successfully disabled automatic updates to manual, I would be grateful for a good link to a tutorial. My attempts have not been so successful: either updates and forced reboots are still occurring, on one machine, OR, Winupdate is so disabled that I can't even manually update anymore. MS really farked up the update system. Can we class action MS for forcing failure on to us without our agreement?
Posted on Reply
#8
Tomgang
lemonadesoda said:
And this is why I hate W10 forced updates. For those who have successfully disabled automatic updates to manual, I would be grateful for a good link to a tutorial. My attempts have not been so successful: either updates and forced reboots are still occurring, on one machine, OR, Winupdate is so disabled that I can't even manually update anymore. MS really farked up the update system. Can we class action MS for forcing failure on to us without our agreement?
To do it right. In Search beside windows start button type in "services" and klik it/open it. scroll down to windows update (it shut be down the buttom). dobble klik and in the first fan there shut be something called starttype and klik that fan next to it, you shut have 3 or 4 different to chose from: Automatic (delay start), automatic, manuel or deactivated. You can properly take your self from here. Manuel you can chose update our self but has to be done with in 3 day after update become accessible cause else windows update will still do it automatic. So I deactivated until I am ready to install new updates and you can off cause set it to manuel when you are ready to update and then done disable it again.

It shut look something like this.
Posted on Reply
#9
raptori
lemonadesoda said:
And this is why I hate W10 forced updates. For those who have successfully disabled automatic updates to manual, I would be grateful for a good link to a tutorial. My attempts have not been so successful: either updates and forced reboots are still occurring, on one machine, OR, Winupdate is so disabled that I can't even manually update anymore. MS really farked up the update system. Can we class action MS for forcing failure on to us without our agreement?
I found that disabling the service doesn't cut it all the way as recently MS do enable the update service even after you disable it , so what I did is limit the download bandwidth to almost nothing :

press on your keyboard : windows + R and type "gpedit.msc" to run Local Group Policy editor ( assuming you have window 10 pro not Home edition)

From the left panel select and open (administrative templates) folder under (Computer Configuration ) then (Windows components ) then (Delivery Optimization ).



From the right panel Double-click on (Maximum Download Bandwidth (in KB/s)) , then select enable then below put the speed to 1 KB/s then restart and good luck to windows update trying to update with 1KB/s.



To reset back to default select (Not Configured ) .

On windows 10 build 1709 and newer you have the option to assign your connection as "metered" that also will reduce the updates to minimum if you don't want to use Local Group Policy editor .
Posted on Reply
#10
erixx
After the first patches (guessing, includes MS, Intel and BIOS updates) I had a couple of days of BSOD. More updates came and I am perfectyly fine ATM. So... I am not liking this direction things are taking....
Posted on Reply
#11
TheDeeGee
No issues here, but i'm still on 1703.
Posted on Reply
#12
Red_Machine
Does anyone know when this update was/is released? I haven't had anything since the 11th.
Posted on Reply
#14
erixx
I clicked on your link and found this is "For..... Windows 10 LTSB, etc." Long Term Small Business", wow another flavour!

I am on Fast Ring build 17083, and have not gotten this
Posted on Reply
#15
R0H1T
erixx said:
I clicked on your link and found this is "For..... Windows 10 LTSB, etc." Long Term Small Business", wow another flavour!

I am on Fast Ring build 17083, and have not gotten this
LTSB is Long Term Servicing Branch not another flavor of Windows, it's pretty much MS' equivalent of esr FF from Mozilla.
Posted on Reply
Add your own comment