I’ve been running Windows 10 on a Toshiba Satellite laptop for a while, and have endured only the occasional, minor annoyance from a Windows 10 update. And the latest update on Sunday evening (Feb. 4) appeared to complete successfully after a restart. But when I attempted to restart again yesterday evening, however, I got the dreaded "BAD SYSTEM CONFIG INFO" boot error. No other updates or installs were performed between the Sunday Windows 10 update and the failed reboot.
Following the boot error message, Automatic Repair ran but failed, as did all of the following accessed via Advanced options:
- Continue (to Windows 10) - Hey, it was worth a try.
- Troubleshooting>Advanced options>
- System Restore - "No restore points have been created ..."
- Startup Repair - Same outcome as with failed Automatic Repair.
- Go back to previous version - "We ran into a problem and won't be able to take you back ..."
Command Prompt did open a CMD window, however, so I used Google to find threads describing what to do next. That uncovered several candidate fixes, so I tried #1 described below, and started on #2 before getting to a fork in the road that I decided deserved this posting:
- I first tried a 4-step fix involving use of bootrec, after changing the current directory from X:\windows\system32 to X:\windows\system32. The fix failed at bootrec /fixboot with "The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded ..."
- Next tried a variation of #1 that I found posted 7/30/2017 by John Vil in this (now locked) MS Community thread which starts with bootrec /rebuildbcd. Running that command generated the following report and option:
Successfully scanned Windows installations.
Total identified Windows installations: 1
Add installation to boot list? Yes(Y)/No(N)/All(A):
Question 1: Should I continue down this path, and if so, which /rebuildbcd option should I choose, Y or A?
Question 2: Or should I abandon this path and try another first? For example, fix #4 in this XtremeRain article (also found in an MS Community thread), which appears to involve restoring the pre-update registries?