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

StephenWhiteD3G 

A WORKING SOLUTION ("no parsing required") - We also ran into this issue recently within our organization so I coded an asynchronous method to stop and start the Delivery Optimization service before the call to CheckUpdateAvailabilityAsync(). Note - Our application  runs under the context of the currently logged in user, therefore we had to set a global policy to allow users in the USERS group to stop and start the service name DoSvc . Additionally, these methods will also allow you to take complete control of leveraging MSIX to check for updates whenever you require, and the app will relaunch post update. It will work from desktop shortcuts, and when an MSIX app is pinned to the taskbar (normally MSIX will not update in these scenarios). I call these methods from a timed event that is configured via app settings per environment.

        private async Task CheckForUpdateAsync()
        {
            if (!string.IsNullOrEmpty(_appSettingsProvider.ApplicationVersion))
            {
                _logger.Info($"The current installed application version is: {_appSettingsProvider.ApplicationVersion}");
            }

            _logger.Info("Checking for update...");

            try
            {
                var packageManager = new PackageManager();
                var installedPackage = packageManager.FindPackageForUser(string.Empty, Package.Current.Id.FullName);
                if (installedPackage != null)
                {
                    var tasks = new List<Task>
                    {
                        Task.Run(() => RestartDeliveryOptimizationService())
                    };
                    await Task.WhenAll(tasks);

                    var result = await installedPackage.CheckUpdateAvailabilityAsync();
                    ProcessPackageResult(result, installedPackage);
                }
            }
            catch (InvalidOperationException ex)
            {
                _logger.Info("AutoUpdater was unable to determine the installed package, which is typically due to debugging in VisualStudio. " + ex);
            }
            catch (Exception ex)
            {
                _logger.Error("An error occurred while checking for the availability of a package update. " + ex);
            }
        }

        /// <summary>
        /// Restarts the Delivery Optimization Service to ensure updates succeed. Currently a work around for a known issue. - CM
        /// </summary>
        private void RestartDeliveryOptimizationService()
        {
            try
            {
                var service = new ServiceController("DoSvc");
                var timeout = TimeSpan.FromMinutes(1);
                if (service.Status != ServiceControllerStatus.Stopped)
                {
                    service.Stop();
                    service.WaitForStatus(ServiceControllerStatus.Stopped, timeout);
                }

                service.Start();
                service.WaitForStatus(ServiceControllerStatus.Running, timeout);
            }
            catch(Exception ex)
            {
                _logger.Error("There was a problem starting DoSvc." + ex.InnerException.ToString());
            }
        }

        private void ProcessPackageResult(PackageUpdateAvailabilityResult result, Package installedPackage)
        {
            try
            {
                if (result != null && (result.Availability == PackageUpdateAvailability.Available || result.Availability == PackageUpdateAvailability.Required))
                {
                    _logger.Info("A package update is available.");
                    _timer.Enabled = false;

                    var appInstallerUri = installedPackage.GetAppInstallerInfo().Uri;
                    Process.Start($"ms-appinstaller:?source={appInstallerUri}");
                    Application.Exit();
                }
                else if (result.Availability == PackageUpdateAvailability.Unknown)
                {
                    _logger.Warn("The package update availability status = Unknown.");
                }
                else if (result.Availability == PackageUpdateAvailability.Error)
                {
                    _logger.Warn($"The package update availability status = Error. {result.ExtendedError.Message}");
                    _logger.Warn($"No update information associated with app DisplayName:{installedPackage.DisplayName}, FullName:{Package.Current.Id.FullName}");
                }
            }
            catch(Exception ex)
            {
                _logger.Error("An error occurred while processing the package update. " + ex);
                _logger.Error(ex.Message);
                _logger.Error(ex.InnerException.ToString());
            }
        }

Hi,

It's nearly a year later than the original post on this and I am now having this issue. Has there been a fix for it or not?

Hi, 
we have the same problem. On Windows 10 2004 MSIX updates fail with errors same as mentioned in the previous comments.

This issue is critical for us because we use MSIX and .appinstaller files in production and more and more our users are switching from Windows 10 1909 to 2004. 

Somehting similar is happening here, 2004 as well. I'm getting AppInstaller failures with Unknown error (0x80d05011). It is related to msixbudles as I can easily get appinstaller back into a working condition switching back to non-bundle packaging. It is the same with either flat bundles or regular ones.

The issue doesn't occur if I install the msixbundle directly without .appInstaller.

Also I found the default App.packagelayout template from Visual Studio to have missing configuration name in the end of FileName attribute. This means thegenerated misxbundle file will have no "_Debug" or "_Release" strings in the end of filenames. However, looking inside the generated .appinstaller file msixbundle URL, I see configuration names are there, and so the .appinstaller will fail to lookup for the bundle. Of course the above mentioned error doesn't solve even patching this trivial filename mismatch, and also exists when no App.packagelayout file is provided (and so filename matches correctly).

Hi StephenWhiteD3G,

Could you please send us the link to your Feedback Hub item so we can take a closer look?

What kind of LOB application do you have? I notice the error contains 'MSIXVC' and MSIXVC is an extension of MSIX that is specifically designed for games that are published through PC GamePass; it is not used for non-game scenarios.

Best,

Sharla