MSIX AddPackage not working after WindowsUpdate(KB5005033) installed

槙之介 久保 96 Reputation points
2021-08-12T11:22:20.143+00:00
   var uri = "https://mywebserver/MyApp.msix";  
   var asyncProgress = packagemanager.AddPackageAsync(  
         uri,  
         null,  
         DeploymentOptions.ForceApplicationShutdown  
   );  
   await Task.Run(() =>  
   {  
         while (asyncProgress.Status == AsyncStatus.Started)  
         {  
         }  
   });  

this code is worked when I uninstalled WindowsUpdate or change uri from webserver to local storage.

powershell

   Add-AppxPackage https://mywebserver/MyApp.msix  
   Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened.  
   Error 0x80D05011: Opening the package from location MyApp.msix failed.  
   For additional information, look for [ActivityId] 7c6dcda0-9004-0002-04af-6e7c0490d701 in the Event Log or use the command line Get-AppxLog -ActivityID 7c6dcda0-9004-0002-04af-6e7c0490d701  
     
   At line:1 char:1  
   + Add-AppxPackage https://mywebserver/MyApp.msix  
   + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
       + CategoryInfo          : OpenError: (https://mywebserver/MyApp.msix:String) [Add-AppxPackage], FileNotFoundExcept  
      ion  
       + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand  

I can install msix created in Visual Studio PackageProject before Windows Update.
But can't install msix created in Visual Studio PackageProject after Windows Update.
I think the problem is with the issued msix after Windows Update.

Event Viewer Logs

error 0x80D05011 Could not open the package from CareDataCenter.msix
122715-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2021-08-12-145256.png

error 0x80070002 Could not open the Msix vs package from CareDataCenter.msix.
Make sure you have Msixvc Support Services installed.
122734-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2021-08-12-145314.png

error 0x80D05011: Could not get staging session due to https://mywebserver/CareDataCenter.msix
122614-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2021-08-12-145334.png

AppX deployment operation failed (package, error 0x80073CF0). Error specific to this error Text: Error 0x80D05011: The package could not be opened from the location CareDataCenter.msix.
122716-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2021-08-12-145353.png

I can access mywebserver from browser.
mywebserver not restrict access.

KB5005033 change logs isn`t written anything like that
https://support.microsoft.com/ja-jp/topic/2021-%E5%B9%B4-8-%E6%9C%88-10-%E6%97%A5-kb5005033-os-%E3%83%93%E3%83%AB%E3%83%89-19041-1165-19042-1165-%E3%81%8A%E3%82%88%E3%81%B3-19043-1165-b4c77d08-435a-4833-b9f7-e092372079a4

windows : 10.0.19043
visual studio : 16.11.0

Thank you

Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,407 questions
{count} votes

Accepted answer
  1. 槙之介 久保 96 Reputation points
    2021-08-18T08:18:45.897+00:00

    The problem was renaming the published Msix file.

    Don't change it like this
    "CareDataCenter.Package_1.0.0.0_x86_Debug.msix" to "CareDatacenter.msix".

    This seems to happen when the url protcol is https or http.

    0 comments No comments

0 additional answers

Sort by: Most helpful