Windows 10: Microsoft confirms Windows 10 update bug causes boot issues

If your Windows 10 computer started rendering Blue Screen of Death when you run Check Disk command, don’t worry – you’ll be able to use your device properly again in the next 24 hours, according to Microsoft.

Yesterday, we reported that some Windows 10 PCs are rendered a useless brick when users run the built-in Check Disk Utility (chkdsk). Check Disk Utility basically allows you to use the Command Prompt to check a specified disk and repair/recover data on the drive when corruption is detected.

Generally, users are recommended to use Check Disk Utility when they’ve issues with Windows 10 or Windows Update problems. This is because the free tool is also able to detect malfunctioning sectors on the hard drive and recover your data or corrupted system file.

With a poorly-crafted update, Microsoft broke the Check Disk tool and it could crash some devices with ‘File System’ stop code error, as shown in the screenshot below.

Microsoft says a “small number of devices” that have installed Windows 10 update KB4592438 might not boot if you run “chkdsk /f” command. This is because a bug in the tool is damaging the file system, which makes the affected device unbootable.

Surprisingly, Microsoft acknowledged the issue quickly and the company has already started rolling out a fix, but you might not receive patch immediately. The software maker noted that the system crashes will be prevented automatically in the next 24 hours and you don’t need to make any changes.

Restarting your device might help the server-side update to apply to your device faster, but changes can still take up to 24 hours to propagate.

For enterprises or non-managed devices, you can configure a special Group Policy to address the problem:

1. In the Recovery Console, select Advanced options.
2. Select Command Prompt
3. In Command Prompt, type: chkdsk /f
4. Once done, type exit
5. The device will restart as expected and it will not crash.

Note that the above instructions are for affected enterprise users only. As we mentioned at the outset, Windows 10 customers will get the patch automatically and no actions are required.

In addition to system crashes, users have also reported that Windows 10’s latest update causes high CPU usage, installation issues, temporary data loss, and more.

The post Microsoft confirms Windows 10 update bug causes boot issues appeared first on Windows Latest

Weiterlesen...

 

New install Windows 10 (issue solved)

It's good that you're not experiencing any issues. Unfortunately many folks are, a quick Google search will show the same info im offering the OP.

Heres a couple examples:

Here

Here

It's basically what I mentioned above, small issues here and there ,but nothing to end your day.. for the most part.

I know it's anecdotal, but for my experience 95% of the time it's perfectly fine. The issues I've run into wouldn't be enough for me to roll back , but they would be enough (had I not installed it yet) ,to avoid it for another couple weeks which is why I'm suggesting it to the OP

Windows 10 Fall Creators Update problems and complaints

• Installation problems with the Fall Creators Update
• Microsoft Edge problems with the Fall Creators Update
• Drivers problems with the Fall Creators Update
• Experience problems with the Fall Creators Update

keep in mind, as of recently, the FCU is installed on 5% of devices roughly.....

 

Windows 10 Anniversary Update Issues

i cant say for sure what might be causing problems for those who are experiencing issues, but I figured it couldnt hurt to point this out to those who might not be aware of it, it is ONLY effecting Insider program members. as far as M$ has announced.

Windows 10 update traps some systems in a boot loop

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer