Download auto-deletes?

[khobar]

I just downloaded BackyardNikon, and when I attempt to run the setup file, I get a security warning about verifying publisher, then an error about not being able to access a device, and then the file auto-deletes? Why is that happening?

Running Windows 10 with Panda Security.

[astroman133]

Try temporarily disabling your anti-virus software. The A/V software may be deleting the setup file because it does not know what it is and it is not signed.

[khobar]

Thanks for the quick reply!

I downloaded the setup file to a network server, then copied it from there to my "C:" drive. Windows complained about admin privileges. I clicked "OK" and it copied. I was then able to install.

I am guessing my local "Downloads" directory is somewhat quarantined by security software and that's why the file was getting trashed.

[s3igell]

AV Software use numerous heuristics to "grade" a file - especially an EXE - as "Virused" or "Suspect"/"Untrustworthy" and in need of either Deletion or (more likely) Quarantine.  Unfortunately one of these parameters is "Frequency of Encounter or Use" by that AV Product.  "Boutique Applications" such as BYN Installer EXE's rarely reach the "Frequency of Use" such as to earn a "Trustworthy" grade, and depending on your AV Product is usually either Quarantined (moved to a Hidden Directory where you have to "Ask" the AV Product to let you use it) or outright Deleted.  (Often this behavior requires one to CAREFULLY read the Dialogs which the AV Product pops-up.)

[astroman133]

Perhaps the "deleted" files have only been quarantined by the A/V software.

[khobar]

I expected the A/V software to tell me it was quarantining the file or give some indication it was handling it. Then I would have known. When I dbl click the setup file in the download folder, Windows plays a chime with a popup that says, "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access them." The reason the popup appears is the file is deleted as soon as I double clicked on it. I have never seen that behavior before. 

The good news is that after putting the file in my "C:" directory I was able to install and all is good.