SoylentNews is people
SoylentNews
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.
(Score: 2) by Aiwendil on Monday October 03 2016, @07:51AM
Just a crazy idea
But if you have any OCR-capable screenreader, will it pick up the fonts of BIOS when feed images of it via a webcam?
(Hitting the magic key to get to options normally is done from memory for sighted as well - due to too short delay (tends to be that the POST-beep is when to hit the key))
(Score: 1) by ShadowSystems on Monday October 03 2016, @03:34PM
First, I don't have a webcam. I know they're useful for stuff like Skype & such, but as a blind person I can't see (metaphoricly nor physicly) the use.
It's not like I can see whom I'm talking to anyway, so why should I let them see me?
Besides, that means wearing clothes... pants? BAH!
=-D
Second, since there's no pre-OS-load Screen Reader Environment (SRE), that means there isn't a SRE available to interact with the webcam during boot.
I need the OS to load & give me the SRE so I can know if the webcam was able to OCR the screen during the boot menu.
*Makes fingers pointing across each other gesture in classic "I need one to do the other" frustration*
=-J
Seriously, I'm not sure it would work anyway.
Since I can't see to aim the webcam, how would I know I've got it pointed at the screen in such a way as to let it see the boot menu?
For all I know I've got the dumb thing pointed up my nose, covered with part of my thumb, & getting a prime view of booger miner's motherload.
(It's the view most often captured in my days of photography, so it makes sense that it'd be the image I captured now as well.)
*Cough*
=-Jp
I'd need a second computer using the webcam to try & capture the first computer's screen during boot.
And that supposes the SRE can OCR the screen fast enough to let me start smashing keys.
*Sigh*
*Hands you a fresh, homemade chocolate chip cookie for effort*
Thanks!
I'd give you a silver star for effort but I think I baked them into the cookies.
=-D