Cleanmgr won't run - how to empty winsxs

0

Many posts on the web re:cleanmgr say it requires Desktop Experience, and some that just say copy the two cleanmgr files to System32 (two destinations).

cd C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr....
copy cleanmgr.exe %windir%\System32\
copy cleanmgr.exe.mui %windir%\System32\en-US\
pause

I can't install anything as my disk is nearly full. Unless Desktop Experience has a 0KB footprint it is not an option. I copied the two files as directed on other posts. The program runs w/o displaying an error but nothing happens. I do not see the dialog box for choosing the drive letter as I see on Win7.

All I really need to do is clean up winsxs which keeps growing over time and filling up my C:\ drive.

How do I empty winsxs? Or anyone recognize the cleanmgr not doing anything?

This problem is on a production Windows Server 2008 R2 x64.

rheitzman

Posted 2014-10-06T16:50:10.480

Reputation: 165

Question was closed 2014-10-06T17:43:05.090

1You do understand the winsxs folder is more or less vital to the operation of Windows right? If you get rid of it then Windows cannot repair itself. – Ramhound – 2014-10-06T17:04:53.307

Well, whatever CleanMgr does I want to do the same thing w/o installing the Desktop Experience. My guess is winsxs is a cache created by NGEN. I'd also guess that over the years some, if not most, of the files are obsolete. A SWAG would be that if all the files were deleted .Net would rebuild them as needed. On the next NGEN run it would rebuild the current set - No? – rheitzman – 2014-10-08T22:09:16.847

Winsxs is way more than a cache for ngen – Ramhound – 2014-10-08T23:01:07.600

Well, I'm not sure enabling the Desktop Experience would actually take any additional disk space, but unfortunately cleanmgr.exe seems to need to copy %WINDIR%\system32\dism into a new directory in %TEMP% every time you run it ... – SamB – 2015-09-18T00:55:36.787

No answers