Forum Discussion

StephenWhiteD3G's avatar
StephenWhiteD3G
Iron Contributor
Jun 15, 2020

Windows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.

We use MSIX for one of our LOB applications at my organization. We recently updated some machines to Windows 10 2004 to test it before rolling it out to the rest of the company. One problem we ha...
20H1
MSIX
StephenWhiteD3G's avatar
StephenWhiteD3G
Iron Contributor
Jun 18, 2020
Hi Sharla,

I thought I did, but I'll do my best to get a repro going on one of them ASAP. Thanks for letting me know they were missing.
StephenWhiteD3G's avatar
StephenWhiteD3G
Iron Contributor
Jun 18, 2020



Hi again Sharla,

I submitted another report using my organization account instead of personal account from a machine that is affected (my work PC actually). Please let me know if the diagnostics and the recording uploaded.

Here is the new feedback hub link:

https://aka.ms/AA8qzzo

Thanks again for your help, I hope we can get to the bottom of this soon.


P.S. As an experiment, I am going to remove the AutomatedBackgroundTask element in the app installer file on the next update for the org and see if that changes anything. I have a hypothesis that may be the cause of the problem, as I found earlier today that if I deployed an update locally and then quickly opened the app from the start menu, it was able to see and install the update without any problems and I was also able to uninstall and reinstall the app multiple times in a row without any errors. 

  • StephenWhiteD3G's avatar
    StephenWhiteD3G
    Iron Contributor
    Jun 22, 2020

    Hi Sharla,

    I just wanted to follow up and see if you were able to see anything or if you had a chance to look at this again yet. If you haven't, I understand. The users have been given guidance to use the bundle file until we can find a better solution regarding this, but its still a huge problem. 😞 

    As far as other things we have tried, I adjusted our CI/CD pipeline in Azure to apply version numbers to the .wapproj file that has a zero for the last number, but that didn't result in any changes. I was hoping it would help since the YAML we were using was adding version numbers that had a number in the last digit (one of the examples we found on MSDN showed that it was supposedly safe to do this, but the MSIX documentation says it must stay as Zero and we recalled that Visual Studio doesn't allow you to change it when creating the app installer via the wizard).

    We also tried turning off the "Automatic Background Task" setting in the app installer, but that hasn't seemed to make any difference either.

    I'm currently trying to see if Process Monitor or Process Explorer can provide any more details as to what may be not responding correctly in Windows when these errors occur, but unfortunately I haven't had any success yet.

    Again, please let me know if you or anyone on your team have any updates. 

    • StephenWhiteD3G's avatar
      StephenWhiteD3G
      Iron Contributor
      Jun 23, 2020
      Small update, but unfortunately still no other work arounds found on our end besides having the user download and run the full MSIXBundle.

      We have a test environment for the the LOB app that uses MSIX / App Installer as well. For some reason, this one appears to not have the errors occur when it is run and then updates are provisioned and applied subsequently. However, the biggest difference between the test and live environments is that the test environment uses a local file share on the company file server for hosting the files for the app installer and MSIX bundle.

      The live environment uses an Azure Blob storage (which you probably saw from the feedback hub video; hopefully you were able to get that). The live is due to the fact we use Azure DevOps and Pipelines and we found it to be the best way to automate delivery and deployment.

      Hopefully someone on your end may be able to see more than me; but my guess is the problem may be due to the way App Installer or some component of MSIX in Windows 10 2004 is handling the URIs of UNC paths versus HTTPS? Again, this is just a stab in the dark.


      • StephenWhiteD3G's avatar
        StephenWhiteD3G
        Iron Contributor
        Jun 26, 2020

        Sharla,

        Edit #2: Well, the idea I had earlier about HTTP turned out to be incorrect. The app installer errors out on subsequent package updates when using either HTTP or HTTPS endpoints.

        One thing I noticed is that this cryptic error gets logged in the event viewer whenever the problem occurs, I am not sure if this indicates there is a bug in the App Installer process itself, but it is making me wonder:

        Suspending
        Error: Unknown HResult Error code: 0xefffffff
        Function: Windows::ApplicationModel::Store::Preview::InstallControl::AppInstallManagerImpl::OnSuspend
        Source: onecoreuap\enduser\winstore\installservice\lib\appinstallcontrol.cpp (476)

        Skipping license manager: PFN Microsoft.DesktopAppInstaller_1.0.41331.0_x64__8wekyb3d8bbwe
        Function: InvokeLicenseManagerRequired
        Source: onecoreuap\enduser\winstore\licensemanager\apisethost\activationapis.cpp (373)

         

        Note: I can also see these errors in the output if I try to debug App Installer using VS when the error occurs. For what it is worth, I also tried restarting all of the services that App Installer is calling (Windows Store Install Service, Game Service, Client Licensing and App X Service, but unfortunately that doesn't seem to clear the state for it.)

Resources