New
#10
From the Administrative Tools menu after searching for it in the Start screen. Not only is there no checkbox, but now I notice no "Cleanup System Files" button either.
When I "Run" cleanmgr it the button appears, as does the checkbox; over 5GB freed! Cleanmgr must have some "better" rights when run that way.
Maybe an update to the steps might be prudent, and many thanks..
--Al--
Here's a simple way:
1. Go to My PC
2. Right-click the C: drive to get the context menu
3. Left-click Properties
4. Left-click the "Disk Cleanup" box
It will start calculating and display the Disk Cleanup window, with some items checked.
5. Left-click "Cleanup system files"
It will recalculate and display the Disk Cleanup window again.
Check off any items you want to delete and click OK.
Answer "Yes" to the confirmation screen.
It will display a cleaning-up progress screen.
All done!
Note: the "More Options" tab at the top of "Disk Cleanup" is best left alone for now. :)
Hello Al,
Please post some screenshots showing step by step what you see versus what's in the tutorial to see what the issue may be. :)
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
I had this problem, just used this to change ownership of it https://www.tenforums.com/tutorials/3...dows-10-a.html
Much appreciated, I'm having the same problem in 10162 only it's the Windows Telemetry that's buggering things up this time. I'll give that a go.
Thanks for this tutorial, but this only seemed to partially delete this folder. I've tried all options, and only the first couple have made a difference. When I tried the second option, it would say 'access denied' for a lot of files. The third option would just say "This folder isn't empty." I've made a thread of this issue if you need more information, but how would I bypass this?
I ran Disk Cleanup a few times and finally my stubborn folders gave in and Windows.old disappeared without my even knowing, I checked this morning and it was gone (it had been there a while from when I upgraded to the RTM build from the last Insider build). A couple of reboots and another couple of rounds of Disk Cleanup may do the trick.