MSIX automatic update not working unless I restart my computer

%3CLINGO-SUB%20id%3D%22lingo-sub-2477328%22%20slang%3D%22en-US%22%3EMSIX%20automatic%20update%20not%20working%20unless%20I%20restart%20my%20computer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2477328%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20created%20a%20webpage%20that%20contains%20a%20link%20that%20allows%20end%20users%20to%20download%20and%20update%20their%20software.%3C%2FP%3E%3CP%3EThe%20HTML%20webpage%20links%20to%20the%20AppInstaller%20and%20launches%20the%20installer%20window%20when%20clicked.%3C%2FP%3E%3CP%3EThe%20entire%20workflow%20is%20automated%20using%20Azure%20CI%2FCD%20pipelines%20where%20we%20transfer%20the%20msix%20and%20appinstaller%20to%20a%20IIS%20server%20using%20FTP%20so%20every%20time%20we%20change%20the%20source%20code%2C%20it%20gets%20built%2C%20packaged%2C%20and%20transferred%20to%20a%20host%20so%20users%20can%20download%20and%20upgrade.%20Each%20deployment%20replaces%20both%20the%20msix%20and%20appinstaller%20files%20with%20new%20files%20on%20the%20host%20but%20the%20download%20link%20still%20points%20to%20the%20appinstaller%20and%20is%20able%20to%20serve%20the%20installer%20since%20the%20name%20and%20the%20location%20of%20it%20does%20not%20change.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverything%20works%20except%20the%20automatic%20updates.%20If%20the%20end%20user%20launches%20the%20app%2C%20they%20don't%20get%20prompted%20with%20the%20new%20version%20and%20the%20option%20to%20update%20until%20they%20restart%20their%20computer.%20But%20if%20they%20click%20on%20the%20installation%20link%2C%20the%20update%20window%20will%20pop%20up%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tested%20this%20multiple%20times.%20It%20happens%20consistently%20and%20again%20the%20only%20solution%20that%20has%20worked%20for%20me%20do%20far%2C%20is%20rebooting%20the%20computer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20am%20I%20doing%20wrong%20here%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EMo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2478617%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20automatic%20update%20not%20working%20unless%20I%20restart%20my%20computer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2478617%22%20slang%3D%22en-US%22%3ELet's%20start%20with%20the%20simple%20stuff.%20Can%20you%20post%20the%20XML%20of%20the%20AppInstaller%20file%3F%20%5BFeel%20free%20to%20redact%20links%20with%20replacements%20like%20%22server%22%2C%20%22share%22%2C%20and%20%22file%22%20if%20necessary.%5D%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2704820%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20automatic%20update%20not%20working%20unless%20I%20restart%20my%20computer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704820%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F896369%22%20target%3D%22_blank%22%3E%40Mo_Velayati%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%20the%20difference%20in%20the%20Publisher%20field%20in%20the%20following%20file.%26nbsp%3B%20It%20is%20the%20one%20I%20use%20to%20distribute%20my%20TMEditX%20product%20with%20updates.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3E%3CBR%20%2F%3E%3CAPPINSTALLER%20version%3D%221.5.0.0%22%20uri%3D%22https%3A%2F%2Fwww.tmurgent.com%2FAppV%2FTools%2FTMEditX%2FInstall%2FTMEditX.appinstaller%22%20xmlns%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fappinstaller%2F2018%22%3E%3CBR%20%2F%3E%3CMAINPACKAGE%20name%3D%22TMEditX%22%20publisher%3D%22CN%3D%26amp%3Bquot%3BTMurgent%20Technologies%2C%20LLP%26amp%3Bquot%3B%2C%20O%3D%26amp%3Bquot%3BTMurgent%20Technologies%2C%20LLP%26amp%3Bquot%3B%2C%20STREET%3D26%20Angela%20Street%2C%20L%3DCanton%2C%20S%3DMassachusetts%2C%20PostalCode%3D02021%2C%20C%3DUS%22%20processorarchitecture%3D%22x64%22%20version%3D%221.5.0.0%22%20uri%3D%22https%3A%2F%2Fwww.tmurgent.com%2FAppV%2FTools%2FTMEditX%2FInstall%2FTMEditX-1.5.0.0-x64.msix%22%3E%3C%2FMAINPACKAGE%3E%3CBR%20%2F%3E%3CUPDATESETTINGS%3E%3CBR%20%2F%3E%3CONLAUNCH%20hoursbetweenupdatechecks%3D%220%22%20showprompt%3D%22false%22%3E%3C%2FONLAUNCH%3E%3CBR%20%2F%3E%3CAUTOMATICBACKGROUNDTASK%3E%3C%2FAUTOMATICBACKGROUNDTASK%3E%3CBR%20%2F%3E%3CFORCEUPDATEFROMANYVERSION%3Etrue%3C%2FFORCEUPDATEFROMANYVERSION%3E%3CBR%20%2F%3E%3C%2FUPDATESETTINGS%3E%3CBR%20%2F%3E%26lt%3B%2FAppInstaller%26gt%3B%3C%2FAPPINSTALLER%3E%3C%2FPRE%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

