Windows 10 mandatory October KB4041676 update is causing machines to BSOD [Update]

Yesterday, Microsoft released a Cumulative Update for Windows 10 Creators Update, otherwise known as version 1703, which updated it to build 15063.674 as part of its Patch Tuesday update cycle - are you following? Good.

Today when people started waking up from their machines automatically updating during the night, however, they have been faced with a BSOD (Blue Screen of Death) instead of the Windows 10 desktop, and unfortunately, no-one seems to know why the installations are failing, only that it relates to KB4041676, which is yesterday's update.

On one thread at the Microsoft Answers forum, which has yet to see an official response from Microsoft, one user reported BSODs on all of his test machines, which consist of different makes of laptops and PCs (self-built, HP, and Lenovo):

I deploy patches via SCCM on a regular basis to nearly 5500 clients worldwide. My first group of Alpha systems which contains all of my own workstations receive the first round of patches as a test. ALL of the systems running 1703 blue screen upon reboot AFTER applying this patch (KB4041676).

The message that comes up is INACCESSIBLE BOOT DEVICE. After that, it reboots automatically, attempts to boot again, and then displays the "Automatic Repair" screen. None of these systems make it past this message.

My ALPHA test systems range from brand new Lenovo laptops, 2 Lenovo desktops, 1 Dell desktop, 2 custom built desktops, and 10 VMs.

What now Microsoft?

In another comment in the same thread, another user had a similar experience, posting:

Any computers that we had on overnight and have rebooted are no longer starting up with a blue screen and INACCESSIBLE BOOT DEVICE.

We've tried all the standard stuff:

Bootrec /fixmbr /fixboot /rebuildos
Renamed bcd file and tried rebuildos
tried copying SAM,SOFTWARE,DEFAULT,SYSTEM from regback
tried sfc /scannow
tried dism /image:DRIVE:\ /cleanup-image /restorehealth

So far NOTHING has brought the computers back. These are varying models as well across laptops and desktops, the main contributing factors are Windows 10 1703 and the KB 4041676 update.

And the list goes on, on Reddit, some people are complaining that disk usage remains at over 100% while trying to apply the update, which can take upwards of over an hour. Others are reporting that the installation is getting stuck at various points, 22% in this instance and 23% in another case reported on Microsoft Answers.

If you haven't updated yet, now would be a good time to ensure you have a System Restore point to roll back to. Additionally, you can download the Windows Update troubleshooter via this Microsoft article by following the steps, or through this direct link, running it before updating will check if you're good to go or repair previous failures to update.

Until Microsoft responds with the reason for why the update is failing, it's anyone's guess as to what is causing it, since the reports are coming in from vastly different types of machines attempting the update and failing at one point or another.

We will update this post once we have more information.

Update: Some people are commenting that the known issue posted along with the KB update:

"Systems with support enabled for USB Type-C Connector System Software Interface (UCSI) may experience a blue screen or stop responding with a black screen when a system shutdown is initiated."

- is probably the reason, but that doesn't answer why some systems without USB Type-C are having issues, including returning an install date of "1/01/1601" for the patch (Comment #1, #2).

Update #2: This appears to actually only affect WSUS users, despite multiple reports of others having isues updating outside of the Enterprise environment. Although Microsoft itself hasn't commented yet, some MVPs, forum volunteers and gurus have chimed in and even posted workarounds and fixes for those bricked (BSOD) machines that applied a Delta patch as well as the Cumulative Update (the former of which has been expired and won't download anymore) and therein was the problem. The Delta patch shouldn't have gone out with the KB update, and this has now been rectified.

For those that still need to recover their machines that updated via WSUS and then can't boot to desktop, go here for the fix, follow instructions.

Update #3 October 13: Microsoft has now confirmed a fix for this issue, see this article.

Cheers for the News Tip Chris Peters!

Report a problem with article
1507731402_screen_shot_2017-10-11_at_7.15.52_am
Next Article

Microsoft debuts four new Xbox One S bundles

1473240722_three-logo
Previous Article

Three brings digital literacy programme to Scotland

99 Comments - Add comment

Comments are closed

The comments on this article have been closed by our moderators. Further discussion about this article can be done so on our forums.

Visit our forums »

