{"id":2653,"date":"2017-11-06T21:06:16","date_gmt":"2017-11-06T19:06:16","guid":{"rendered":"http:\/\/blog.hosebei.ch\/?p=2653"},"modified":"2017-11-06T21:06:16","modified_gmt":"2017-11-06T19:06:16","slug":"windows-10-remove-windows-old-folder","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=2653","title":{"rendered":"Windows 10 – Remove Windows.old Folder"},"content":{"rendered":"

Long time no see, huh? Now I’m back with a new post about removing the Windows.old folder after a feature Upgrade.
\nRecently I seen this on twitter, a commented it with: Why don’t you let the automation from Windows 10 let it do. But since then, I was in a project, where the removal of this folder was required, and within the Upgrade Task Sequence. I thought, this is easy, starting the Scheduled Task should do the job…
\n\"\"<\/a><\/p>\n

You can easily start this task within a command line, but since this does not solve the “problem”, I don’t provide this command. But I will provide a more useful information. You can use cleanmgr.exe, yes, this is the “Disk Cleanup” which is included since some versions of Windows:
\n\"\"<\/a><\/p>\n

But this is a GUI, how can we use this within in TS? I used my prefered search engine, and found a solution. You can create a Cleanup Profile, save this to registry, and then run the profile from command line. Seem cool? Here are the steps:
\nGo ahead, and start cleanmgr.exe with the following parameters:
\ncleanmgr.exe \/sageset:1703<\/code>
\n\"\"<\/a>
\nThe parameter sageset instructs the cleanup wizard to save the selected options to the registry. The following number after the parameter sets the profile ID, or number, with which the settings are stored. The Number can be from 0 to 65535, so there might be enough numbering possible.<\/p>\n

As soon as the wizard is loaded, you can select all the options you want to include within the cleanup, in my case, I only selected “Previous Windows Installation(s)” as shown in a print screen above. After a click on OK, the wizard writes this settings to the registry under “Computer\\HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\VolumeCaches”, per each setting:
\n\"\"<\/a>
\nAs you can see on the previous picture, every setting from the wizard has a corresponding key within the registry. So if you have selected “Previous Windows Installation(s)”, you will find a new entry under “Previous Installations”, in my case named “StateFlags1703”, where the number from the parameter is represented:
\n\"\"<\/a><\/p>\n

Now you can export this, and import it within the Task Sequence, oder just write it through Powershell with the following command:
\nNew-ItemProperty -Path \"HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\VolumeCaches\\Previous Installations\\\" -Name \"StateFlags1703\" -Type DWORD -Value 2<\/code><\/p>\n

When this is done, you only need to call cleanmgr.exe with the “sagerun” parameter, and the not (?) documented silent parameter:
\ncleanmgr.exe \/sagerun:1703 \/S<\/code>
\nWithout the \/S parameter, the GUI will show up and requires you to press OK, what will not work within a TS.<\/p>\n

Hope this helps, and deleting the windows.old folder, I still recommend to do only if required, otherwise let the scheduled task do the magic.<\/p>\n","protected":false},"excerpt":{"rendered":"

Long time no see, huh? Now I’m back with a new post about removing the Windows.old folder after a feature Upgrade. Recently I seen this on twitter, a commented it with: Why don’t you let the automation from Windows 10 let it do. But since then, I was in a project, where the removal of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,41,43],"tags":[],"class_list":["post-2653","post","type-post","status-publish","format-standard","hentry","category-operating-system-deployment","category-updates-management","category-windows-10"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2653","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2653"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2653\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2653"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2653"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2653"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}