What Is the $WINDOWS.~BT Folder?
When you initiate a Windows 11 upgrade from Windows 10, or when a major feature update is deployed via Windows Update, the setup process requires a place to store downloaded installation files before they are applied to your system drive. This location is typicallyC:\$WINDOWS.~BT. The "BT" stands for "Build Tree," which refers to the structure of files required to build the new operating system image on your hardware.
This folder contains critical components such as drivers, system libraries, and configuration files necessary for the installation process. If the installation fails halfway through, Windows uses these files to attempt a repair or to revert the changes made so far, ensuring your computer does not end up in a broken state. Because it holds such vital data, it is not a standard user folder and should not be modified manually while the system is running.
Why Does It Persist After Installation?
Many users are surprised to find that the$WINDOWS.~BT folder does not disappear immediately after their Windows 11 installation completes. This persistence is intentional. Microsoft leaves the folder in place to allow users to uninstall the recent update or downgrade to the previous version of Windows within a specific timeframe. Typically, you have ten days from the completion of the upgrade to perform this rollback.
During this period, if you encounter driver conflicts, application incompatibilities, or severe performance issues related to the new OS version, you can use the "Go Back" option in the Recovery settings. This function relies entirely on the data stored within C:\$WINDOWS.~BT. Once the ten-day window closes, or if you explicitly choose to remove the old Windows installation, the system will delete this folder to reclaim disk space. Until then, it serves as a crucial backup mechanism for system integrity.
Can You Safely Delete It?
Deleting the$WINDOWS.~BT folder manually using File Explorer is generally discouraged because it may result in permission errors or leave behind orphaned files that do not free up the expected amount of space. Furthermore, deleting it prematurely removes your ability to roll back to the previous Windows version, which could be risky if you discover critical bugs in the new update. However, if you are certain you want to keep Windows 11 and wish to recover the gigabytes of storage it consumes, there are safe methods to do so.
The recommended approach is to use the built-in Disk Cleanup utility. This tool recognizes the folder as part of the Windows Update cleanup process and handles the deletion safely, including clearing out the associated registry entries. Alternatively, if you are comfortable with command-line tools, you can use the dism command to clean up component stores, though Disk Cleanup is more user-friendly for most scenarios.
To use Disk Cleanup:
- Press
Win + Sand type Disk Cleanup, then open the app. - Select your system drive (usually
C:) and click OK. - Click the button labeled Clean up system files. You may need to confirm administrator privileges.
- Re-select the
C:drive if prompted. - In the list of file types, check the box for Previous Windows installations.
- Click OK and then Delete Files to proceed.
$WINDOWS.~BT folder and any other temporary installation files, freeing up significant space on your hard drive without compromising your current Windows 11 installation.
Related Configuration Tips
If you are managing your Windows 11 environment extensively, understanding how to handle system resources and peripheral connections is also important. For instance, configuring key bindings can help streamline your workflow just as much as managing disk space does. You might find our guide on Control volume with key bindings in Windows 11 useful for optimizing input methods. Similarly, if you are setting up development environments or specialized hardware, knowing how to manage serial ports can prevent connectivity issues later on. Check out How to Install pyserial Module and Handle Serial Port Connections in Windows 11 for detailed instructions on handling COM port interactions in Python applications.Frequently Asked Questions
Is it safe to delete the $WINDOWS.~BT folder using third-party cleaners?
While many third-party cleaning tools claim to remove this folder, they often lack the precision of native Windows utilities and may delete necessary files incorrectly. It is safer to stick with the built-in Disk Cleanup tool or the Storage Sense feature, which are designed specifically to handle Windows installation remnants without causing system instability.
How much disk space does the $WINDOWS.~BT folder typically occupy?
The size varies depending on the version of Windows you are upgrading from and the features included in the update, but it commonly ranges between 4 GB and 8 GB. In some cases, particularly with larger feature updates, it can exceed 10 GB, making it one of the largest temporary folders on a typical Windows partition.
Can I move the $WINDOWS.~BT folder to another drive?
No, you cannot move this folder to another drive. It is hardcoded into the Windows Setup process to reside on the root of the system drive where the operating files are located. Attempting to rename or relocate it will likely cause the update process to fail or prevent the system from rolling back correctly.
Why does my antivirus flag the $WINDOWS.~BT folder?
Some antivirus software may flag this folder due to its contents, which include executable files and scripts similar to those found in malware. However, since it is created by the legitimate Windows Update service, it is safe. You should add an exception for C:\$WINDOWS.~BT in your antivirus settings if it causes false positive alerts.
What happens if I run out of space while the folder exists?
If your drive becomes critically full while the $WINDOWS.~BT folder is present, Windows may struggle to perform routine maintenance tasks or create new system restore points. It is advisable to delete the folder using Disk Cleanup as soon as you are confident your Windows 11 installation is stable to prevent potential performance degradation.