How do you get that stub executable work? My short cut in the desktop seems point to the installer.

I have seen the same problem: The overall error is as follows:

Faulting application name: my-app.exe, version: 4.0.0.0, time stamp: 0x5f64eb21
Faulting module name: my-app.exe, version: 4.0.0.0, time stamp: 0x5f64eb21
Exception code: 0xc0000409
Fault offset: 0x0000e841
Faulting process id: 0x4960
Faulting application start time: 0x01d966493c1c594f
Faulting application path: C:\Program Files\myapp\my-app.exe
Faulting module path: C:\Program Files\my-app\my-app.exe
Report Id: f26180e9-1aa2-42fa-8e51-bdff783a0e62
Faulting package full name: 
Faulting package-relative application ID: 

It's weird as the actual specified version is 4.0.0.7, but this seems to be referring to 4.0.0.0. In my configuration there is no mention of 4.0.0.0 at all.
My guess is that it's truncating a version somewhere and later on it can't find "the version". Reverting to a 3 stage version number cures the issue.

Still not fixed unfortunately. If you manually rename the subdirectory to have three version component, the real executable is properly launched. I'm not sure how to skip generating that stub exe at all. I don't see the added value, since a MSI cannot be installed side-by-side.

there is plan to fix it?
@Sebazzz

StubExecutable expects app's version to be a valid semantic version, while the 4-level version is not a valid semantic version.

• See: https://github.com/bitdisaster/Squirrel.Msi/blob/master/src/StubExecutable/Semver200_parser.cpp

So this is an expected behavior. In the base case, electron-wix-msi may check the version to be valid and show an explicit error.

If you are using it via @electron-forge/maker-wix - this is probably the source of the issue. The MakerWix replaces a valid semantic version with windows compatible, making it an invalid semantic version.

• Ref: Removal of prerelease tags in normalizeWindowsVersion prevents app installed via MSI installer from starting on Windows electron/forge#3805