SoylentNews is people
SoylentNews
from the broken-fixes-make-PCs-into-bricks dept.
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.
If you don't already have the 23 September 2019 (or later) SHA-2 update installed, you will probably be having a rather ungood day.
(Score: 2, Informative) by Anonymous Coward on Tuesday February 18 2020, @02:42PM
for some use cases i can understand people clinging to m$ products.
however for people doing "document processing" i would like to offer the insight that the main component of your computer is your harddisk (or ssd), that is STORAGE.
what m$ tries to do s bind your storage to their os. it is true that you can remove a hdd with windblows and all your data/documents and connect it to another computer. but does this other computer really need to run windows?
the answer is no!
chances are also that if your windows computer fails but your storage is fine connecting it to a newly bought computer will make the installed windblows operating system have a fit once it notices the new (non lightning struck) hardware.
so if you're not a special use case, stop letting m$ abuse you by binding their os to your storage.
with linux, if your computer hardware fails but your storage is okay, connecting it to newly bought hardware will 99% have linux boot up from the old intact storage device!