How to repair windows system32 config system from recovery console

Your computer restarts. Fixes to try: Restart your computer. Restore the Desktop folder. Create the missing Desktop folder. Check Desktop location through Registry Editor. Restore your computer. Reinstall Windows System 32 error is mainly caused due to corrupted registry, Virus, malware. For eliminating this problem it is always advised to create system backup regularly or you can use computer maintenance tools for getting permanent resolution.

Using System Restore Log in to Windows using an administrator account. Turn on the computer and press the F8 key repeatedly when the first logo screen displays.

A Windows startup screen displays. If the error message displays again, skip to the step to Recover the computer. Windows failed to load because a critical system driver is missing or corrupt. Browse to the System32 folder. Right-click it and select Properties. Click the Security tab.

Click the Advanced button. Click OK. Select Task Manager from the options available on your screen. Find the process named Windows Explorer, right-click on it, and select End task.

There are 2 methods with which you can do this: Close the Command Prompt as well as any other running programs. Find the System32 folder and delete the files or the entire folder. The System32 folder opens at startup because of a corrupt registry value.

Search for Command Prompt, right-click the top result, and select the Run as administrator option. Confirm the command results:. Type cmd in the run box. Hence type the below command instead of the one you are trying and check if you get the error. Regards, Manasa P — Microsoft Support. Joey Please help. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

I have the same question Report abuse. Details required :. Cancel Submit. What system recovery is that you are trying to run? If you are trying to follow Microsoft article KB to resolve a non booting issue and a system file missing or corrupt message, I would recommend you read and apply this first and you may find that KB is unnecessary: Was the issue preceded by a power interruption, aborted restart, or improper shutdown?

These can cause corruption in the file system which must be fixed before you do anything else. If any of those events have occurred or even if they have not occurred , you should verify the integrity of your file system before doing anything else especially "trying" things. It makes zero sense to start trying to copy files around on a hard disk that has a corrupted file system so this must be fixed first using the XP chkdsk program, and running chkdsk may resolve your issue entirely. Use the XP Recovery Console to verify the file system on your HDD and correct any problems and then try to boot your system - this may be all you need to do.

Or, you are welcome to just start trying things that might work. This is not the same as any recovery disks that might have come a store bought system.