Thanks for the info. We have the update downloaded in CM but not deployed anywhere. I put that on our exclusion list for now.

Glad I changed my local group policy to disable auto updates. I usually wait at least a few days before installing patches for exactly this reason..

My PC is set to not restart automatically, so definitely going to roll this one back. There is definitely an issue - when I look at my update history, the date of this one is listed as "1/01/1601"

The 'inaccessible boot device' issue

I've discussed a few details about the 'inaccessible boot device' issue at http://borncity.com/win/2017/1...-windows-78-1-october-2017/

The problem occurs in WSUS or SCCM environments, if an administrator allowed delta and cumulative updates for the month. A Technet forum post has been deleted - but there is also a Microsoft article dealing with this topic linked within my article. Maybe it helps.

The 'inaccessible boot device' issue

I've discussed a few details about the 'inaccessible boot device' issue at http://borncity.com/win/2017/1...-windows-78-1-october-2017/

The problem occurs in WSUS or SCCM environments, if an administrator allowed delta and cumulative updates for the month. A Technet forum post has been deleted - but there is also a Microsoft article dealing with this topic linked within my article. Maybe it helps.

In addition to this, Microsoft has updated the known issues to include one cause of the BSOD:

https://support.microsoft.com/en-us/help/4041676

"Systems with support enabled for USB Type-C Connector System Software Interface (UCSI) may experience a blue screen or stop responding with a black screen when a system shutdown is initiated."

The 'inaccessible boot device' issue

I've discussed a few details about the 'inaccessible boot device' issue at http://borncity.com/win/2017/1...-windows-78-1-october-2017/

The problem occurs in WSUS or SCCM environments, if an administrator allowed delta and cumulative updates for the month. A Technet forum post has been deleted - but there is also a Microsoft article dealing with this topic linked within my article. Maybe it helps.

Weird part is, this is the first month I have seen a "delta" update for Windows 10 show up in my WSUS.. Never seen one more now. all the others are full cumulative.

Weird part is, this is the first month I have seen a "delta" update for Windows 10 show up in my WSUS.. Never seen one more now. all the others are full cumulative.

I'm being told by someone who contacted MS, that the Delta issue has been resolved and you should re-sync WSUS. Delta updates should not appear in WSUS and these should be marked expired after the re-sync.

The USB-C issue remains.

Weird part is, this is the first month I have seen a "delta" update for Windows 10 show up in my WSUS.. Never seen one more now. all the others are full cumulative.

same here, noticed this morning again

"

Critical and Security Updates

2017-10 Delta Update for Windows 10 Version 1607 for x86-based Systems (KB4041691)
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

2017-10 Delta Update for Windows 10 Version 1607 for x64-based Systems (KB4041691)
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system."

I think Microsoft should have an insider channel for just monthly updates. I wonder what all those systems have in common.

Updated 9 machines without issue. Unmountable boot device sounds like an issue with some kind of raid or SATA controller driver.

Only time I've seen unmountable boot device has been a corrupt NTFS volume, a drive with bad sectors or when you change the bios from IDE to ACHI or RAID or vice versa.

I think Microsoft should have an insider channel for just monthly updates. I wonder what all those systems have in common.

Updated 9 machines without issue. Unmountable boot device sounds like an issue with some kind of raid or SATA controller driver.

Only time I've seen unmountable boot device has been a corrupt NTFS volume, a drive with bad sectors or when you change the bios from IDE to ACHI or RAID or vice versa.

I think they do... on the insider preview there is an option for "just fixes and drivers"

I think Microsoft should have an insider channel for just monthly updates. I wonder what all those systems have in common.

Updated 9 machines without issue. Unmountable boot device sounds like an issue with some kind of raid or SATA controller driver.

Only time I've seen unmountable boot device has been a corrupt NTFS volume, a drive with bad sectors or when you change the bios from IDE to ACHI or RAID or vice versa.

You mean a beta program within the forced updates program subscription based cloud service OS that is Windows now ?

Beta inception LOL

I'm being told by someone who contacted MS, that the Delta issue has been resolved and you should re-sync WSUS. Delta updates should not appear in WSUS and these should be marked expired after the re-sync.

The USB-C issue remains.

