SOLVED - Can't build app because Aut2exe folder keeps getting set to read-only

[Mbee]

Every time I try to build an app (using Tools -> Build in SciTE), I get the following error message:

Aut2exe.exe ended with errors because the target exe wasn't created, abandon build. (C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe\~AUFA27.tmp.exe)rc:2

It turns out that this is a result of the folder "C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe" constantly being set to read-only by some mysterious "force" that I know nothing about and certainly did not request.  For when I manually change the folder attribute to remove the read-only status, the build runs perfectly. Once. Then it inexplicably (and automatically) gets set back to read-only again!

What's going on?

As for a work-around, is there some environment variable or whatever I can alter in order to change the Aut2exe work folder?

 

I'm running 64-bit Windows 7 Pro SP1 with the latest version of AutoIt.

 

Thanks!

Edited January 24, 2016 by Mbee
Problem now solved.

[computergroove]

Does the issue happen if you change the location of aut2exe to a location outside of the c:\user directory?

[mLipok]

This mysterious is your AV software 

Add 

"C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe"

To exceptions.

 

[EmilyLove]

  On 1/23/2016 at 3:11 AM, Mbee said:

Every time I try to build an app (using Tools -> Build in SciTE), I get the following error message:

Aut2exe.exe ended with errors because the target exe wasn't created, abandon build. (C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe\~AUFA27.tmp.exe)rc:2

It turns out that this is a result of the folder "C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe" constantly being set to read-only by some mysterious "force" that I know nothing about and certainly did not request.  For when I manually change the folder attribute to remove the read-only status, the build runs perfectly. Once. Then it inexplicably (and automatically) gets set back to read-only again!

What's going on?

As for a work-around, is there some environment variable or whatever I can alter in order to change the Aut2exe work folder?

 

I'm running 64-bit Windows 7 Pro SP1 with the latest version of AutoIt.

 

Thanks!

Expand  

Add this line to the top of any scripts that have this issue.

#AutoIt3Wrapper_Run_Before=attrib "%LocalAppData%\AutoIt v3\Aut2exe\*" -R /S /D

This will remove the read-only flag from the "%LocalAppData%\AutoIt v3\Aut2exe\" folder when you compile.

You may also want to run SciTE as Administrator from now on. Otherwise, it may not have permission to remove read only flag when it tries to compile.

Edited January 23, 2016 by BetaLeaf
Changed to using %LocalAppData% since this is default.

[Mbee]

  On 1/23/2016 at 6:40 PM, mLipok said:

This mysterious is your AV software 

Add 

"C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe"

To exceptions.

Thanks, mLipok!  You are exactly correct!  Add that to the multiple reasons I don't much like my Panda Antivirus Pro 2016 software very much (but the others I've tried recently have had even worse problems -- time to go back to Avira, I guess).

Nice job!

 

Expand  

 

[mLipok]

You're welcome!

mLipok

[NightHawk56]

Thanks mLipok! It worked for me too 

Adding an exception on Windows running the default Microsoft AV:

1. Open Windows Defender Security Center.
2. Click on the Virus & threat protection icon.
3. Click on the link Virus & threat protection settings.
4. Scroll down to Exclusions and click on the link Add or remove exclusions.
5. Click on the button Add an exclusion.
6. In the drop down menu select Folder.
7. Navigate to "C:\Users\usrname\AppData\Local\AutoIt v3\Aut2exe".
8. Click on the button Select folder.

Edited October 23, 2018 by NightHawk56

[Skeletor]

@NightHawk56, Please read the forum rules before posting. 

[mLipok]

@NightHawk56 I'm glad it was helpful. And thanks for the HowTo for "Windows Defender".