Auto-update doesn't work for some users (sideloaded MSIX package)

%3CLINGO-SUB%20id%3D%22lingo-sub-2245151%22%20slang%3D%22en-US%22%3EAuto-update%20doesn't%20work%20for%20some%20users%20(sideloaded%20MSIX%20package)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2245151%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20WPF%20app%20that%20we're%20sideloading%20off%20our%20network%20with%20an%20MSIX%20package.%26nbsp%3B%20We%20have%20it%20set%20up%20to%20pop%20up%20the%20update%20window%20when%20the%20program%20starts%20if%20there's%20a%20new%20update.%26nbsp%3B%20However%2C%20there%20are%20a%20couple%20of%20users%20who%20don't%20get%20this%20window%20when%20they%20run%20the%20program.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20think%20of%20one%20possible%20cause.%26nbsp%3B%20We%20have%20been%20editing%20the%26nbsp%3B%3CSPAN%3EC%3A%5CProgram%20Files%20(x86)%5CMicrosoft%20Visual%20Studio%5C2019%5CProfessional%5CMSBuild%5CMicrosoft%5CVisualStudio%5Cv16.0%5CAppxPackage%5CMicrosoft.AppxPackage.Targets%20file%20to%20get%20rid%20of%20the%20_Test%20suffix%20on%20the%20installation%20directory.%26nbsp%3B%20There%20was%20a%20time%20where%20Visual%20Studio%20was%20updated%20and%20we%20forgot%20to%20change%20those%20and%20wound%20up%20making%20a%20few%20weeks%20of%20directories%20with%20the%20_Test%20on%20them%2C%20but%20most%20of%20them%20do%20not.%26nbsp%3B%20Don't%20ask%20me%20why%20we%20got%20in%20this%20situation.%26nbsp%3B%20Anyway%2C%20could%20that%20have%20an%20effect%20on%20it%3F%26nbsp%3B%20Maybe%20these%20two%20use%20installed%20it%20when%20the%20directory%20was%20named%20_Test%20(but%20now%20the%20directories%20don't%20have%20that%20suffix)%3F%26nbsp%3B%20We%20do%20weekly%20updates%20to%20the%20program%20and%20we%20have%20every%20version%20in%20a%20subdirectory.%26nbsp%3B%20The%20MSIX%20package%20thing%20deploys%20it%20that%20way%20for%20us.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

We have a WPF app that we're sideloading off our network with an MSIX package.  We have it set up to pop up the update window when the program starts if there's a new update.  However, there are a couple of users who don't get this window when they run the program. 

 

I can think of one possible cause.  We have been editing the C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppxPackage.Targets file to get rid of the _Test suffix on the installation directory.  There was a time where Visual Studio was updated and we forgot to change those and wound up making a few weeks of directories with the _Test on them, but most of them do not.  Don't ask me why we got in this situation.  Anyway, could that have an effect on it?  Maybe these two use installed it when the directory was named _Test (but now the directories don't have that suffix)?  We do weekly updates to the program and we have every version in a subdirectory.  The MSIX package thing deploys it that way for us.

0 Replies