Inaccessible Boot Device error in Windows 10

I have a similar issue to everyone else in this thread- Updates automaticallly installed and PC stuck in bsod loop. Start up repair fails. Can't boot in safe mode. 

PC is home built, running win 10 on an i7 4770k

After finding your instructions, I succesfully removed package "Package_For_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9" last night and the computer booted as normal- hallelujah! 

Turning the PC off and going to bed, it then installed package 16299.125.1.6 overnight! Today I'm back to square one.

In the package list, I can 192.1.9 as install pending and 125.1.6 as installed. Running the remove package again does not work for either packages, instead returning error 0x800f082f DSIM failed. 

Microsft support suggested I try using a bootable USB to run repair- this didnt work. Then they suggested using "dism /online /cleanup-image /restorehealth" with the USB. This failed as "dism does not support servicing windows pe with the /online option". Now they suggest the only option is to reset/ rebuild my PC, but I don't want to lose various software that I no longer have install media and/or keys for.

Hoping the collective wisdom of the internet may have some more suggestions?

Thanks in advance.

EDIT: I've just found the post giving the registry updates to fix error 0x800f082f so thanks to whoever posted it! http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

However can anyone help with the cmd entries to make this registry update?

There isn't a solution to this unfortunately.  I went through this earlier in the thread and did everything possible.  That registry fix doesn't work.

For the record, with nothing having worked, interestingly enough when I restored the OS from an old backup and did all the updates, the issue didn't reoccur.  All the software (besides some settings and browser plug-ins here and there) was pretty much the same and all updated first.  It seems the issue has occurred for people that were the most up-to-date and then did the update.  It hasn't occurred, even when this issue originally started happening, on even the same computers with the same configuration on which a bunch of updates were all done at once, having for instance not turned the PC on in months.

 Now they suggest the only option is to reset/ rebuild my PC, but I don't want to lose various software that I no longer have install media and/or keys for.

Hoping the collective wisdom of the internet may have some more suggestions?

The command

dism /online /cleanup-image /restorehealth won't work from preinstallaton environment.

You need to check on which drive are your Windows files while running from the USB stick. Usually it is D: if you have the system partition.

Then run dism.exe /image:D:\ /cleanup-image /restorehealth I am writtng this from off the top of my head.

It is usually possible to see what is broken in the package by examining the dism logs. This is a very tedious work, not worth it if you have another recovery options.

forget about what's on the x: drive. And it is NOT on C: (unless you aren't following instructions)

You need to boot from recovery media, not use the recovery environment on the hard drive.

You do not care anything about the x: drive!!!!!

After booting from recovery media, locate your windows drive.  It should be the only drive that has a Users**{your name}**  folder

use that letter in the repair procedure.

Then follow the instructions (CAREFULLY).  Remember you can use notepad in the recovery environment.  Also you can mark and copy the long names of the patches from the DOS windows and paste them in a notepad file. Create a batch file from the notepad files that looks like this:  (in my case the windows drive letter was e:)

md e:\temp

md e:\temp\packages

dism /image:e:\ /get-packages

pause

dism.exe /image:e:\ /cleanup-image /revertpendingactions

dism /image:e:\ /remove-package /packagename:package_for_kb4056887~31bf3856ad364e35~amd64~~10.0.1.0 /scratchdir:e:\temp\packages

dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /scratchdir:e:\temp\packages

dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /scratchdir:e:\temp\packages

dism /image:e:\ /remove-package /packagename:Package_for_KB4058702~31bf3856ad364e35~amd64~~16299.188.1.0 /scratchdir:e:\temp\packages

This was the batch file I created to fix the problem.

I put the pause in so you can verify which Packages are installed in your version of windows.  You need only remove the 2018 dated packages.

You will recover your Windows build for one boot only. 

Do not reboot, but immediately perform an in-place upgrade (repair install)

After the upgrade, your windows will be recovered.

what I can do if I did restart after first successful boot without in-place upgrade ? I get same "inaccessible-boot-device-error" and now unable to boot even following this instructions again