I'm being told by someone who contacted MS, that the Delta issue has been resolved and you should re-sync WSUS. Delta updates should not appear in WSUS and these should be marked expired after the re-sync.

The USB-C issue remains.

Well the text has been send to premium customes - afaik. From my blog (https://goo.gl/bzMmpn)

Note that the issue is NOT with the Cumulative Update.

Root Cause: The Windows 10 Delta & Cumulative Updates were both published to WSUS & SCCM which is a situation that should not happen.

Customers should re-synchronise their WSUS / SCCM server and the Delta Updates Binaries will be expired.

There is no issue with the Windows 10 or 2016 Cumulative but only an issue when both the Cumulative and Delta are installed on a machine together. Since Delta Updates are never available to Windows or Microsoft Update, this could not have affected Consumer scenarios.

Please go ahead and deploy the Windows 10 & Server 2016 Cumulative and Security Only Updates.

What does winver 1709 have to do ANYTHING with WSUS/SCCM... absolutely nothing

The start of the article is about this being an issue with an update for 1703. That MS claim it's a wsus only issue only came about later in updates to the original article, and that is still contested by some anyway.

I was happy that I'd already upgraded beyond 1703 and was thus unaffected.

WSUS had nothing to do with my comments.

Technically this issue has nothing to do with forced updates, since WSUS/SCCM updates are manually approved...

So the update is not automatically installled then ? ..technically ?

not on WSUS or SCCM it needs the corp admin who manages both solutions to define the update for their OUS and deploy, both are just centralised patch management systems (granted SCCM is a lot more than that) and again any SCCM adm should be testing these before releasing to production, so a storm in a Tea cup. the SCCM adms are to fault for not testing new builds.

Oh ######, I've downloaded the update and it is ready to install after a restart. What should I do now?

Edit: Pulled the trigger and restarted. All good. Everything is working fine and on .674 version

"Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Microsoft Edge, Windows Authentication, Windows TPM, Device Guard, Windows Wireless Networking, Windows Storage and Filesystems, Microsoft Windows DNS, Microsoft Scripting Engine, Windows Server, Windows Subsystem for Linux, Microsoft JET Database Engine, and the Windows SMB Server."

Here is the issue.. probably caused by some security software, AV, Firewall, mallware detection or some other BS, a lot of times that type of software utilizes "security holes" to attach themself to OS better, once the security flaw gets patched, it kills the OS.

Happen in past many many times, mcafee, symantec etc... it happens every few months\years.

The dude ith 5000+ pcs should look at whatever security software he has, there is the issue.

Update wiped out EVERY app I had on my computer. No Settings anymore so I can't roll back. Thanks Microsoft for totally destroying my computer with another one of your crappy updates!

Update wiped out EVERY app I had on my computer. No Settings anymore so I can't roll back. Thanks Microsoft for totally destroying my computer with another one of your crappy updates!

With the amount of people saying they've had success with the update, i'm going to go with a computer issue on this one.

With the amount of people saying they've had success with the update, i'm going to go with a computer issue on this one.

Nope, nothing wrong with the computer prior to the update. However when the computer rebooted during the update, the screen went into portrait mode then rebooted again back into landscape. Third reboot and all seemed to run fine until I hit the windows button and tried to see the menu. All my win32 apps were just fine but EVERY app from the windows store and Windows itself were gone. Could not even access Settings. I have run an "update" from the ISO and the setting and stuff came back but still missing every app I had installed from the store. NO store, no groove, news app, etc.

Update wiped out EVERY app I had on my computer. No Settings anymore so I can't roll back. Thanks Microsoft for totally destroying my computer with another one of your crappy updates!

Why don't people make an image of their computer? buy an external drive, using something like Macrium reflect and make an image and a boot USB and then all you have to do is reinstall the image.

It is as some people say, a no brainer.

With the amount of people saying they've had success with the update, i'm going to go with a computer issue on this one.

However when the computer rebooted during the update, the screen went into portrait mode then rebooted again back into landscape.

I stand by what I said.

And you're still wrong.

Thanks for letting us know.

My computer updated automatically yesterday. I hope i wont have this problem. God i hate those stupid automatic update of windows 10. I preferred to be able to chose which update i wanted to install.

My computer updated automatically yesterday. I hope i wont have this problem. God i hate those stupid automatic update of windows 10. I preferred to be able to chose which update i wanted to install.

Go to update and change your settings. Since the creators update you have complete control over the updates now

Go to update and change your settings. Since the creators update you have complete control over the updates now

yeah nope all you can do is defer updates you cant actually unselect one so it doesn't get installed and I'm not WSUS/SCCM user nor do I have USB.C and I still got hit with problems after the install of this rapedate by MS

Can confirm our issue was the Delta and Cumulative patch being applied together. We have found and used the fix of removing the packages from within Win Recovery which has got us back to working.

We had some computers pick up the update this morning which are fine, it was only computers that got the update ~12 hours ago that were affected.

Mine didn't BSOD yet but it took me forever to get it to load my desktop kept saying failure to load personalized setting and went non responsive had to reboot serval times.

after finally getting it to boot to desktop though I am still ###### cause now my boot time is like 2 minutes whereas it was around 15seconds before... not kewl they need to fix this

This is exactly why I change the update settings to at least delay updates for a couple weeks. Anyone know the best way on 1703 Pro to disable automatic installing? I was using the reboot block method before but I think I would rather make it manually install

This is exactly why I change the update settings to at least delay updates for a couple weeks. Anyone know the best way on 1703 Pro to disable automatic installing? I was using the reboot block method before but I think I would rather make it manually install

why? this issue affected only machines managed by SCCM and WSUS??

why? this issue affected only machines managed by SCCM and WSUS??

Um no this issue is not just affecting those using WSUS/SCCM to install updates nor is affecting just those with USB type C on their mobo's I have no USB C nor do I use WSUS/SCCM and yet my system went bung right after the update

I paused updates for 7 days and already had feature updates/ quality updates deferred for 30 days. Thanks for the heads up.

My fiance got two penalties in Overwatch (-50SR each, plus a suspension) as a result of this BSOD happening twice on her Win10 machine this morning. Thank you, Microsoft, for reminding that I should stick with Win 7.

My fiance got two penalties in Overwatch (-50SR each, plus a suspension) as a result of this BSOD happening twice on her Win10 machine this morning. Thank you, Microsoft, for reminding that I should stick with Win 7.

That's not gonna be a proper fallback solution for very much longer...

My fiance got two penalties in Overwatch (-50SR each, plus a suspension) as a result of this BSOD happening twice on her Win10 machine this morning. Thank you, Microsoft, for reminding that I should stick with Win 7.

There is a version of overwatch that runs while computer boots? Even before windows environment? What voodoo is that.

My fiance got two penalties in Overwatch (-50SR each, plus a suspension) as a result of this BSOD happening twice on her Win10 machine this morning. Thank you, Microsoft, for reminding that I should stick with Win 7.

Nvidia released a broken driver from what I read (I switched to AMD) that an update fixed last night. You may want to check it out.

That's not gonna be a proper fallback solution for very much longer...

Neither will 10 when they decide to pull the rug out on the next batch of Fanboys. People supporting them seem to forget the clock is ticking on you guys not us 7 fans. The snow globe at MS gets shaken regularly.. i know i had a TRS-80 and have been in this stuff since the start.. after i got let down enough i got tired of it.. most of you will too when you get older.

That's not gonna be a proper fallback solution for very much longer...

Neither will 10 when they decide to pull the rug out on the next batch of Fanboys. People supporting them seem to forget the clock is ticking on you guys not us 7 fans. The snow globe at MS gets shaken regularly.. i know i had a TRS-80 and have been in this stuff since the start.. after i got let down enough i got tired of it.. most of you will too when you get older.

ok ok we get it, you love windows 7.

and for the record, W10 isnt going anywhere default_wink.png

That's not gonna be a proper fallback solution for very much longer...

Neither will 10 when they decide to pull the rug out on the next batch of Fanboys. People supporting them seem to forget the clock is ticking on you guys not us 7 fans. The snow globe at MS gets shaken regularly.. i know i had a TRS-80 and have been in this stuff since the start.. after i got let down enough i got tired of it.. most of you will too when you get older.

ok ok we get it, you love windows 7.

and for the record, W10 isnt going anywhere default_wink.png

I'm gonna repeat what I told a lady yesterday when she told me she'd like to have Win10 installed when she has 7 installed. She has an older computer (About 7 years-ish old, Pentium with 2gb ram). I told her, "Sure your computer can take it. But for that I would at the very least invest in an additional 2gb of ram. But that would be rather expensive (She runs on DDR2) unless we go used and then you have a potential stability factor. Is your computer running well?" "Yes" "Then I would recommend to simply stay with it. Windows 7 is still running good, and your computer is also running good, so no reason to upgrade right now and spend money on a computer that has maybe 2-3 years tops left in it."

Btw all she does is some light browsing, facebook and emails.

My fiance got two penalties in Overwatch (-50SR each, plus a suspension) as a result of this BSOD happening twice on her Win10 machine this morning. Thank you, Microsoft, for reminding that I should stick with Win 7.

While I doubt your story, your BSOD surely was something else and not related to this patch. Sounds like a GPU driver is causing your BSOD, considering KB4041676 BSOD's are occurring at boot.

Feck updates, just give us ISO's for 16299. Tried the ESD to ISO route but just asks for Product Key all the time on machines with digital licence link to account.

What a joke this has become. This is almost a monthly occurrence now. How many times now, just this year alone has their been multiple patch Tuesday BSOD issues.

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

I would rather hit issues like this than have an increased exposure to malware.

I would rather hit issues like this than have an increased exposure to malware.

Lucky you I work from home and can't afford to loose production. I need a working computer and getting a 0 day from only being 7 days behind is much lower than getting bricked by an update. Corporate computers are typically at least a month behind where each update is tested first.

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

Again with the unformed comment. This has nothing to do with regular Windows 10 clients not on WSUS/SCCM... Sorry but you don't know what you are talking about. This was an errant delta update that was published to the WSUS/SCCM catalog, nothing that went out to normal users.

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

When 10 is not tested to the extent that Win 7.

One is a matured stable platform and the other is a long running beta test.

I would rather hit issues like this than have an increased exposure to malware.

Don't click on virus.exe on torrent sites then.

I have never had a virus on my machine(s) since 7 came out.. an dget this, i have stopped using AV software since 2005.

Want to see some specs, benchmark reports etc ?

My custom OSD i made and the fact that i keep tabs on what is running at all times helps.. as well as limiting tasks and services etc.. i run a tight ship.. and i mean 'I'.

I don't fear malware.. malware fears me.. i have exposed many of them on P2P sites for example.. hell i have had my own stuff i coded flagged my Kasperky before LOL

No offense but i think noobs and wannabee edgy kids like Win10 or WIn 8.

People who have work to do use Windows 7 and.... and are happy. So i enjoy your latest batch of BS of death messages and excuses. Don't forget bad mouthing WIn 7 makes WIn 10 work better LOL

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

i have the pro version windows 10 and can delay large updates a year and security updates for 30 days, Maybe because i have the creator edition.

Why stick with Windows 7 it was said here ealier this week?

Well there you have it neowiners.

Rapid updates with agile may work great with simple smart phone apps, but can wreak havoc on very complex software like an operating system. Luckily I use the professional edition of 10 and have feature updates delayed up to 70 days and security and quality for 7.

Yes there is a risk of getting hit with a 0 day malware for me, but I do not want to have these problems and prefer others to find them for me first and the odds of a retraction of an update hitting before day 7 are higher.

So no people are not idiots for sticking with what works including Windows 7.

suuure cos W7 never ever been bricked by an update in its life. /shakes head

I would rather hit issues like this than have an increased exposure to malware.

Don't click on virus.exe on torrent sites then.

I have never had a virus on my machine(s) since 7 came out.. an dget this, i have stopped using AV software since 2005.

Want to see some specs, benchmark reports etc ?

My custom OSD i made and the fact that i keep tabs on what is running at all times helps.. as well as limiting tasks and services etc.. i run a tight ship.. and i mean 'I'.

I don't fear malware.. malware fears me.. i have exposed many of them on P2P sites for example.. hell i have had my own stuff i coded flagged my Kasperky before LOL

No offense but i think noobs and wannabee edgy kids like Win10 or WIn 8.

People who have work to do use Windows 7 and.... and are happy. So i enjoy your latest batch of BS of death messages and excuses. Don't forget bad mouthing WIn 7 makes WIn 10 work better LOL

This seems somewhat unrelated to my comment to be honest. I was really talking about liabilities.

If you're suffering downtime due to a bungled update from a vendor then that's excusable. Yes, frustrating but still excusable.

If you're suffering downtime due to a security problem and it turns out you had avoided or had delayed security updates that would have mitigated the problem then that's not excusable. That's seen as sheer incompetence.

AV software is a different and depressing ballgame altogether.

Again with the unformed comment. This has nothing to do with regular Windows 10 clients not on WSUS/SCCM... Sorry but you don't know what you are talking about. This was an errant delta update that was published to the WSUS/SCCM catalog, nothing that went out to normal users.

Tell that to my PC that was working perfectly fine until it crashed right after the update no WSUS/SCCM or USB type C here and yet it still trashed my system

Isn't WSUS set up so that people can test updates before deploying them to their network?

No it's so you have a central point to deploy updates from and manage groups of computers needing those updates. It keeps from having each client on a large network download updates individually. Testing is also an aspect that can be used by making a test group of PCs to install to. But that's not it's only/primary function.

I installed the update successfully or so I thought turned the PC on this morning only to find it wouldn't get past the loading screen after 30 mins of waiting I turned off the PC rebooted into the recovery console and ran system restore so now it's sitting waiting to be downloaded along with updates to the malicious software removal tool and windows defender and I have no way deselect the update KB4041676 as I don't want it until its fixed

So glad I delay my updates. Maybe MS will get it working before my computer decides to update, that is if I allow it to.

insider user here. I had these symptoms after an update in the last month. The system disk was f**ked. NTFS corruption, tried multiple data recovery tools, none of them could see a damn thing on the disk. A complete reinstall needed. The disk itself was fine.

I put it down to a problem with my system, not an update (I couldn't determine what updates had been installed). Hopefully these guys aren't suffering the same problem.

insider user here. I had these symptoms after an update in the last month. The system disk was f**ked. NTFS corruption, tried multiple data recovery tools, none of them could see a damn thing on the disk. A complete reinstall needed. The disk itself was fine.

I put it down to a problem with my system, not an update (I couldn't determine what updates had been installed). Hopefully these guys aren't suffering the same problem.

That's called a bad hard drive....

The continuing mandatory update problem with Windows-10 remains unfixed. Why is there any wonderment that people want to remain with Windows-7? Many of us have better things to do than having to deal with crashed PCs...such as running a business.

The continuing mandatory update problem with Windows-10 remains unfixed. Why is there any wonderment that people want to remain with Windows-7? Many of us have better things to do than having to deal with crashed PCs...such as running a business.

The thing is, you are confusing consumer with enterprise. This issue isn't affecting the standard user who uses Windows Update, this is an issue with SCCM and WSUS. Secondly, anyone running a business off of a single computer, that doesn't have some sort of backup or fail safe plan, is asking for trouble.

The thing is, you are confusing consumer with enterprise. This issue isn't affecting the standard user who uses Windows Update, this is an issue with SCCM and WSUS. Secondly, anyone running a business off of a single computer, that doesn't have some sort of backup or fail safe plan, is asking for trouble.

Really it doesn't affect standard users you say well I'll have to tell my standard PC that then because it's pretty funny that right after the update my "standard" PC went sod off I don't wanna go Just because MS say it only affect those using WSUS/SCCM or those that have USB type C in their systems does not mean that it only affects just those systems

Hmmm, this happened with Win 10 Pro on my desktop PC the other day. Booted up fine in the morning, used it for a while and it installed some updates, shut it down. Turned it back on later in the day and bam, Inaccessible Boot Device. This isn't supposed to be happening on non WSUS machines, so, a massive coincidence??

Hmmm, this happened with Win 10 Pro on my desktop PC the other day. Booted up fine in the morning, used it for a while and it installed some updates, shut it down. Turned it back on later in the day and bam, Inaccessible Boot Device. This isn't supposed to be happening on non WSUS machines, so, a massive coincidence??

You and me both it seems rcm

Comments are closed

The comments on this article have been closed by our moderators. Further discussion about this article can be done so on our forums.

Visit our forums »

Advertisement