System32 is regularly cited for displaying in Windows error messages, and with very good reason. System32 is, after all, the directory where many of the most important files in Windows are stored. So why is it so hard to find?

If you’ve ever had a look for the System32 folder on your computer, it’s likely that you’ve been left a bit mystified. That’s because System32 is hidden from the casual user. The folder is set to invisible unless you specifically request that hidden items be shown. Microsoft has added this function to ensure that a stray user doesn’t go messing with the core files and data that resides in the System32 folder. Pretty wise when you consider that some of these files becoming corrupt will leave you locked out of Windows altogether!

You can access the System32 directory in two different ways depending on what type of Windows operating system you’re using.

For most standard versions of Windows, you can use:

C:\Windows\System32

But for Windows NT based systems, you will have to use:

C:\Winnt\system32

Once you gain access to the subfolders and files in this particular directory, and there are a fair few of them, you should only consider making live edits unless you know exactly what you’re trying to achieve. To put it bluntly, the System32 files are extremely volatile.

Most errors acknowledge System32, not because the folder itself has become damaged, but because one of the files within it has been corrupted. Overwriting your entire System32 folder is thus a pretty bad idea but one that occasionally works.

If you have a Windows recovery disk, you can use the Recovery Console to try and kick the System32 folder back in to shape. Once you’ve inserted the disk and opened up the console, enter the following commands:

md tmp

copy C:windowssystem32configsystem C:windowstmpsystem.bak

delete C:windowssystem32configsystem

copy C:windowsrepairsystem C:windowssystem32configsystem

This often fixes System32 based errors, but it isn’t completely reliable. Either way, if you plan on running the commands above, ensure that you get them absolutely correct letter for letter. A bad edit in the Recovery Console at this point is truly more trouble than its worth.

So is there an easier solution? Thankfully there is, but once again it relies on third party tools to automate the process of fixing your System32 directory.

You’ll find plenty of software designed specifically for the chore of fixing bugs and corruptions in the core Windows file libraries. This includes the System32 folder. ErrorSmart is just one of several products that can be downloaded via the Net and used to filter out the bad data on your system.

If you’re not interested in purchasing a third party solution, you can try the age old “Last Known Good Configuration” trick. This involves rebooting Windows and pressing F8 while it loads. You’ll be taken to the boot select screen with a list of options for how you would like to load Windows. Choose the last known good configuration and wait as Windows reloads. This time, the operating system will roll back to the old configurations that it remembers working without hitches. This sounds like the best solution of all, but unfortunately the tool isn’t the greatest for getting rid of core System32 errors.

Get a Free Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)