Inaccessible Boot Device error in Windows 10

BTW: I called Microsoft several times on this issue.  They were of no help.

The support staff was being overwhelmed (by similar issues I suspect), because wait times were over 45 mins.

I explained that I had access to more that one machine and I could mount the affected hard drive in a working machine to

gain access to it to help resolve the issue.  I explained that I had done all the necessary checks: checkdsk, sfc, etc.

I explained that a I had images of the affected hard drive and if one strategy failed, I had another hard disk with the image waiting.

I explained that system reset worked, but that was not a desirable outcome. l had over 50 programs installed and didn't want to have to load, configure and update all of them.

I explained that I had performed disk, CPU and memory checks and all the hardware was in order.

I explained that taking a blank hard drive, I could install windows 10 (1709) and it worked fine.

I just wanted to back out the last update that crashed the system.

1st tech: put me on hold for 5 minutes and then hung up.

2nd call, couldn't wait the 45 minutes and gave up after 30.

3rd call indicated that support times were heavier than normal, then said that support was closed (there was still an hour to go).

4th call 2nd tech: Consulted with his supervisor for 4-5 minutes then came back and asked me how old the PC was.  I replied "4-5 years"

He then asked me the model.  "HP Pavilion P6120f".  Checked with his supervisors for another 3-4 minutes, then came back and said, "Your PC is not COMPATIBLE with Windows 10".  Seeing that I was at a dead end, I terminated the call, but then I thought back. Windows 10 practically FORCED me to upgrade from Windows 7.  It nagged me constantly to upgrade and it had been working fine on Windows 10 for over 2.5 years.

Once I had figured out the procedure to recover the working build, I called Microsoft to report it so that others could get their PC's fixed.

5th call 3rd tech: Could not understand that I was reporting a successful recovery.  Wanted to know what the problem was.  I am sure she just took down the basic procedure to humor me.  Wouldn't let me talk to anyone in the next support tier.

I'm glad we have this arena to share information.

I haven't seen your symptoms before.  However I suspect you may be getting them because of any of the following:

1. your repair disk may not be the same exact version as the version on the affected PC. (i.e. (1703) instead of (1709))
2. the version Pro vs Home is different

check your version by opening a command prompt after getting into windows the first time.

(right click start, click run and type CMD and press enter)

Microsoft Windows [Version 10.0.16299.125] is 1709.  Most of the files in C:\windows\system32 are dated 09/29/2017.

1709 (64 bit) only fits on a dual layer DVD or 8Gb flash drive.

After first boot, try downloading the media creation tool and either make a bootable flash drive or burn a dual layer DVD (or download the ISO image to the affected hard drive)

run the repair from that image.

I'm only guessing here because all the times I have seen it, (which has been several) the in place upgrade works.

wiz

It needs to be noted, that, Robin's method WRINGS CORRUPTION IN THE IMAGE out in the most extreme, but acceptable way, with an IN PLACE UPDATE for SOME, not that, that is a bad thing. It maybe the ONLY way for a few!

I have to wonder however, Robin, what if you did(or did you?) SFC /scannow, DISM /RestoreHealth and DISM /ComponentStore(abbreviated CMDLine), and what the results would have been. Would that had wrung out the Corruption in the Image(Bit Rot as the Industry calls it). It would be interesting to know???

The bottom line appears to be at this point:

1. Unknown Patch compromise for some PC/Workstations/Servers.(this would also include the Machine Missing a necessary prerequisite Patch, Identified or non-identified) Yup this complex.
2. Compromised Patches by AV of one 3rd party or another.
3. The original Image being to corrupted, for such deep Kernel Patch(s) (not the Patches fault).
4. Other unknown, unlikely, but happens anyway, unspecified problem(s) compounding and compromising the PC.(This one is obviously the least likely)

Which still supports, wringing out all of the corruption one can before Patching deep into the kernel OR really any kind of Patching. Bit Rot is real and corrupting. If just the exact right bit is flipped by something or even the memory, or disk itself, one can find themselves in BSoD hell and/or an unbootable situation.

Just as y'all have probably noticed in the past, some of the error messages that MS/Windows Throws are not necessarily the most accurate in their description of the ERROR or PROBLEM. That however doesn't make the fault any less critical or the PC anymore bootable. Just some food for thought....... about Red Haring's.

Best Regards,

Crysta

from the x: prompt (this is the windows recovery environment drive)

type dir d:

or dir e:

etc until you see your build of windows.

you do not want to do anything to drive X

all references are for you to substitute the letter of your windows build for X.

(you can tell which letter your windows is on by looking at the users directory for your name.

example: dir d:\users or dir e:\users, etc.)

substitute that letter in all the commands

wiz