Forum Discussion
Winforms .exe in MSIX Package Does Not Startup After Auto Update
We are deploying a classic Winforms .exe via MISX. Approximately 20% of the time, the application does not start automatically after an auto update completes. After an update and failed start, we can...
Hi everyone,
We stumbled across this problem recently, and we may have found a solution to this that I wanted to share.
We had the problem that on starting the app the update dialog would take quite the time to do its check, then closes and nothing happens. Only clicking the start menu would cause the app to start. We tested pinning the app to the taskbar, which would cause the app to start sooner, but the update dialog to be slow still.
One colleague with windows 10 had no issue with the update dialog, which would immediately close, but still the app would not start unless clicking the start menu.
We have just switched from a signing certificate issued by our company CA to a code signing certificate that we paid for. And now it just works. For everyone in out team the update dialog is only there a short time, and then the app starts, without needing to click the start menu.
I am not proficient with certificates, but I would guess some step in the validation process ran into a timeout before and now does not, and it also solved the startup issue. Maybe someone that still has the issue can test if this solves their issue also? If so, we may have a more precise starting point to take up investigation again.
We stumbled across this problem recently, and we may have found a solution to this that I wanted to share.
We had the problem that on starting the app the update dialog would take quite the time to do its check, then closes and nothing happens. Only clicking the start menu would cause the app to start. We tested pinning the app to the taskbar, which would cause the app to start sooner, but the update dialog to be slow still.
One colleague with windows 10 had no issue with the update dialog, which would immediately close, but still the app would not start unless clicking the start menu.
We have just switched from a signing certificate issued by our company CA to a code signing certificate that we paid for. And now it just works. For everyone in out team the update dialog is only there a short time, and then the app starts, without needing to click the start menu.
I am not proficient with certificates, but I would guess some step in the validation process ran into a timeout before and now does not, and it also solved the startup issue. Maybe someone that still has the issue can test if this solves their issue also? If so, we may have a more precise starting point to take up investigation again.
I have a Winforms / WPF app in an MSIX/Appx package.
After some release of Windows, it has gotten very slow to launch. So slow, I had to stop providing it to customers. On the dev machine, it's 5 seconds before the app shows the splash screen and goes into main and starts loading. On customers machines it takes about 30 seconds before Windows gives the application control.
I don't believe this has to do with auto updating, as the application doesn't use it.
The benefit of these app packages is that it solves DLL stomping.
But, the app has a large number of DLLs. Is it possible that Windows is scanning and hashing all these DLLs before launch?
JMarianczuk