Forum Discussion

JohnMcC1983's avatar
JohnMcC1983
Copper Contributor
Jan 27, 2026

App installer randomly timing out on version checking.

I have had my program installing via MSIX for over two years without any issue. 

2 Replies

  • JohnMcC1983's avatar
    JohnMcC1983
    Copper Contributor

    Apologies, the site really isnt working for me today,
    Hopefully someone can help with this issue

  • JohnMcC1983's avatar
    JohnMcC1983
    Copper Contributor

    App installer randomly timing out on version checking.

     

    I have had my program installing via MSIX for over two years without any issue. 

    I host my appinstaller and msixbundles on blob storage and direct users to a URL to download the appinstaller to install the program.

    I have quite tight versioning on the program so have my update settings as below

     

    OnLaunch HoursBetweenUpdateChecks = 0 ShowPrompt=true UpdateBlocksActivation=true

     

    ForceUpdateFRomAnyVersion=true

     

    AutomaticBackgroundTask

     

    This forces the program to check to make sure it is on the correct version every time it is started up and forces the users to take the current version from the blob storage when I upgrade the version.

     

    An issue has started with only one user base since last Thursday after they applied windows update.   Randomly users are activating the app, it checks for updated and then just shuts down.  I have seen this before when another user had no internet connectivity, the updater couldn't get connected to the blob storage to verify versions so just shut down.

    I have been doing some research and can see that this check process has a very small tolerance for timeouts. 

    I have updated the HoursBetweenUpdateChecks to be a few hours which has made the issue slightly better however on first start up of the day (when the cache has expired) I am getting some users get into my program straight away and other who have to start the program up to 8 times before it will suddenly start working. 

    I think the issue could be potentially linked with KB5072033.

     

    Has anyone else come across this?

Resources