Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Monday October 03 2016, @02:52AM   Printer-friendly
from the oops,-I've-done-it-again dept.

Microsoft "extremely careless"

I have a dual-boot machine with Win10 on one partition. This morning, Windows installed a large update with the comment "your machine will restart several times". Sure enough, the update took forever, and afterwards...there's only Windows 10 left.

I haven't yet gone spelunking with a LiveCD, but Win10 updates have been known to nuke entire partitions, not just the bootloader. Time will tell...

For what it's worth, the Windows update history shows: KB 3176937, 3176935, and 3193494. This would appear to be a group of updates that lead to "Windows 10 version 1607".

Microsoft Delivers Another Broken Windows 10 Update

This week, Microsoft pushed out another cumulative update and reports of installation problems are widespread. While I don't know how many users are impacted, based on comments sent to me, it's certainly widespread enough that this is well beyond an isolated issue.

The update that is causing the problem, KB3194496, is not installing correctly for users. The update, when it does fail, is causing some machines to restart, often multiple times, as Windows 10 attempts to remove the failed update. Worse, after a restart, the file will attempt to install again resulting in the loop of failed install, reboot, re-install and failure again.

Some users have reported that the cumulative update did install correctly on the second or third attempt while others have said that it fails every time.

[...] Microsoft is pushing the idea that you should always patch your machine on the day the update is released as they often release security patches that fix vulnerabilities. But, until the company can get a handle on their quality control issues, such as the Anniversary update breaking millions of webcams, it feels like every time you run Windows update you are rolling the dice.

Some have found a solution to their problem here.


Original Submission #1Original Submission #2

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Monday October 03 2016, @08:32AM

    by Anonymous Coward on Monday October 03 2016, @08:32AM (#409314)

    No, I tested them unfortunately. Yes that is strictly windows games. My wife *LIKES* her games. She wanted a new computer *AND* her games which was lots of installing off of CDs and reinstalling lots of Steam and Bigfish which simplified installing a good chunk of them. Not much GoG though. I tested them as I need to find ones that are broke and I put them to the side to find ways to fix later. Fortunately the list of 'to be fixed' is pretty small. No new real breakages that I didnt know about already (about 20). They didnt run under vista or win7 either so not too surprising. But do work 'ok' under XP. Only one so far out of the whole set that only works in 98. And yes installing 1500+ games *sucks* *ass*. Been meaning to crack them all properly and dig out the registry settings to make them all portable and easy to install. Oh and you may be thinking 'she does not play all of that'. Yes she does. She has many games with well over 1000+ hours logged.

    If I added in DOSBox it would be well over 20k. Long live eXo and archive.org! :) My personal collection of DOS games is about 200. I dont mess much with them anymore. As you pointed out the conversion from 16->64 killed a lot of those. But they live on through DOSBox and Scummvm.

    On my personal computer I have about 450ish or so steam games. Out of those I know 5 were broke but I have not tested all of them yet the rest are unknown. That seemed to be a genuine MS issue with full screen and directx and was fixed about 2 months after initial release. I also had some issues with nvidia. Clean reinstall of the drivers fixed that. That took a few months of debugging to find the issue. The nvidia installer confused two driver installs together.

    One of my boxes I am planning on removing windows altogether. It does not need it and would startup a lot faster without it. I figure I could squeeze another 10-15 seconds out of the startup with linux instead of windows. Which is more important for that use case.

    Why yes, my wife and I spend too much money on games :) But 37 years of collecting games and a decent amount of disposable income grants you a bit of freedom to buy frivolities.