Mar 17 2020 04:54 AM
Mar 17 2020 04:54 AM
I just wanted to double-check my troubleshooting thinking here, maybe I'm missing something in the modern era of Win 10.
So a laptop with a 2.5" HDD first boots up and gives the light-blue screen with the QR code saying there was a problem with the computer. It then shuts down. There is zero useful error info on screen, though, I did not follow the QR code to see what it said.
However, on powering it up again at the bottom during/after POST it gives the "diagnosing your PC" text as Win 10 will do anytime you have boot problems.
Long story short, all methods to do repair fail. System Restore does see restore points, to be able to utilize them I had to use cmd to start the vss service and then rstrui.exe /offline:c:\windows=active to be able to try to process them, but they all failed with "unspecified error".
Reset this PC > Keep my Files fails, no specific error.
So I've gone through all options in the startup diags screen for Win 10, both from the on-disk booted version and having booted from the USB WinRE thingy (Win 10 Media Creation Tool).
FWIW I went into the BIOS and boot mooe is UEFI. Set it to Legacy just to see, and that completely fails to even start to boot so i reversed that.
I was able to successfully clone the hard drive (took it out, docked to a duplicator). And I can access the data and see no signs of problem if I mount the drive to a working computer. A full virus scan on this docked drive also came up clean, though I do realize there could be more deeply embedded/encrypted malware, but for arguments sake let's say it's clean.
Am I missing some key Win 10 boot sector /fixmbr trick or something? I began to follow some command prompt guidance on running these bootrec commands. /fixmbr says it did so successfully, no change to issue. /fixboot said "Access is Denied". The other two bootrec both say they see 0 Windows installations, yet I can easily browse to the Windows folder on the C:
I tried to do this "diskpart /s scriptname.txt" thing so I can run diskpart > select disk 0 and maybe some other commands to follow, but apparently that command doesn't work as advertised because I would specify it on the computer having issues and it would just say it can't find the file.
My assumption is that the USB boot environment, under the Startup Repair section, tries to do all this mbr/partition type stuff anyway so it's a waste of time doing it manually. Would that be correct? You never know with MIcrosoft though.
Mar 18 2020 07:57 AMSolution
Mar 19 2020 04:00 PM
I ended up having to do a clean install. Had this been a hardware fault I expect I'd have had problems. What annoys me about the Win RE is that why, if this is only a software issue, could it not have fixed that? The concept of replacing corrupted file, and rebuilding corrupted partition/file system info should be fully integrated into the RE and yet it failed on all counts, and yet, it did see 4 System Restore points, and could even browse the full file system of C: with no issues. So perhaps it's some screwy thing with those hidden partitions but let's just say that my confidence in the WinRE kind of went down here, even Reset this PC failed and that makes little sense since it all went to plan by me just wiping out partitions and starting anew.
Ah well :)
Mar 20 2020 12:49 AM
Mar 20 2020 06:16 AM
Yeah that's exactly what I thought was going to happen, I got the insider news on that but in my head I thought the feature was already part of the bootable media so I was puzzled why even that didn't work. But I bet you're right, the image was corrupted or inaccessible somehow. Given that it would fail the Rest This PC process basically immediately, I suspect it was inaccessible to begin with, lending more credit to this being some kind of corrupted "something" in the file or partition/boot system, or maybe some general corruption just beyond those points.
Needless to say I'm putting this system on a full system image backup plan.
Thanks for all the good input!
Jan 22 2023 04:43 PM