> ## Content Index > Fetch the complete content index at: https://techbytefix.com/llms.txt > Use this file to discover other available public pages before exploring further. # Fix BAD_SYSTEM_CONFIG_INFO Error and Start Windows Again - URL: https://techbytefix.com/fix-bad-system-config-info-error/ - Published: 2026-10-25T00:27:46.000Z - Updated: 2026-10-25T00:27:46.000Z - Author: Jake Whitman - Tags: Windows, Troubleshooting To fix BAD\_SYSTEM\_CONFIG\_INFO, start with the reversible options in Windows Recovery Environment: remove a recent update, run System Restore or Startup Repair, and try Safe Mode. If those fail, repair the boot configuration and Windows system files, then test RAM and recently added hardware before considering a reset or reinstall. ## What to do first when BAD\_SYSTEM\_CONFIG\_INFO appears BAD\_SYSTEM\_CONFIG\_INFO means Windows found invalid system configuration while starting. The exact cause is commonly a damaged registry setting, broken boot configuration data, an incompatible driver or update, or faulty memory. The blue screen can appear during startup, after an update, or soon after you install a driver, memory module, storage device, or other hardware. ```text BAD_SYSTEM_CONFIG_INFO ``` Error If Windows reaches the desktop, save important files to an external drive or cloud location before changing system settings. If it crashes before you can sign in, use Windows Recovery Environment instead of repeatedly forcing shutdowns. Disconnect newly added USB devices, docks, printers, external drives, and other hardware that Windows does not need to start. Do not disconnect the drive containing Windows. If you recently installed RAM, a graphics card, storage drive, or another internal component, power the computer off and return it to its previous hardware configuration if you can do so safely. Write down what changed before the first crash: a Windows update, driver installation, BIOS or UEFI change, new hardware, unexpected power loss, or failed disk. If removing a device lets the computer boot, shut it down again and test that device separately rather than assuming Windows is fixed. Do not delete files from `C:\Windows\System32\config`, replace registry files from an unverified source, or run a reset before protecting your data and checking whether hardware is failing. Those actions can make recovery harder and can destroy installed programs or personal files. ![A Windows laptop shows a blue screen during startup.](https://tse1.mm.bing.net/th?q=Windows%20laptop%20blue%20screen%20startup&w=624&h=352&c=7) ## Which fixes are safe for your situation These steps apply to Windows 10 and Windows 11 on ordinary desktop and laptop installations. Recovery options can differ on a work-managed computer, an encrypted drive, or a manufacturer recovery image. You may need an Administrator account, a BitLocker recovery key, and a second computer to create Windows installation media. If Windows starts and stays running, begin with removal of a recent update or System Restore. If it crashes repeatedly, use Windows Recovery Environment (WinRE). A restart is required for most repairs, so connect the computer to AC power and keep a backup drive available. To enter WinRE after a failed startup, turn the computer on and let Windows begin loading. When the Windows logo or spinning indicator appears, hold the power button until the computer turns off. Repeat this interruption once more. On the next start, Windows should display Automatic Repair; choose `Advanced options`. If Automatic Repair does not appear, start from Windows installation media. Select the correct language, choose `Repair your computer` instead of `Install now`, then open `Troubleshoot` and `Advanced options`. You may need to unlock the Windows drive with its BitLocker recovery key. Before running commands, identify the Windows drive letter in WinRE. It might not be `C:`. In Command Prompt, try `dir C:\Windows`, then `dir D:\Windows` or another letter until you find the folder containing Windows. Use that letter in later commands. If no drive contains a Windows folder, stop and check the storage connection or seek help rather than guessing. ## How to repair BAD\_SYSTEM\_CONFIG\_INFO without making the problem worse Follow these steps in order. After each step, choose `Continue` or restart and check whether Windows reaches the sign-in screen and remains stable. If a step works, stop there and verify the result before changing anything else. 1. Remove a recent update or use System Restore In WinRE, open `Troubleshoot` \> `Advanced options` \> `Uninstall Updates`. Try `Uninstall latest quality update` first. If the problem began after a larger Windows version upgrade, use `Uninstall latest feature update` instead. Windows may ask for your account password. If uninstalling an update is unavailable or does not help, open `System Restore` and select a restore point from before the crashes began. System Restore normally preserves personal files, but it can remove recently installed drivers, programs, and updates. Review the affected items before confirming. Expected result: Windows starts without the blue screen after the restart. If the error returns, continue to Startup Repair rather than repeatedly uninstalling updates. 1. Run Startup Repair In WinRE, select `Troubleshoot` \> `Advanced options` \> `Startup Repair`. This tool checks common startup problems, including some boot configuration and system-file issues. It may restart the computer more than once. Expected result: Windows reaches the sign-in screen. If Startup Repair reports that it could not repair your PC, return to `Advanced options` and continue with Safe Mode or Command Prompt. That result does not prove that the drive or motherboard is defective. 1. Try Safe Mode and remove the suspected driver In WinRE, select `Startup Settings` \> `Restart`, then press `4` or `F4` for Safe Mode. Use `5` or `F5` for Safe Mode with Networking only if you genuinely need network access. Safe Mode loads fewer drivers, which helps distinguish a third-party driver from a deeper startup problem. If Safe Mode works, open Device Manager and roll back or uninstall the driver installed immediately before the error began. Also remove recently installed system utilities, antivirus software, storage tools, or overclocking software. Restart normally after each change. Expected result: normal Windows starts without the crash. If the error also occurs in Safe Mode, a normal third-party driver is less likely to be the cause; continue with boot and system-file repairs. 1. Rebuild boot configuration from Command Prompt Open `Advanced options` \> `Command Prompt`. These commands require Administrator-level recovery access. First inspect the boot entries: ```cmd bcdedit /enum all ``` Command Prompt If the command displays boot entries, rebuild the boot files for the Windows installation you identified earlier. Replace `C:` with the correct Windows drive letter if necessary: ```cmd bcdboot C:\Windows ``` Command Prompt Expected result: `Boot files successfully created.` Restart and test Windows. If `bcdboot` cannot copy the boot files, the drive letter may be wrong, the EFI system partition may not have a usable drive letter, or the storage may be damaged. Do not delete partitions or format the disk; stop and identify the partition layout first. On older BIOS-based installations, you can also try these non-destructive boot checks: ```cmd bootrec /scanos bootrec /rebuildbcd ``` Command Prompt If `bootrec /rebuildbcd` finds a Windows installation, accept it only when the listed path is the installation you intend to start. If it finds nothing, that points to a path, disk, or boot-mode problem rather than a reason to erase the drive. 1. Repair Windows system files offline Still in WinRE Command Prompt, replace `C:` with the Windows drive letter you identified: ```cmd sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows ``` Command Prompt Expected result: System File Checker reports that it found and repaired corrupted files, or that it did not find any integrity violations. Restart and test Windows. If SFC cannot perform the requested operation, verify the drive letter and run it again from WinRE rather than deleting files manually. If an interrupted update may be involved, use DISM to revert pending actions: ```cmd dism /Image:C:\ /Cleanup-Image /RevertPendingActions ``` Command Prompt Restart after the command completes. If DISM reports that the image cannot be serviced, check that `C:` is the actual Windows partition and that the drive is accessible. Repeating commands with guessed drive letters can repair the wrong volume. 1. Test memory and remove hardware if software repairs fail Faulty RAM can produce changing stop codes, failed repairs, corrupted files, and crashes that appear unrelated to updates. If the computer can boot, press `Windows` \+ `R`, enter `mdsched.exe`, and choose to restart and check for problems. You can also run the manufacturer’s built-in memory test or a reputable bootable memory diagnostic. Test one memory module at a time when the computer has multiple removable modules, following the computer or motherboard manual. Power off, unplug the machine, and observe anti-static precautions. If the error follows one module or disappears when a particular module is removed, replace that module or have the system serviced. Also check recently installed storage, graphics cards, and expansion cards. A loose connection or incompatible component can mimic a Windows configuration problem. If memory testing reports errors, stop software repairs and address the hardware first. Do not trust a Windows installation that is being corrupted by unstable RAM. ![A Windows computer displays the Startup Repair option in the recovery environment.](https://tse1.mm.bing.net/th?q=Windows%20computer%20Startup%20Repair%20screen&w=624&h=352&c=7) ## How to confirm Windows is actually fixed A single successful restart is not enough. Confirm that Windows reaches the desktop twice or more, remains idle for a while, and resumes from a normal restart without showing the same blue screen. Reconnect removed devices one at a time, restarting between changes. If you used Safe Mode, return to normal startup and check Device Manager for warning icons. Review `Settings` \> `Windows Update` \> `Update history` and note any update or driver you removed. Do not immediately reinstall the same driver or update until you know which change triggered the failure. From an elevated Command Prompt in normal Windows, check system files again: ```cmd sfc /scannow ``` Command Prompt (Run as Administrator) Expected output is either `Windows Resource Protection did not find any integrity violations` or a report that corrupted files were found and repaired. If SFC repeatedly reports corruption after a restart, investigate the storage drive and memory instead of treating the repair as complete. Run Windows Memory Diagnostic or a hardware memory test to completion if you had unexplained crashes, failed SFC repairs, or inconsistent results. A clean memory test lowers the chance of a RAM problem but does not rule out a failing motherboard or storage device. Keep your backup current while monitoring the system for repeat crashes. ## When to stop troubleshooting and reset or replace hardware [Stop troubleshooting and protect](https://techbytefix.com/basic-troubleshooting-skills/) your files when the computer cannot consistently detect the Windows drive, the drive makes unusual noises, files keep becoming corrupted, or memory testing reports errors. A failing SSD or hard drive can make registry and boot repairs appear to work temporarily. Copy personal files from WinRE or connect the drive to another computer if Windows will not stay running. If Windows is stable but damaged beyond normal repair, a repair installation that preserves personal files and applications may be appropriate. Use official Windows installation media that matches the installed edition and architecture, and start the installation from within Windows when possible so the repair-install option is available. Reset this PC can remove applications and settings, and some reset choices remove personal files. Do not select a destructive reset, clean installation, or disk format until your important data is backed up and hardware tests do not indicate failing RAM or storage. Use `Reset this PC` only after less destructive repairs fail and you have decided what to do with your files. If BitLocker, partition errors, repeated memory failures, a physically damaged drive, or an uncertain motherboard fault is involved, professional service is safer than repeating boot commands. Take the stop code, recent changes, test results, and backup with you; that information can shorten the diagnosis. ## Conclusion Begin with a backup, disconnected new hardware, update removal, System Restore, and Startup Repair. If those fail, continue with Safe Mode, boot-configuration repair, SFC, and DISM, then test RAM and storage before choosing a reset or reinstall. Seek professional help when the Windows drive is unreliable, memory tests fail, or the hardware fault is uncertain. ## Frequently Asked Questions ### Can BAD\_SYSTEM\_CONFIG\_INFO delete my files? The blue screen itself does not normally delete personal files. Repeated forced shutdowns, a failing drive, or destructive recovery options can put them at risk, so back up important files before making repairs. ### Should I delete the registry files in System32\\config? No. Deleting registry files can prevent Windows from starting and make recovery harder. Use update removal, System Restore, Startup Repair, Safe Mode, and offline system-file tools instead. ### What if Windows will not enter Automatic Repair? Start from Windows installation media, choose \`Repair your computer\`, and open \`Troubleshoot\` > \`Advanced options\`. If the Windows drive is missing there, check storage connections and hardware before running repair commands.