Unable to delete Autoit compiled exe

[MrBedo]

So this is a really strange one. If I compile an AU3 file (using right-click menu), I can delete it, no problem.

However, if I run that exe from within a VMWare virtual machine as a different user (non admin) I can no longer delete the exe. Worse still, I can't edit the permissions on the exe or even take ownership. I should say that I'm a domain admin and have no problem taking over files and folders usually.

I cannot delete the file as the non-admin (VM) user either. The script from which the exe is compiled contains a 'RunAs' command and I cannot delete the exe using the account that command calls either.

The exe doesn't change location at any point during this process.

Can anyone shed any light on this behaviour?

thanks

[MrBedo]

Shutting down the VM resulted in me being able to delete the exe. That suggests that the exe was bein held open but I'd already checked that it wasn't still runnign in the background. I hadn't used any 'wait' commands in the script either.

At least I know how to resolve it now, but I'm still at a loss to explain the behaviour.

[jchd]

Could that be the effect of some AV program? Many of them behave strangely when detecting an AutoIt executable being accessed/run.

[Rich071]

MrBedo,  Not sure if this is the same as your issue since you did not mention using shared folders. But it's worth a shot.

I use shared folders a lot with the VM's. If you run an EXE from a shared folder on the Host, then close the EXE, the EXE will still be held by VMware. On the Host, unlock the file with Unlocker. You will see that the file is being held by vmware-vmx.exe. This is a known problem. Shutting down the VM, as you said, will also release the lock.

You can also create a batch file to auto unlock locked files with Unlocker. Run Unlocker with /? for all the command line options. A couple of common ones, are below.

/S - Unlock the files without showing the GUI

/L - Text file with list of files to unlock.

Hope this helps.

(Edited for spelling)

Edited August 17, 2014 by Rich071

[JScript]

(...) You can also create a batch file to auto unlock locked files with Unlocker. (...)

Or try this in pure AutoIt:

JS

[Rich071]

Jscript,

Thanks for the link, however isn't this a just a little bit overkill, to delete a directory and all it's contents, when the original intent is to kill a single process in memory and delete one file?

I'm sure I will have later use for your script in a complete different scenerio.

Thanks,

[MikahS]

just change the function from deleting a folder to a file..

[Rich071]

I agree, changing to a filename would work. However, why reinvent the wheel, if you have Unlocker installed. It's there with a right click and also in my case, from a compiled batch file, that is in a Utils folder on the taskbar, in the Host, it is easy to get to. Yes, these could be added to a larger script to enhance it but that is a completely different scenerio.

Yes, I love Autoit, in fact, I have done some things, that I wouldn't be able to do without it. I consider it, "One of the best things since sliced bread", but unless I have a need to enhance and include these portions in a larger script or a script with more flexibility, I'd rather not reinvent the wheel.

An after thought, I do have a need for the folder deletion script on a project that I'm currently working on, inside a WinPE session. I will be testing that later today.

I do appreciate all the feedback.

Thanks,

[MikahS]

To each their own @Rich071

Edited August 18, 2014 by MikahS