Windows 10: Windows Failed Automatic Repair, Bad System Config Info and Cant Open PC to Login or Desktop

One day I turned on my PC and it said my hard drive failed or something along the lines of that. It proceeded to say the automatic repair system failed which then sent me to a blue screen of death and the problem said it was a Bad System Config Info. I’ve tried doing the Restart Repair option, turning my pc on and off, doing a reset on my pc (it was the keep file option but it still failed go reset it) and some command prompts. I don’t have a Recovery USB or Disc. I need answers because this has been happening to me for 2 days and i haven’t been able to get to my desktop and access my files or anything. If anyone can help me find an answer it would be very much appreciated.

:)

 

automatic repair can not repair PC stop code: BAD SYSTEM CONFIG INFO -help

automatic repair can not repair PC stop code: BAD SYSTEM CONFIG INFO -help. WINDOW 10 is running on a MAC three Parallells

 

Bad system config info and failure to launch windows 10

Windows 10 on a Dell XPS about 1.5 yrs old

turned machine on and got the Your PC ran into a problem and needs to restart; bad system config info.

Went through the multiple suggestions to fix, repair or restore but none of them were successful. Seemed to get a consistent response that a problem was encountered and therefore no the problem couldn’t be resolved.

Under troubleshoot attempted the prompt command option. The message under the Microsoft Windows [version 10.0.17134.1] said not enough resources available to process this command.

I found a video on youtube to address the bad system config info issue and followed the steps as presented.

After going through that process my system still won’t boot up.

there apprared to be enough free space on C.

thanks in advance for any assistance

Bob

 

Bad system config info windows 10 on boot up!!!

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) thread which starts with bootrec /rebuildbcd. Running that command generated the following report and option:

Successfully scanned Windows installations.

Total identified Windows installations: 1

[1] C:\Windows.old\WINDOWS

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?