TeraByte Unlimited

The mount folder itself should have the same permissions as where it exists. The program doesn't set or assign any special permissions for it. In most cases, the cleanup attempt can remove any lingering files. Usually, permissions on build-specific files (like InitScript.cmd) are normal administrator level and can be handled using an administrator command prompt. I would guess the file was in use or locked by something on the system when the first unmount was attempted. This might happen if it was accessed while the build was being created or paused, for example. Aside from that, the mounted folders (like \Windows\System32) and system files do have very restrictive access by default (just as the installed Windows files do), which can create difficulties if the normal cleanup fails.

I mentioned a cleanup attempt in my previous post, but it may not try it in certain situations. If you get a chance, can you check the log and see if a cleanup was actually attempted? It would log "Performing cleanup" (assuming English version). Also, were any warnings logged?