We are using Thinstall 4.7.3 to build apps that may have been captured in an earlier version of Thinstall.
When our app exits, Thinstall starts up its sandbox cleanup program, which is unfortunately identified by the name of one of our apps when using ProcExp.exe. It manages to clean up much of %APPDATA%\Thinstall\SandboxName, but gets hung in a loop when cleaning %SystemRoot%, because it cannot remove the 'assembly' directory, which is marked as System and ReadOnly by either Thinstall or the OS on Thinstall's behalf. The assembly directory is indeed empty. The only problem is the incorrect attributes on the assembly directory. THe sandbox removal process is stuck in a loop where it:
calls CreateFile to get a handle to the assembly directory
calls QueryAttributeTagFile
calls SetDispositionInformationFile, but is told that the 'attribute' dir cannot be deleted
calls CloseFile
(and loops endlessly, hoping things will change)
It would seem that it was Thinstall that created this sandbox. So Thinstall should be able to remove it properly, but is seemingly unable to do so!
This is seen on WinXP and Win7. Probably Win8 as well, but I haven't looked yet.
Is this a bug? Is there a fix?
We have somewhat of a work-around to have a program that runs before our app is started, out of a command file that afterwards launches our thinstall-virtualized application. But then, what point is 'RemoveSandboxOnExit'?
Best regards,
George Byrkit