Microsoft RE-BORKS Windows 7 patch after reboot loop horror Reports are emerging that a twice-issued Microsoft Windows 7 patch is still causing pain for users, with some claiming the fix is triggering continuous reboots. The patch was first issued as KB2949927 and withdrawn in October due to system faults, before being re-released this week as KB3033929. Sporadic reports across …
Far easier just to turn Windows automatic updates off altogether, this way I get to keep 100% compatibility without drama. Don't even have to think about Wine.
Better still, I uninstall the Windows automatic updates service, this way other sneaky MS programs can't silently turn it back on, as they're so often wont to do.
I've learned the hard way many years ago never to turn on Windows (or even Linux) automatic updates, as things change, often strangely and without notice. And in Windows' case, the all-to-regular BSODs were somewhat distracting.
BTW, I do use Linux regularly for many purposes but not as my default desktop machine. For some reason, Linux is missing a key component, Win32/64 API compatibility! Quick, quick, Linux devotees, reach for the down-vote.
I just consider it a shame that more vendors don't produce Linux versions of their software. That way I wouldn't need a Win32 API on my machine.
As for the update in the article, it appears to be installed on the machine here (a Dell) which has successfully rebooted at least twice since the update was installed, so Im clearly missing out on the fun and excitement too.
And please don't feel left out. In the months to come, your turn will likely follow.
If it happens to me, I'll just boot 8.1 and restore last night's back-up. However, given how none of the other duff patches have affected me and how I've had zero problems with it since it was in beta, beyond the inadvisability of chancing Sod's Law I feel confident that I never will.
Come to think of it, of the many operating systems I've run over the years, I think Windows 7 is the only one that's been trouble-free. I suppose, in the context of this thread, it would be tactless to suggest the OS deserves a testimonial dinner or something...
Well, yesterday my dentist was gnashing HIS teeth... After patch Tuesday, his win7/32-bit went BSOD and looping. I don't know his config, but multiboot is probably not involved. Luckily he still could patch my teeth without it. He's back to paper records for a while.
It hasn't (yet) cause any problems on my Dell Win7/64 machines. But then thanks to El Reg, I did install all the other updates first and then did a separate update run just for this update.
Mind you the update isn't small at 43.8MB...
Wouldn't surprise me if it turns out the cause of the problems are due this update upsetting some unknown rootkit, just like the update to NTFS.SYS a few years back caused some systems to unexpectedly BSOD...
KB3035131 - hanging an HP workstation...That must be something else then, as the patch in question here is KB3033929, which fails for me on a dual-boot Win7/Linux system with an 80004005 error.
The system does recover, after a few reboots to remove the failing patch - which then shows up in Windows Update as needing to be installed. Fortunately I have the system set to do updates when I request - so I've hidden it (as I had to hide the previous one).
The page you are looking for may have a new location, or is no longer available.
http://support2.microsoft.com/en/kb/3033929
"Check for updates but let me choose whether to download and install them."
Is the sensible way to configure windows update.
Is in my list and is now unticked, thanks for the heads up Reg
""Check for updates but let me choose whether to download and install them."
Is the sensible way to configure windows update."
Well yes, and I could have sworn that my various 3 Win7 boxes (mix of Win7/.32 and Win7/64, Home Premium and Pro, at least one multiboot) were configured that way.
Somehow by this Tuesday, they weren't configured that way any more, they'd downgraded to the MS-recommended setttings of "please test our patches for us".
Consequently the patches were auto installed.
One system failed and auto-recovered. Two survived with no visible damage so far.
I guess I'm supposed to consider myself lucky.
Not ideal.
Not for the first time, I actually had a problem with this latest group of updates. Windows 7 Pro 32bit.
Downloaded and installed then asked to agree a re-boot. Clicked the OK - the system closed down but did not re-boot.
Tried a re-start, nothing. Unplugged everything and started to look for my back up boot CD. Switched everything back on and thankfully it all booted up OK and installed the updates.
In the end, a minor glitch which gave me a virtual heart attack - Reminder = must retain my sense of humour!
Ah, yes, but maybe (unlike me) you do not dual boot using GRUB.
It has tried to update three times since Thursday... failed, but after further restarts has at least recovered to boot pre-update.. (vital, as I am only using Win7 to play Elite:Dangerous ).
I have deselected the offending update in Windows Update so as not to disturb my gaming.... (never a happy chappie as far as Microsoft are concerned...)
I take no chances with M$ overwriting boot things. If Windoze has to boot it is in a $VIRTUAL machine and does not see a real disk (got to love fast SSDs!!!!).
I do get nostalgic for "blue screens of death". In Linux we typically get the "consoles of chaos" or the "titanic hits the iceberg of keyboard input loss" which leaves a much prettier Xorg display.....
All of course the followed by the "button of power..."
P.
No, I don't dual boot. Why would I want to torture myself like that?
IF I need Windows, I use the work laptop and then, I swap out the HDD with a plain Jane install of 'dows on it because of all the restrictions those tw@'s put on tier implementation.
Otherwise, it's ran virtual.
The timer vanished on Grub after this patch was installed. Re-installing grub fixed it, but that was weird ...
Hmmm...my grub timer disappeared a few weeks back. It confused the hell out of my wife, as in my case it just sat there displaying the grub options with no time-out at all. I hadn't considered the possibility of MS fiddling with it. But if they did fiddle with booting in some way I'd have expected more of a difference than the grub time-out changing.
Ditto, KB3033929 also messed up my Mum's HP Pavilion (hangs on start-up with a black screen and flashing cursor in top left). Luckily was in the right half of the country to be able to visit, start the laptop in safe mode, and remove this update. Also had to go back on win update once fixed, and set it to hide the update forever more . . .
Installed both KB2949927 and KB3033929 with No problems on a Dell Vostro with Win 7 Pro.
After further reading on both KB's I uninstalled KB2949927, again No problems so far.
I thought that KB3033929 superseded KB2949927 and would have removed it when installing the newer update but, it didn't.
So, five days later and the problem patch is still there. My gaming rig is doing the "Failure configuring Windows updates. Reverting changes." thing if KB3033929 is selected. I've just hidden the update for now, I'll take my chances. I can't believe Microsoft haven't pulled this update yet, given the number of reports. WTF, Microsoft!
IE will not start, and the shortcut is gone. Some might find this a feature. Many, many error messages with reports the following missing files.
api-ms-win-downlevel-user32-l1-1-0.dll
api-ms-win-downlevel-ole32-l1-1-0.dll
System Restore works until the patch is re-installed and then
reports the following missing files.
api-ms-win-downlevel-user32-l1-1-0.dll
api-ms-win-downlevel-ole32-l1-1-0.dll
over and over and over again.
Looks like a re-image is the only solution I have.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
