This app can't run on your PC

Donald wrote:

When I click on the exe file for VirtualMIDISynth

Which .exe are you talking about, the setup executable or VirtualMIDISynth.exe?
I mean, were you able to complete VirtualMIDISynth installation or the issue happens at installation stage?

I need to have further info about your system, expecially the bitness (x86 or x64 windows version).

Please open a command prompt and run this:

systeminfo > info.txt

This creates file info.txt in current directory; open it with Notepad, remove sensitive data, then post it here...

Well, I'm out of ideas 🙄.

The only "strange" thing I see from your log is Windows edition: "Windows 10 Enterprise", which is pretty uncommon and I don't have that OS to test setup with.
The first thing that comes to my mind is that, being an Enterprise edition, it doesn't have the required 32bit compatibility feature (WOW64) installed or enabled.
VirtualMIDISynth is a 64bit program, but its setup (built with NSIS) is 32bit so it can run on both architecture and install the required versions.
So, you should ask your IT admin (who installed that Windows version) if this is the case.

Another thing that comes to mind is SmartScreen feature, that sometimes gets crazy and lockd downloaded files from being installed.
Please check the following links and try to follow the proposed suggestions 😉

https://answers.microsoft.com/en-us/windows/forum/windows_10-other_setti...
https://www.thewindowsclub.com/how-to-enable-or-disable-smartscreen-filt...
https://ugetfix.com/ask/how-to-fix-this-app-cant-run-on-your-pc-error/

8Track wrote:

I get the "app can't run on your PC" error trying to run on a Microsoft Surface X Pro with an ARM processor.

Windows x86/x64 emulation on ARM works by "compiling blocks of x86 instructions into ARM64 instructions with optimizations to improve performance" (https://docs.microsoft.com/en-us/windows/uwp/porting/apps-on-arm-x86-emu...).

This process could work for all "user applications", but it's not guaranteed to work for device drivers and other "special" DLLs like VMS.
Additionally, VMS relies on WinMM layer and I can't find any documentation that confirms its porting to ARM platform...