#Purging windows update cleanup stuck full
#Purging windows update cleanup stuck windows 10

HDD usage on the Windows guest (most time between 2% and 15% when cleanmgr was working, with pikes of 28%).HDD usage on the Linux host (near 0% when cleanmgr was working, with pikes of 2%), Linux disk cache is really great avoiding dato be sent to real disk.CPU usage on the Linux host and on the Windows Guest (most time between 0% and 1%, with pikes of 5%, no more).I am afraid that cleanmgr is doing something on the windows registry per each file it deletes (accessing the registry is very low). Test2: Having the 24GiB virtual disk on the Linux host RAM Test1: Having the 24GiB virtual disk on the physical harddisks

#Purging windows update cleanup stuck windows 10

Guest: Windows 10 Home with 16GiB of ram and a Virtual disk of 24GiB.

Host: Linux 64bits distro over a hardware that main parts are AMD Deca Core 5GHz with 64GiB of RAM and a Sata Raid0 controller with two WD VelociRaptor HDDs (able to sustain a combined secuential write speed of near 1GiB/s and a 4K random write of 300MiB/s) cost is >ten thousand euros.

Yes, if i put the virtual disk totally on RAM, cleanmgr time does not drop but if i manaully delete the files, that time drops down just a little (Linux write cache is great when you have 64GiB of RAM on it).

#Purging windows update cleanup stuck full

The delete it self can go so fast since the host is a Linux, that speed is caused just because Linux caches all writes to the fixed size file that is used as the disk on the virtual machine (24GiB), and since i have 64GiB of RAM and i let to the Windows 16GiB it does not need to use SWAP neither PAGEFILE.SYS also more, Linux can hold the full file on RAM (i tested with that file on RAM and delete times go done a lot, but cleanmgr time does not drop down). So deleting the files is not the botle neck (the delete itself only need five minutes but cleanmgr takes more than eight hours). Please note i rebooted onto Linux SystemRescueCd just to be able to list all files, also the ones looked by Window and also to do such listing as fast as possible (no acl check, etc).ДЄlso please note that on cleanmgr i only count only time after search ends (the search itself also tooks more than six hours). to delete such files in an admin command prompt (cmd) and take note of the time (less than five minutes)

Reset back the inmutable virtual machine.

List all files on disk to another log file (less than a minute).

Reboot onto SystemRescueCD and mount the windows partition.

Let cleanmgr do its job and take note of the time (more than eight hours).

List all files on disk to a log file (less than a minute).Boot a SystemRescueCD and mount the windows partition.Just to put fire on the question, i had done on an inmutable virtual machine the next steps: