* AS 7.6.4 - Resolved a problem running .exe file

AS allows faster and more convenient creation of source records for Family Historian.
Post Reply
avatar
rfj1001
Superstar
Posts: 271
Joined: 14 Dec 2003 18:11
Family Historian: V7
Location: Dorset, England
Contact:

AS 7.6.4 - Resolved a problem running .exe file

Post by rfj1001 » 30 Nov 2022 15:11

The exe file wouldn't run as I got a message to say it had been downloaded from the internet and was potentially unsafe.
I had this experience with another exe file, again from a trusted source. This had never happened before

There is a lot of information on the internet giving multiple ways to overcome these messages and none of them worked. Eventually I found that is was nothing to do with file security - it was file length.

Thanks to someone else, I found out that when an exe file is decompressed, it creates another directory, of the same name, within the first directory. I'd saved my AS file to my desktop which had quite a long file path so the decompressed directory structure length was too long for win11 and this caused the error.

I moved the AS exe file to C:\temp and it ran with no misleading messages.

Hope this might help someone else.

User avatar
NickWalker
Megastar
Posts: 2401
Joined: 02 Jan 2004 17:39
Family Historian: V7
Location: Lancashire, UK
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by NickWalker » 30 Nov 2022 15:26

I would doubt that is the reason. When you run the executable it does extract to a temporary folder but this wouldn't be on the desktop (unless you have some odd settings on your computer), it would extract it into your c:\users\<username>\appdata\local\temp folder, regardless of where you ran it from.

There are a few suggestions on the knowledge base as to the causes of various blocking issues: https://fhug.org.uk/kb/kb-article/solvi ... l-sources/

I couldn't be sure without seeing the actual message, but in my experience the 'unsafe' message is often because it has the 'mark of the web' and can be resolved by right-clicking on the file, selecting properties and then clicking the 'unblock' button.
Nick Walker
Ancestral Sources Developer

https://fhug.org.uk/kb/kb-article/ancestral-sources/

avatar
rfj1001
Superstar
Posts: 271
Joined: 14 Dec 2003 18:11
Family Historian: V7
Location: Dorset, England
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by rfj1001 » 30 Nov 2022 15:39

Thanks Nick,

I'd already clicked the unblock box on the AS exe file and that did not work on its own.

My default download is to my desktop - much easier to find for me :)

It might not be the correct explanation as to the problem but it definitely is a solution to that error message that has worked twice for me from safe-sourced exe files.

User avatar
NickWalker
Megastar
Posts: 2401
Joined: 02 Jan 2004 17:39
Family Historian: V7
Location: Lancashire, UK
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by NickWalker » 30 Nov 2022 15:56

I wonder if it is the process of copying and pasting the file that is unblocking it.
Nick Walker
Ancestral Sources Developer

https://fhug.org.uk/kb/kb-article/ancestral-sources/

avatar
rfj1001
Superstar
Posts: 271
Joined: 14 Dec 2003 18:11
Family Historian: V7
Location: Dorset, England
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by rfj1001 » 02 Dec 2022 12:09

As an experiment to see if your thought was correct or not, I copied and pasted the AS exe file back from C:\temp, where it ran successfully, to my desktop. I then tried to run it from there. The original error message came up again.

Screenshot attached for your info.

Screenshot 2022-12-02 120329.jpg
Screenshot 2022-12-02 120329.jpg (19.69 KiB) Viewed 812 times

User avatar
tatewise
Megastar
Posts: 27075
Joined: 25 May 2010 11:00
Family Historian: V7
Location: Torbay, Devon, UK
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by tatewise » 02 Dec 2022 12:23

Did you explore 'Show details' or Why can't these files be opened? which may give clues to help us all understand the cause?
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

User avatar
NickWalker
Megastar
Posts: 2401
Joined: 02 Jan 2004 17:39
Family Historian: V7
Location: Lancashire, UK
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by NickWalker » 02 Dec 2022 12:26

It sounds like something on the computer is preventing the exe from running when it is on the desktop rather than in the temp folder, presumably as a security measure. If moving it elsewhere allows you to install it then that's the solution.

Is your desktop redirected in any way, perhaps on a different drive? This message seems to be related to the old Control Panel->Internet Options settings, almost as if it is treating your desktop as not being a trusted site.
Nick Walker
Ancestral Sources Developer

https://fhug.org.uk/kb/kb-article/ancestral-sources/

User avatar
mjashby
Megastar
Posts: 692
Joined: 23 Oct 2004 10:45
Family Historian: V7
Location: Yorkshire

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by mjashby » 02 Dec 2022 13:32

If this is on Windows 11, it might also be worthwhile checking the 'Smart App Control' setting.

User avatar
NickWalker
Megastar
Posts: 2401
Joined: 02 Jan 2004 17:39
Family Historian: V7
Location: Lancashire, UK
Contact:

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by NickWalker » 02 Dec 2022 13:36

mjashby wrote:
02 Dec 2022 13:32
If this is on Windows 11, it might also be worthwhile checking the 'Smart App Control' setting.
I think you would get a different message from Smart App Control (which would reference Smart App Control) and also I think it would block the application regardless of where it is being run from.
Nick Walker
Ancestral Sources Developer

https://fhug.org.uk/kb/kb-article/ancestral-sources/

User avatar
mjashby
Megastar
Posts: 692
Joined: 23 Oct 2004 10:45
Family Historian: V7
Location: Yorkshire

Re: AS 7.6.4 - Resolved a problem running .exe file

Post by mjashby » 02 Dec 2022 19:51

Nick,

You are probably correct, as the most likely cause of these problems is a 'folder permissions' issue.

The information on how the Windows Smart App Control function works is vague, to say the least, so I felt it would be worthwhile eliminating that possibility, as it's a relatively new function that many Windows users may not have noticed.

Mervyn

Post Reply