How can sideloaded UWP app update the version installed in a device

Question

How can sideloaded UWP app update the version installed in a device

McMillenBelenMNRF-9276 10

Our organization has developed a line-of-business (LOB) application for use on Panasonic mobile tablets. The app is distributed via sideloading, with the installation package hosted on a shared UNC path. Installation is handled using a .appinstaller file.

We’ve encountered an issue where the app does not consistently detect and install new versions after a new package is deployed to the shared network location.

The application is published using Visual Studio 2022, with the update settings configured to check for updates every time the app launches. However, in practice, users often need to open the app multiple times before the update is applied. There appears to be a delay or inconsistency in how the appinstaller mechanism detects the new version.

Are there additional configuration steps or settings required when publishing the app to a shared UNC path to ensure updates are detected and applied immediately?

Harry Vo (WICLOUD CORPORATION) 405 Reputation points Microsoft External Staff

2025-07-18T03:34:39.5466667+00:00

Hi McMillen, Buom, does my solution I shared works for you?

Let me know if you need any further help or adjustments! Thank you!

2 answers

Your answer

Harry Vo (WICLOUD CORPORATION) 405 Reputation points Microsoft External Staff

2025-07-18T03:34:39.5466667+00:00

Hi McMillen, Buom, does my solution I shared works for you?

Let me know if you need any further help or adjustments! Thank you!

Answer 1

Hi McMillen Buom,

It looks like there's a delay in the update detection process. By default, the .appinstaller file is set to check for a new version every 24 hours, which can cause a significant delay for users.

To fix this issue, modify the code in your .appinstaller file from:

<UpdateSettings>
    <OnLaunch HoursBetweenUpdateChecks="24"/>
</UpdateSettings>

to:

<UpdateSettings>
    <OnLaunch HoursBetweenUpdateChecks="0"/>
</UpdateSettings>

This change will make the application check for updates every time it launches.

Moreover, if the issue still persists, it's recommended to host your .appinstaller file and installation package on an internal HTTP server instead of a network share. Hosting over HTTP ensures better reliability and compatibility with the update mechanism.

If you have any other questions, feel free to ask. Thank you!

Answer 2

As a supplement to Harry's answer, you can also add attributes s4:AutomaticBackgroundTask and s4:ForceUpdateFromAnyVersion.

You can refer to the following code:

<UpdateSettings>
    <OnLaunch HoursBetweenUpdateChecks="1"/>
    <s4:AutomaticBackgroundTask/>
    <s4:ForceUpdateFromAnyVersion>true</s4:ForceUpdateFromAnyVersion>
</UpdateSettings>

Note:

s4:AutomaticBackgroundTask: Checks for updates in the background. A check is made every 8 hours independently of whether the user launched the app. This type of update cannot show UI. Available in Windows 10, version 1803 and later.

s4:ForceUpdateFromAnyVersion:A boolean that allows the app's version to be incremented or decremented. Without this element, the app can only move to a higher version. Available starting in Windows 10, version 1809 and later.

For more information, you can check document: UpdateSettings .

Share via

How can sideloaded UWP app update the version installed in a device

2 answers

Your answer