In the wake of playing out a set up redesign on a Remove Windows.old Server 2012, you will track down a WINDOWS.OLD folder in the foundation of C:. This folder will have a reinforcement of your old program records, appdata and Windows folder… in the event you really want to return or recuperate something that could have been lost during the overhaul. At the point when you attempt to erase it however you are told you don’t have consents. Simply a little point here, it is for the most part not prescribed to do in that frame of mind on servers.
Subsequent to playing out a set up overhaul on a Windows.old Folder Windows 11, you will track down a WINDOWS.OLD folder in the foundation of C:. This folder will have a reinforcement of your old program records, appdata and Windows folder… in the event you want to return or recuperate something that could have been lost during the redesign. At the point when you attempt to erase it however you are told you don’t have consents.
On certain crates I simply utilize my scortched earth strategy of evening out the segments and beginning without any preparation – others I will do an introduce and utilize a similar parcel. You receive the accompanying feared message – which you excuse and continue on.
There is no such thing as tragically, that Disk Remove Windows.old Server Full GUI introduce, except if you add Desktop Experience. Dread not. Whenever you have affirmed you don’t really want anything from that old c:windows. old directory structure, you can physically erase it, with a tad of additional work.
Here’s how you do it.
1) Download Junction.EXE from Sysinternals. I removed and saved it to c:source. You will utilize this tool to produce a rundown of the multitude of intersections that must be removed.
2) make a reference document that rundowns all the intersection focuses and representative connections being used by opening up an order instant, changing into C:source and running
- junction.exe – s – q c:windows.old >junctions.txt
3) open up PowerShell ISE administrator privileges and run the accompanying content to Remove Windows.old Server 2012 every emblematic connection and intersection focuses in c:windows.old.
- foreach ($line in [System.IO.File]::ReadLines(“c:sourcejunctions.txt”))
- if ($line – match “^\\”)
- $document = $line – supplant “(: JUNCTION)|(: SYMBOLIC LINK)”,””
- & c:sourcejunction.exe – d “$file”
You ought to get the accompanying looking by…
Presently it’s some basic taking of possession, allowing freedoms and erasing windows.old to get your space back.
4) to take possession use
- takeown/F C:windows.old/R/D Y
5) erase c:windows.old – you currently have authorizations and possession.
How much space you get back will change in view of your specific circumstance. My last run at this saved me 15.5 GB of room on my OS drive.
How do I clean up Windows Server 2012?
Windows Server 2012: Enabling Disk Cleanup Utility
- Open The Roles and Features Wizard.
- Click on Add job and Feature.
- Pick establishment Type.
- Click Next the whole way to highlights.
- Continue with the establishment and Reboot.
- Confirm that the Utility is without a doubt introduced.
- Plate Cleanup in real life.
In the pursuit box on the taskbar, type settings, then pick it from the rundown of results. Select System > Storage > This PC and afterward look down the rundown and pick Temporary documents. Under Remove transitory documents, select the Previous form of Windows check box and afterward pick Remove records.
However, it’s not the situation in Windows Server, particularly the later forms like Remove Windows.old Server 2012. You presumably could empower Desktop Experience element to bring back the Disk Cleanup Utility yet it won’t ensure to tidy up these two monster folders oversaw by the framework overhauls and updates.