Windows 11, announced with the slogan ‘Next generation Windows’ and released on October 5th, came with many innovations. One of the biggest design changes was the centering of the start menu on the taskbar. Microsoft has also introduced Android support for its operating system, revamping the user interface of system applications, especially settings and the Microsoft Store.
The output of Windows 11 was not entirely perfect. Microsoft, which made a bad impression at the beginning of the road due to a performance problem on computers with Ryzen processors, solved the problem in partnership with AMD, but still could not make the operating system ‘error-enabled’.
Windows 11 and its new problem: Hollow folders
Since 2019, the problem of ‘self-empty folder creation’ reported by Windows 10 users has resurarned with Windows 11. Hundreds or even thousands of completely empty folders are created in the System32 directory of the operating system, MSPowerUser reported. It is not known how or why they occurred out of the blue.
Looking at the extension of folders, it seems that they are Temp files based on the concept of tmp. In Task Manager, you may have thought at first glance that a virus created the folders that are indicated to be used by the ProvTool.exe tool named Provisioning Package Runtime Processing.
Photo: MSPowerUser
But you don’t have to worry. Self-contained folders are not a precursor to any malware. It also has no negative performance impact on the Windows 11 operating system. You can use your computer normally without sacrificing the performance of your processor, RAM, and other hardware.
The problem has been around since Windows 10
Folders that are not known why they occur are not specific to Windows 11. It is having an effect even in the Windows 10 operating system, which was released in 2015. In Microsoft forums, users report that more than 2,000 hollow tmp folders have been created in the computer’s System32 directory. The company also failed to find a significant solution to the problem in Windows 11.
Of course, if we consider that Windows 11 is very young, we can tolerate the problem somewhat. With future updates, the issue can be completely obsolet and still persist.
