- Feb 5, 2004
- 2,768
- 29
- 91
So, right in the midst of the SB, we had a brief power outage. You know, one of those OFF-BACK ON! ones that resets everything. My PC went down, and on reboot, I got the Win10 blue screen telling me that something had gone wrong, and I needed to use repair tools to fix it, error code 0x000014c, C:\WINDOWS\BCD. I'd never had any doings with this error before, so I popped in my installation USB drive, booted into it, and went through the menu options to the one to fix boot errors, fingers crossed the whole time. It was unable to repair whatever damage had been done, so off to the interwebs for a solution. Two days later I found the needed info-dropping to the command line and running a series of commands that basically rebuilds the BCD (Boot Config. Data). Everything went as hoped until I ran the critical command, "rebuildBCD." This produced an error message saying that no device could be found. Stumped, I ran that info through Google and by good luck I found a thread a guy left saying he had the same problem. Solution? (anyone want to take a shot?) I had my installation USB drive in a USB 3.0 port. The guy's thread said all he had to do was boot from a USB 2.0 port and the repair worked. I tried that, and bingo! Repair was successful and I am now typing this on my previously unbootable PC.
So, anyone else have this issue? Whatever else I might have tried, I doubt I would have ever opted for a 2.0 port as a troubleshooting option. I have no idea why one port worked and the other didn't, but I feel lucky that I stumbled on to the fix. Those of you who are knowledgeable about such things may know, but what I wonder is a) what the hell happened to the BCD during that power failure, and b) why would a USB 2.0 port allow the OS utility to work when a 3.0 port would not? All very freaking weird. Thanks for any info you can lend.
So, anyone else have this issue? Whatever else I might have tried, I doubt I would have ever opted for a 2.0 port as a troubleshooting option. I have no idea why one port worked and the other didn't, but I feel lucky that I stumbled on to the fix. Those of you who are knowledgeable about such things may know, but what I wonder is a) what the hell happened to the BCD during that power failure, and b) why would a USB 2.0 port allow the OS utility to work when a 3.0 port would not? All very freaking weird. Thanks for any info you can lend.
