This app can't run on your PC

Started by chrislegarth, February 25, 2025, 08:36:18 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

chrislegarth

February 25, 2025, 08:36:18 AM
I'm grasping at straws so I'm looking for any thoughts...

I have several programs that are run directly off our network NAS.  When they are run from computers on the network, they work without issue.  However, if the computer is connected through the VPN or off a Microsoft AVD, they randomly and frequently get the blue This app can't run on your PC error or other DLL errors.  I've been attributing this to the VPN connectivity but as more and more staff connect remotely, it is becoming an issue.

Any ideas?

...and as always THANKS!

td

#1
February 25, 2025, 08:49:10 AM
By "programs" are you referring to compiled WinBatch scripts?
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

chrislegarth

#2
February 25, 2025, 08:53:52 AM
Tony- Yes, compiled WinBatch scripts.

td

#3
February 25, 2025, 09:59:44 AM
Your problems with Microsoft's AVD are likely permission issues. Once the WIL DLL and the Windows DLLs that the WIL DLL depends on are loaded into memory they stay there, so your problems should start at process startup. The only exception is if you load an extender as the Extender DLL and its dependent DLL are only loaded when you call the AddExtender function. If that is not the case, it may be a connectivity issue of some kind.

Sorry that I cannot be more specific. My understanding is that AVD access runs as a virtual machine on a local or "cloud" based machine but I may be wrong about that.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

chrislegarth

#4
February 25, 2025, 11:52:54 AM
Thanks for the info Tony.
I usually load all the extenders at the top of the script so I don't know exactly what part of the startup is tripping the error message. I'm thinking it's not getting the AddExtender functions as I think that gives a standard WinBatch error dialog. Googling the error message sends you down a rabbit hole of not very useful information.

td

#5
February 25, 2025, 01:13:07 PM
Are you compiling your scripts as a large exe or a small exe?
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

#6
February 25, 2025, 02:30:20 PM
No promises but it would be useful to know the exact nature of the error message you are seeing.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

#7
February 25, 2025, 05:14:47 PM
Yet another thing to consider. Since your compiled scripts are executing on a virtual machine, it could be possible that your VM does not have access to the 32-bit Windows subsystem. You could check this by compiling a script as 64-bit and observing whether or not you get the same error.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

td

#8
February 26, 2025, 09:59:45 AM
Yet more. According to MSFT documentation, AVDs support Win32 applications. WinBatch and compiled scripts are Win32 applications.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade
Print
Go Up Pages1
User actions