I noticed I still had the folder created for my 2017.1.0b7 install and went to delete it, however I am unable to. The culprit is the file mono.exe and all attempts to delete the file have failed saying I don’t have access. Initial attempts saying I need administrator permissions to delete the file when I in fact am the adminstrator.
I have tried many things to remove this file, going so far as to attempt TAKEOWN /F <filename> in the admin console with no success.
Did you try rebooting? Perhaps something locking the file.
No change after reboot.
I have experienced this issue as well on b9. Even though Unity was closed, the mono.exe file was still locked. But a restart did fix it for me. This still seems like an issue that needs to be fixed though, a file shouldn’t remain locked after Unity dies.
Could you use Process Explorer to see what’s locking the file? It’s likely it’s machine configuration specific, as we haven’t seen this issue in house yet.
Not sure if what was used was Process Explorer, but my buddy did a search for processes that were touching the file and nothing showed up.
However this isn’t a problem for me anymore because I was able to delete it just a few minutes ago. I haven’t done anything out of the ordinary to actively try to delete the file, I just decided to try and delete it on a whim when I noticed this thread had some responses.
Still bugs me that the cause was not found, and that I won’t really be able to find out on my end anymore.
Your experience did give me a possibility. When I said a reboot did not work, it was because between than and that my post my computer had been shut off and turned back on a few times. However just now when I tried and it worked it was one of the first things I did after turning on the computer.
I am no longer in a position to test this, and I am not too familiar with how applications lock and unlock files, but here is what I came up with. Perhaps the current install of Unity (b8 and then later b9 in their separate folders) somehow locked both its own and the b7 mono.exe. Then when closing unity, it would only unlock the mono.exe in its own directory.
Windows automatically unlocks files when the process that was locking them is terminated. Something must have been actively using that file - perhaps some kind of anti virus software?