Fix: “…\windows\system32\config\system is missing or corrupt” in Windows 10
There are a plethora of system errors that can completely destabilize your system’s performance or even prevent it from starting. And, while some errors are just horrific at the first sight (BSODs), they can be, more or less, addressed with moderate ease. However, when something is as serious as the failed loading of the System32 configuration file — things get a lot harder to deal with.
If you restarted your PC and there’s still the “Windows could not start because of the following file \windows\system32\config\system is missing or corrupt” prompt, make sure to check the steps we provided below. Of course, as a side note, none of the steps we enlisted will help in case your HDD is faulty.
Fix: Windows could not start because of the following file \windows\system32\config\system is missing or corrupt
- Use a recovery drive
- Use a bootable system installation drive
- Scan for HDD errors
- Run SFC and DISM
- Export your data and perform a clean reinstall
1: Use a recovery drive
The first solution we can recommend when something as critical as the registry corruption occurs is to use a recovery drive. If you have an alternative Windows 10 PC at your disposal, this shouldn’t be an issue. Besides the fully functional Windows 10 PC, a USB stick drive is a must. With those two, you should be able to create a Recovery drive.
- READ ALSO: Top 6 antivirus with data recovery for 2018
Users who experienced this massive system disrupt had a little luck with the auto-repair function. So, a manually inserting a recovery drive might be the best way to resolve the issue. However, there’s one small problem. Namely, since you’re, obviously, unable to make the system load, you can’t disable a Fast boot.
This can be an issue as you’ll have a hard time entering the Boot menu or BIOS (UEFI) settings with the Fast boot ON. In order to avoid this, restart your PC 3 times in a row and it should boot automatically in BIOS settings. Once there, choose to boot from the Recovery drive and you should be good to go. Also, if available, enable Legacy USB option in the BIOS settings menu.
Here’s how to create and use Recovery drive to fix the error at hand:
- Plug in your USB flash drive in the fully functional Windows 10 PC.
- In the Windows Search, type Recovery and choose “Create a recovery drive“.
- Follow the instructions until you’ve created the Recovery drive.
- Plug in the USB in the affected PC and boot from the drive. It should boot automatically.
- Choose Refresh your PC or some other recovery option and run it.
- Once the process is finished, the error should be gone.
2: Use a bootable system installation drive
Now, when an error like this occurs, we can say with certainty that the system is beyond the repair without the external drive. The first solution referred to Recovery drive but that might or might not work for various reasons.
On the other hand, you can always use the USB stick to create a bootable drive with the Windows 10 installation. Just, instead of installing the system, you can choose to repair it accordingly.
Now, the sole creation of the installation media is as simple as they come. Besides the obvious alternative PC (doesn’t have to be a Windows 10 PC), you’ll need to USB drive of at least 6GB of free storage space and the Windows Media Creation tool. Follow the steps we provided below to create and utilize the installation media to fix the critical registry error:
- Download Media Creation Tool from this link.
- Plug in the USB flash drive with, at least, 8 GB of storage space.
- Run Media Creation Tool and accept the License Terms.
- Select ”Create installation media (USB flash drive, DVD, or ISO file) for another PC”.
- Choose the preferred options and click Next.
- Media Creation Tool will download the setup and copy the installation files onto the USB flash drive.
- Now, you should tend to back up your data. Finally, restart your PC.
- In the initial boot screen press F10, F11, or F12 to access the Boot menu. It differs depending on your motherboard.
- Click on Repair and choose one of the available recovery options.
If this doesn’t help, make sure to stick with the USB installation media. It’s mandatory for the next enlisted steps.
3: Scan for HDD errors
Now, we already have stressed the hardware as the possible culprit. This is, at the first sight, just a critical corruption of the essential registry files (really big deal but repairable). But, beyond the threats of possible virus infection or misuse, there’s also a potential problem with the HDD failure. In order to find out whether the HDD has let you down or is still working, you can use third-party bootable tools or open the elevated command-line and try that way.
By running the “chkdsk” command, you should be able to see the state of your HDD and maybe even fix some corrupted sectors. If you’re not sure how to access the Command Prompt when the PC won’t boot, follow the steps below:
- Boot from the installation media an choose Repair your computer.
- Open Troubleshoot.
- Select Advanced options.
- Choose Command Prompt.
- In the command-line, type the following line and press Enter:
- chkdsk /f C:
- After the HDD is scanned for errors, restart your PC.
4: Run SFC and DISM
If you’re still in the elevated command-line under the recovery options, make sure to stay there for a little while. Even though it’s a long stretch, there are two command tools you can run and fix the occurring error.
- READ ALSO: Fix: DISM failed on Windows 10
The first tool is SFC or System File Checker. It’s used to confirm the integrity of the essential system files. In case they get corrupted, it should be able to fix them. Here’s how to run it in a few simple steps:
- In the command-line, type sfc/scannow and press Enter.
- Wait for the procedure to end, restart your PC and look for changes.
Furthermore, if SFC fails, you can always turn to DISM (Deployment Image and Servicing Management tool). This tool has the upper hand over the SFC as it uses additional resources (Windows Update or external installation media) to completely replace the affected files. These instructions should show you how to run this utility via the command-line:
- In the command line, type the following line and press Enter:
- Wait for the procedure to finish (it might take up to 10 minutes) and restart your PC.
5: Export your data and perform a clean reinstall
Finally, if none of the previous steps worked for you, but you’re 100% positive that hardware isn’t the problem, the reinstallation stands as the final step. Make sure to export your data before moving to the reinstallation. As one would suspect, this error mostly occurred on the upgraded versions of Windows 10. Sometimes the things mixed up between the two system iterations and it’s rather hard to repair the damage.
- READ ALSO: How to Reinstall Windows 10
If you’re not sure how to perform a clean reinstall (we already explained how to make a bootable USB drive), follow the steps below:
- Backup your data from the system partition.
- Plug-in USB or insert DVD with the Windows 10 installation.
- Restart your PC and enter boot menu. Choose to boot from the installation media.
- Wait until the installation files load and choose Install now.
- Select preferred settings and choose the Custom install.
- Format system partition and highlight it for installation.
- Your PC will restart a few times and, after that, you should be looking at the brand new and faultless Windows 10.
RELATED STORIES YOU SHOULD CHECK OUT:
- FIX: File System Error 1073741515 in Windows 7, Windows 10
- Fix Windows 10 error “Overlap: Duplicate ownership for directory”
- How to fix File System error 1073545193 on Windows 10
- Fix: eight fixes to ERROR_IMAGE_SUBSYSTEM_NOT_PRESENT
Firefox has announced that it will start to warn users if they visit any breached sites. This is in an attempt to not only make […]
Oh dear. It’s been a pretty bad month for Microsoft concerning its Windows 10 October 1809 Update release. Microsoft eventually released the update a couple […]
Yesterday, Microsoft released Visual Studio 15.9. With it came the announcement that “developers now have the officially supported SDK and tools for creating 64-bit ARM […]