New
#1
BSOD on boot - INACESSIBLE_BOOT_DEVICE
Hi,
All my woes started with an update, that did not want to install. It would attempt to finish the update installation on reboot, but then fail and "undo the changes." I later found out via event viewer that it was failing to create a restore point. I believe that's why the update install was failing, and I never did figure out why the restore point was failing, but I think the restore point saga is one for another post.
On what ended up being my last attempt at getting it to install, there was a power loss at the "Restarting..." phase of the update installation (so it had already done the "Updating.." part). Upon reboot, BSOD with the message in the title.
I wasn't able to get very far via the cmd prompt in recovery, uninstalling latest updates via recovery, etc, so I dug out the DVD today and tried further debugging. When I attempted automatic repairs today, it failed as per usual, but at least this time it gave me a log path (albeit not very useful), which is here:
SrtTrail.txt - Google Drive
So a binary is corrupted, makes sense, but it doesn't really tell you what. So my first thought after reading around was to run SFC, and I did that via "Repair" on the DVD.
sfc /scannow /OFFBOOTDIR=D:\ OFFWINDIR=D:\Windows
This failed because it said a previous repair was pending. After some digging, I found it determines this by looking for the file: Windows\WinSxs\Pending.xml. I removed this (I still have it if I need to put it back). After that, the above command ran successfully. Unfortunately, no problems found.
So the other mainstream tip you find is to use DISM to remove pending installed packages. It fails for seemingly all packages that are pending install, I also tried removing pending uninstall, ie.:
dism /image:\ /Remove-Package /PackageName:Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4400.1
This failed, the log for which is here:
dism.log - Google Drive
I would definitely prefer not to nuke the partition, although I'm definitely at a stand-still. If anybody has any idea on why that package removal is failing, I'm all ears. I just saw in signing up & posting this the v2 script collector thing. I'm going to see if I can run that now off the DVD repair mode.
Thanks!
EDIT:
It seems the v2 script collector is written in power-shell, which is a no-go for me using only the repair mode on the DVD or recovery partition which only have the traditional command prompt.
Should I try the DM log collector .exe instead? I can't really look at it to say if it'll work in the DVD recovery mode given that it's a binary. But I have filesystem access via another OS, so I can get any logs that are needed.
Last edited by Greg100; 01 Sep 2021 at 05:31. Reason: Update