Very often, users of computers and laptops on which Windows systems are installed blindly follow the recommendations of "specialists" to clean the system partition of garbage to speed up the OS and notice that the main Windows directory takes up much more space than it was right after installing the OS. One of the largest volumes is the System32 folder. Without thinking twice, users try to get rid of either herself or her contents, completely unaware of what will happen if the System32 folder is deleted. Alas, looking a little ahead, it is worth saying that one should not expect anything good from such actions. Next, let's try to figure out what kind of directory it is, what is in it, and whether it is possible to perform operations related to cleaning the contents.
What is the System32 directory and what files are stored in it: general information
To determine the importance of this directory in ensuring the normal operation of the operating system, you must immediately pay attention to its name. It speaks for itself - it is a system catalog that contains the components responsible for the correct operation of Windows, and on systems with a capacity of 64 bits, its additional function is to enable 32-bit applications to be launched.
In addition, among them there are a lot of standard Windows programs and system management tools. But some users find that in 64-bit OSs, very many components of the System32 directory are duplicated in the SysWOW64 directory. So why keep a directory for 32-bit applications on a 64-bit system? This in most cases provokes many to delete the described folder. But this is not so simple.
Can I delete the System32 folder and how to do it?
Indeed, for many uninformed users, the temptation to remove is too great. However, at the first attempt, the system starts to give a lot of warnings about the fact that this directory cannot be deleted or some objects are simply not deleted due to a lock. This, from the point of view of the system itself, is absolutely correct. But this does not stop many. So let's see what can be deleted in the System32 folder. By and large, it is undesirable to touch any of the components present there.
If you really want to clean up the trash that has accumulated there or get rid of possible viruses, it is better to use the standard “C” drive cleaning procedure, additionally indicating the removal of system files. You can also use automated optimizer programs like CCleaner or iObit ASC.
If you really want to completely get rid of this directory, in a working system you must first change the access rights to it, setting yourself as the owner through the properties of the folder yourself. But this technique is not applicable to all files, and some of them will remain on the hard drive.
To completely remove all residual objects, you can use the Unlocker utility, in which, upon detection of a blocking descriptor, the deletion is selected, and possibly the preliminary termination of processes or unlocking access.
You can also boot using removable media on which the LiveCD environment is recorded, and then get rid of the desired directory through the command line. But this operation is quite complicated and may require a lot of time.
But it’s much easier to remove your hard drive, connect to another computer, load the operating system installed on the terminal to which you are connecting, and then get rid of everything unnecessary in this working OS.
What happens if you delete the System32 folder?
We figured out the main actions. Now let's see what happens if you delete the System32 folder. In the case of deletion directly in a running OS, the consequences will affect immediately. You can be absolutely sure that the blue screens will start popping up, and the main system tools launched from the Run console will be unavailable, the hardware will stop working, because this is where the many device drivers are located in this directory, etc. In case of deletion directories when starting from removable media or when connecting a hard drive to another computer when you reuse it on your terminal or laptop, the system will stop loading at all, and recovery may not be possible.
How to restore the system after deleting the System32 directory?
Now suppose that the user has deleted the System32 folder. What to do in such a situation? What tools can bring the system to life? By and large, if you have previously created a workable copy of the system, you can use it, but this applies only to the image, and not to the recovery point, which is stored in the described directory. If the rollback does not start automatically at boot, you can try to restore the system with booting from removable media, and then, if possible, run a full scan of system files from the command line (sfc / scannow).
In some cases, it is advisable to use the initial menu, where you can choose to download the last working copy, and if this does not help, you can try to start with support for the command line and network drivers so that the missing components are downloaded from the Internet. However, there is little hope for this (after all, most drivers from the directory have been removed, and those that remained in the SysWOW64 directory may not work), and usually only a complete reinstallation of Windows helps.
What is the result?
Now, probably, it is already becoming clear what will happen if the System32 folder is deleted, and why it is highly discouraged to do such things. In general, it is worth repeating: if you want to get rid of computer debris completely painless for the system, it is better to use standard cleaning methods or use highly targeted utilities. With their help, you certainly will not harm the operating system. And you can’t delete the directory itself manually under any circumstances!