Is this what lets programs create files on my windows system that I cant delete? about hcsshim HOT 2 CLOSED

The advice to use docker-ci-zap.exe is correct. It is only "dangerous" in that it will delete anything that you point it at. If you use docker-ci-zap.exe C:\programdata\Docker it will delete the remaining Docker images and nothing else, and is safe to use. If you point it at C:\, well, it's no different than the age old rm -rf / on Linux, and would delete all files on your C drive, hence the label "dangerous".

The files cannot be deleted as they are owned by TrustedInstaller, which is used to protect critical files such as Windows installations, and is the same reason you cannot delete files in C:\Windows\System32\. Docker images on Windows are similar to a Windows install, hence why they are protected by TrustedInstaller. You should be able to take control of the files an delete them without use of docker-ci-zap.exe using methods such as this one. docker-ci-zap.exe is more of a convenience tool to get the correct permissions to delete the files than anything special.

Visual Studio Feedback tool is unrelated to, and does not use this project, though might also use TrustedInstaller.

from hcsshim.

Thanks, for that info. "Dangerous" was someone else's moniker, I was more annoyed with having to use it than worried about side effect.

I guess my problem then is with Docker setting the TrustedInstaller as the owner of the files. Its a service, and those images/files are only critical to it, not the OS that hosts the service. I'll file an issue over there if there isn't one specifically for this.

I found that after a reboot, I could take ownership of some more (but not all) files and delete them. Three more cycles of that and the folder is now gone.

from hcsshim.