Inaccessible Boot Device error in Windows 10

Thank you for your fix.......... but let me tell you how that worked with my notebook from Lenovo with Intel Chip!

Had the "inaccessible bootdrive" problem after the patch : KB4056892

Did try a lot of things that did not work, found your fix, tried it, but got allways this error:  DISM 0x800f082f

I did try again a lot of things but could not remove the package.

After a long time searching I found this webside:

http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

with the hint to change this key in the registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending]

So, after changing the registry key : "Exclusive" from 4 to 0, the uninstall worked and the system is up and running again.

I did not try any updates yet but will wait some days.

So, if anybody is having the same error 0x800f082f while trying to revert maybay this helps

ade_Nob

needless to say, that I am very angry that things like this happen out of the blue because of Microsoft!

With all of the DISM work that is going on here, are you or anybody else using the full suite of tools for a HEALTHY Image?

As I read what y'all are doing, I think not because nobody mentions it?????

Here is my Script, again:

ReagentC /Info

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

DISM /Online /Cleanup-Image /AnalyzeComponentStore

DISM /Online /Cleanup-Image /StartComponentCleanup

DISM /Online /Cleanup-Image /AnalyzeComponentStore

It might even make good sense with all of the problems to run one line at a time. If I were you I would be doing this not only in WinPE but Online once you Log back in as well. 

Here are the OFFLine equivalents to the above for WinPE:

sfc /scannow /OFFBOOTDIR=R: /OFFWINDIR=C:\Windows

DISM /Image: C:\  /WinDir:Windows  /SysDriveDir:R:\  /Cleanup-Image /RestoreHealth

DISM /Image:C: /WinDir:Windows  /SysDriveDir:R:\  /Cleanup-Image /AnalyzeComponentStore

DISM /Image:C:  /WinDir:Windows  /SysDriveDir:R:\  /Cleanup-Image /StartComponentCleanup

Where 'C' is your Image Disk and 'R' is your Central Boot and System Recover Disk(if all of that is on the 'C' disk then R = 'C' or not needed) 

ReagentC /Info  Is to check your WinRE or Recovery Environment. That need to be complete and Health or your not going to get into it at Boot time.

It should look like this:

Windows PowerShell

Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

    Windows RE status:         Enabled

    Windows RE location:       \?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE

    Boot Configuration Data (BCD) identifier: 4aa763b2-d195-11e7-8ba6-687f74ba1970

    Recovery image location:   \?\GLOBALROOT\device\harddisk0\partition1@Windows RE Install

    Recovery image index:      1

    Custom image location:

    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32>

"Custom image location" is no longer used and never worked very well or at all when it was used in W 8/8.1.

"\harddisk0\partition1" is my 'System Recovery' or 'R' disk. From this Image partition perspective, it is "\harddisk0\partition2" or 'C' disk and not specified.

"\Recovery\WindowsRE" is where the System Recover "Boot.wim" is along with other necessary files build by "ReagentC.exe" (RE Agent Control).

"@Windows RE Install" is where my Recovery ESD or WIM. It is called "Install.esd". This is for W 8.1 Pro my Main partition.

"\RecoveryImage (IP)" is the same for my FAST Ring "Install.esd" which is out of the latest SLOW Ring ISO that has been released.

"\RecoveryImage (RTM)" is the same for my Release Preview Ring or 1709 RTM "Install.esd" which is out of the latest RTM ISO Released. This is the one that should compare the most to y'all. The Point being when one is using a Central System Boot and Recovery Store on a separate partition, one gets creative. Also there is no one way to do allot of this stuff as long as your way, REALLY WORKS.

I personally don't use WinRE very often BUT I want to know that is there and healthy and complete. The system on the other hand uses it every time I boot to some extent.

I also would be running: CHKDSK /b (/x only in WinRE or Online) after I have wrung all of the corruption(corrupt System Files) out with the above to make sure all of your Directory Clusters are health as well in "System Volume Information".

I updated my NUC to the latest CU(RTM not Preview on W 8.1) last night and this:

"DISM /Online /Cleanup-Image /StartComponentCleanup"

Throws a CORRUPTION error. OH! says I, HUUUUUM!

So even though I had done this prior in the Script I did it again:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

I then proceed to run this again:

"DISM /Online /Cleanup-Image /StartComponentCleanup"

And it came out clean. At this point I have not seen a BSoD YET! It is working just fine on it's slide show and playing Radio Paradise, independently as it is part of my Entertainment Center, on a Broadwell CPU Mobile Dual Core 4 Threads. It can get quite a workout especially in Maintenance.

Folks if you run a corrupt system, Knowingly or Unknowingly, expect Corrupted Results!!!

If Microsoft is producing CORRUPTED Patches they should be hearing you scream for the hill tops.

At least you will be able to say what you do to keep corruption under control on your end.......

It is possible that there is a combination of faults here....

Make sure your Systems are Healthy, Admins. All of this can be run in Powershell. Powershell is a very excellent REMOTE Control facility, learn it, use it. Learn all about "Desired State Configuration". Powershell is heavy into all of this, Learn it, use it. This is not hard BUT there is a Learning Curve. Once Learned, it will be invaluable to your Employer OR a future Employer. Much promotion has occurred over Powershell.

And yes, Garbage in Garbage out! Make sure it is Microsoft's Garbage not yours and that you can Prove it.......

Hope all this helps folks,

Best Regards,

Crysta

It really didn't have anything to do with Bitlocker since the error reappeared today. I had no luck uninstalling the latest January updates through dism either. Windows did indeed start once, but after the first reboot got the same "inaccessible boot device" message again. Uninstalling even more updates with dism didn't help.

I once again restored my working backup and toggled the pause update switch. This really is my last option until Microsoft fixes this error. Btw. the working backup is from January 14th (Window 10 build 16299.192) which I find a bit strange since this should include all the latest updates. But still it does work - at least for some time.

It sure is the most serious and time consuming Win10 bug I have witnessed since Win10 was introduced. It makes me remember all the warning voices from back then, that saw these kind of issues with forced rolling updates coming.

What is kinda typical though is, that the only machine that's been hit by the bug is a 32bit machine which, for its ancient 16bit monitoring software, really is indispensable for the company.

PS: My "last option" failed me merely minutes after I posted the above. I again restored my backup and uninstalled the latest three updates through the Control Panel > Programs > Programs and Features > Installed Updates dialog. Windows tells me that it is now build 16299.125. I again toggled the pause update switch and went through a couple of restarts successfully. My issue seems to be mitigated for now - fingers crossed.