I created a webpage that contains a link that allows end users to download and update their software.

The HTML webpage links to the AppInstaller and launches the installer window when clicked.

The entire workflow is automated using Azure CI/CD pipelines where we transfer the msix and appinstaller to a IIS server using FTP so every time we change the source code, it gets built, packaged, and transferred to a host so users can download and upgrade. Each deployment replaces both the msix and appinstaller files with new files on the host but the download link still points to the appinstaller and is able to serve the installer since the name and the location of it does not change.

 

Everything works except the automatic updates. If the end user launches the app, they don't get prompted with the new version and the option to update until they restart their computer. But if they click on the installation link, the update window will pop up as expected.

 

I have tested this multiple times. It happens consistently and again the only solution that has worked for me do far, is rebooting the computer.

 

What am I doing wrong here? 

 

Thanks,

Mo

3 Replies
Let's start with the simple stuff. Can you post the XML of the AppInstaller file? [Feel free to redact links with replacements like "server", "share", and "file" if necessary.]

@TIMOTHY MANGAN 

 

Hi Timothy,

 

sorry for the delayed reply.

Here's what's inside the AppInstaller

<?xml version="1.0" encoding="utf-8"?>
<AppInstaller Uri="https://somewebsite.com/SomeApp.appinstaller" Version="1.0.0.5" xmlns="http://schemas.microsoft.com/appx/appinstaller/2018">
  <MainPackage Name="12345678-1234-4333-12f3-123456789f12" Version="1.0.0.5" ProcessorArchitecture="x64" Publisher="CN=My Company, O=My Company, STREET=My Address, L=Somewhere, S=State, C=US" Uri="https://somewebsite.com/SomeApp.msix" />
  <UpdateSettings>
    <OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="true" UpdateBlocksActivation="true" />
  </UpdateSettings>
</AppInstaller>

 

And here's the issue:

Every time I build and package the app, I sent it over to a IIS server via FTP which replaces the old .msix and .appinstaller files with the new ones. But when I launch my already installed app, it does not recognize that there's a new version available so it moves forward with opening the application without updating.

 

What I am missing?

 

Thanks! 

@Mo_Velayati 

 

What version OS are you deploying onto?

 

Note the difference in the Publisher field in the following file.  It is the one I use to distribute my TMEditX product with updates.

 

<?xml version="1.0" encoding="utf-8"?>
<AppInstaller Version="1.5.0.0" Uri="https://www.tmurgent.com/AppV/Tools/TMEditX/Install/TMEditX.appinstaller" xmlns="http://schemas.microsoft.com/appx/appinstaller/2018">
<MainPackage Name="TMEditX" Publisher="CN=&quot;TMurgent Technologies, LLP&quot;, O=&quot;TMurgent Technologies, LLP&quot;, STREET=26 Angela Street, L=Canton, S=Massachusetts, PostalCode=02021, C=US" ProcessorArchitecture="x64" Version="1.5.0.0" Uri="https://www.tmurgent.com/AppV/Tools/TMEditX/Install/TMEditX-1.5.0.0-x64.msix" />
<UpdateSettings>
<OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="false" />
<AutomaticBackgroundTask />
<ForceUpdateFromAnyVersion>true</ForceUpdateFromAnyVersion>
</UpdateSettings>
</AppInstaller>