Inaccessible Boot Device error in Windows 10

This worked on an AMD system:

1. BSOD after installing Jan-2018 Cumulative Update.
2. System Restore to restore point established before step 1.
3. Reboot after System Restore to an again working system.
4. Allow Windows Update to again install the Jan-2018 C.U.
5. Before rebooting the system, installed KB407391.msu downloaded from the Microsoft Update Catalog (330MB, 15 min. to install on an older, slower system).
6. Rebooted after installation complete. Successful restart, no BSOD.

Bobby?  Can you post up your support incident number?  Thanks in advance.

What if you have removed the update (on Friday) via DISM, The computer then came back and booted normally.

Computer rebooted to resintall windows update late Friday night while I was out, and now back to the innaccessible boot device message.

The packages are not listed now under the dism commands that i removed before.  There is only one update package listed (from 12/9)   I've run out of patience with this time.

I saw Microsoft released a new patch today

https://support.microsoft.com/en-us/help/4073290/unbootable-state-for-amd-devices-in-windows-10-version-1709

But how can you install the patch when you can't get into the PC? 

KB40743290 for 64-bit systems and KB4073291 for 32-bit systems was released to deal with the AMD processor BSOD issue, but how and when should it be installed? I'm working on an older AMD desktop system right now that hadn't been updated with the Jan-18 Cumulative Update yet. I set a restore point and then ran Windows Update. It dowloaded and installed only the cumulative update and after rebooting, I still got the BSOD. I'm now in the process of doing a system restore. When it's back up again, do I rerun Windows Update and reinstall the Cumulative Update and then attempt to install KB4073291 from its msu file before rebooting?

Hi,

It sounds like you are trying to do everything in WinRE(Recovery Environment) when you really should be in WinPE(Preliminary or Preinstallation Environment). I have had DISM throw that message but as of yet never encountered a problem because of it.

To create a WinPE you need to get the latest stable ADK for 1709 and install a few items that you need for DISM and WinPE. If you install to few, you can always go back in and get more. This presumes you have a working stable Window 10.0 1709 PC to do this on. Look in "Program Files" under the ADK for the CMD, have a USB or DVD available and click that ICON line.

Be advised DISM needs a fairly stable Image to work in. It "sounds" like your getting your Image more and more tangled up????.....

When you can, probably in Safe Mode, one needs to lock WU/MU GUI right down. I will dig out my notes on how to do that, but look at this first:

Configure Automatic Updates using Registry Editor

This is what Microsoft does NOT what you to know in the Windows 10 CLIENT ERAbut it is just as valid today as it was yesteryear. This is how Management Systems lock down clients and servers. So be very, very careful in the registry, because you can screw up things, if you make them wrong for what the OS KNOWS ABOUTBUT if you put in a Key or Name/Value that the OS doesn't know about, that won't hurt anything..... be as accurate as you can be.

One thing to realize is some values are not shown. for example AUOptions starts at 2 to 5. No, it really starts at 1, which equals OFF. Mine is set to 1. Now if you leave it like that along with a few other Registry modifications, it makes YOU RESPONSIBLE for Managing and keeping your OS updated when it is and how it is viable. That is allot of responsibility. I have had the OS visibly before my eyes change my setting in the registry for WU. You may have to take control in Permissions of those Names. Be very careful that there isn't other names effected that are not specifically to do with WU. Then one may need to force the "System" to be read only, so it can't change them.

Unfortunately this is the world Microsoft has created in their aspiration to be everybody's Admin for the average User and make PCs more utilitarian, which they are not yet there, as Computer.

In other words I am not advocating UnPatched OS, which is where the Security Patches in the MS Catalog come in but at this time they may not even work for you until this CPU/Meltdown/Spectre/BIOS mess is sorted out. Keep aware and please if you do this, don't get complacent.

Best Regards,

Crysta

Hey Crysta,

Thanks for the suggestion!  I'm surprised it's never actually come to me having to do this at any point in the past.  I manage many personal, family, and office computers.

Regarding Windows Update, all that stuff I understand and know about, and you're definitely right in giving those disclaimers.  I keep myself up-to-date with what's going on and always perform maintenance, but that's why I don't recommend it to others when they ask me if I know how to disable them, because obviously nobody knows how or would otherwise care to do any of that.  So far, there haven't been crazy issues like this if you had automatic updates and did them at the pace they came out.  The more annoying thing about them was honestly how they reset many of the privacy, registry, and group policy changes you might make, as well as certain other defaults.  Why even give people those options then or have changeable values when they're just forcibly reset every half year or whatever it is?.. :/  In any case, you're absolutely right that PC's aren't anywhere near what Microsoft purportedly "aspires" to.  Couldn't be any less intelligent compared to what's actually possible in modern times...

Back on topic, not sure why you mention I should look at configuring automatic updates first through the registry editor or booting into safe mode, as being able to do either would mean the real problem/concern would already be solved.  That's what really I'm currently helpless for.

Regarding what's needed to perform this task off WinPE, here is where the steps to actually installing and booting from it would be very helpful.  They don't need to be detailed asI would easily understand them, but you think you can perhaps make some bullet points as to what I would need and then further do with?  Basically I'd just be trying the DISM commands through this?  Thanks again!

Best,

David