Skip to comments.Microsoft ups the ante with fix-fixing patch that leaves some Windows Server 2008 machines unable to boot
Posted on 02/11/2020 7:18:23 AM PST by dayglored
She applied the fix to fix the fix... I don't know why she did the apply. Perhaps it'll die
Like a needy ex-partner that just won't let go, Microsoft's legacy OSes continue to cling to the Windows behemoth's ankles. Windows Server 2008 and Windows 7 have once again been bashed with the borkage bat.
Users are reporting that the fix to fix the fix that broke the desktop wallpaper in Windows Server 2008 R2 and Windows 7 has left systems unbootable after an apparent boot file deletion.
The fix-fixing fix (KB4539602) was unleashed at the end of last week, and some administrators have kicked off a deployment.
It has not gone well.
One Redditor remarked that 18 2008 R2 servers had fallen victim, while another reported 30 Windows 7 computers were refusing to boot after an install.
While Microsoft's support article for KB4539602 insists the company is "currently not aware of any issues that affect this update" it does suggest that users check out the prerequisites before going ahead with it.
In a nutshell, users must have the 23 September 2019 (or later) SHA-2 update installed as well as the servicing stack update from 12 March 2019 or later, before they unleash the fix. And naturally you'll need to reboot after these updates. Because, hey, everyone loves rebooting a server, right?
We asked Microsoft why the update process allowed the patch to be installed without automatically checking the documented prerequisites, but have yet to receive a response. We've also asked if a further fix will be issued or formal workaround published.
We'll update this article should the company respond.
In the meantime, if you need to install this update then please take a careful look at the support documentation and make sure those prerequisites are in place before hitting the Go button.
And maybe, just maybe, it might be time to put those old beige boxes out to pasture once and for all. Free support ended last month and Microsoft clearly would like customers to move on. ®
Or maybe it's the other way -- she's the one with the clingy ex-partner. Opinions?
Par for the course with Microcrap!
I will need more photographic evidence before offering my opinion.
I thought MS said they will quit updating Win7.
I’m still waiting.
A more interesting question is who will be stupid enough to install it. It keeps getting worse with each irritation, er, iteration. With the next one, when you install it, your firstborn will probably clutch at his throat and keel over dead.
They didn’t break all the installs yet.
Its just a washed up carcass on a stinky beach. No one cares about, or uses these defunct products from that has-been company anymore.
If it ain't broke, don't fix it, except in this case, if it ain't broke, break it. :^) The W7 Pro machines we use (and as an employee of a pretty large outfit, I've got zero to say about what we use around there) have started to run noticably slower during the past month or so.
Alas, that carcass is still in widespread use by all sorts of businesses large and small who can't afford (or are too lazy) to migrate their applications and databases to Server 2016 or 2019, because of the radical differences.
Server 2008 was the "Win7 server"; 2012 was Win8 server; 2016 was Win10 server. 2019 is Win10 server on steriods.
It's not a seamless migration. Lots of things simply don't work, and must be re-written.
"No one cares about "? Hardly. You'd be amazed and horrified.
I have a laptop on which one Windows Update broke the Updater App, and so it stopped updating 2 years ago. How do you fix the Updater App when you need the Updater App to update updates to fix the Updater App?
You're not alone. Something's going on.
[Dayglored puts on his tinfoil hat...]
You have to wonder if some Win7 Windows Update from months ago included a "timebomb" that would start the disintegration of performance after Jan 14, 2020.
Of course my first question (beyond “who trusts Microsoft?”) is who would apply patches to their entire farm without patch testing first?
Yeah, I agree, but I was runnin' low on foil. :^) Nothin' sells like planned obsolescence.
It depends. If you have 100 servers, it only makes sense to test it on a select few (non-production) first. What about if you have 5 servers and they're all production critical (yeah, that's another, different problem)?
Sure would be nice if one could trust the supplier.
Turn off automatic updates and only install the bare minimum needed to properly run specific programs/games.
Still running Win 2008 server?
Irresponsible. The owners of the system, not the admin.
Company ownership must give them an ultimatum. Upgrade to current OS (platform and application/DB) in 90 days or you’re fired.
If you’re at a publicly traded company, it should be part of their quarterly and annual public disclosure.
The company’s business operations are at risk.
I don’t have the statistics right at hand, but I wonder if the percentage of Server 2008 still in use is similar to the percentage of the corresponding client (Windows 7) — at around 25%.
It has to be less on the server side.
There are a lot of private individuals on Win7 that skew those numbers.
2008 is out of support.
And it’s now, by definition, a security risk to the entire enterprise.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.