Forum Discussion

sayalishukla03's avatar
sayalishukla03
Copper Contributor
Dec 31, 2018

Error getting MSIX Packaging Tool Driver

Hi

  

I am not able to create MSIX package . 

 

Getting following log ,

[2018-12-21 18:48:03] [Info] ************************************************************
[2018-12-21 18:48:03] [Info]  MSIX Packaging Tool Launch
[2018-12-21 18:48:03] [Info] ************************************************************
[2018-12-21 18:48:03] [Info] Tool Version: 1.2018.1005.0
[2018-12-21 18:48:03] [Info] Attempting to read settings file: C:\Users\Sayali\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\settings.xml 
[2018-12-21 18:48:04] [Info] Opening MSIX Packaging Tool welcome screen.
[2018-12-21 18:48:04] [Info] ************************************************************
[2018-12-21 18:48:04] [Info] ApplicationPackage Workflow
[2018-12-21 18:48:04] [Info] ************************************************************
[2018-12-21 18:48:04] [Info] ----------------Select Installer View----------------
[2018-12-21 18:48:15] [Info] Selected installer : My Sample Project.msi
[2018-12-21 18:48:15] [Info] Installer argument: 
[2018-12-21 18:48:15] [Info] ----------------Select Environment View----------------
[2018-12-21 18:48:19] [Info] ----------------Select Installer View----------------
[2018-12-21 18:49:24] [Info] Selected installer : My Sample Project.msi
[2018-12-21 18:49:24] [Info] Installer argument: 
[2018-12-21 18:49:24] [Info] ----------------Select Environment View----------------
[2018-12-21 18:49:27] [Info] Selected execution environment: Local machine
[2018-12-21 18:49:27] [Info] ----------------Package Information View----------------
[2018-12-21 18:49:51] [Info] Package name: MySampleProject
[2018-12-21 18:49:51] [Info] Package display name: My Sample Project
[2018-12-21 18:49:51] [Info] Publisher name: CN=My Company
[2018-12-21 18:49:51] [Info] Publisher display name: My Company
[2018-12-21 18:49:51] [Info] Version: 1.0.0.0
[2018-12-21 18:49:51] [Info] Activating PrepareComputerLocalOrRemoteSession locally
[2018-12-21 18:49:52] [Info] ----------------Prepare Computer View----------------
[2018-12-21 18:49:52] [Info] Required prepare computer task: MSIX Packaging Tool Driver
[2018-12-21 18:49:52] [Info] Recommended prepare computer task: Windows Search is active
[2018-12-21 18:49:52] [Info] Recommended prepare computer task: Pending reboot
[2018-12-21 18:49:52] [Info] Checking if MSIX Packaging Tool Driver is installed...
[2018-12-21 18:49:52] [Debug] About to start process
[2018-12-21 18:49:52] [Debug]     - File name:                 dism.exe
[2018-12-21 18:49:52] [Debug]     - Arguments:                 /online /add-capability /capabilityname:Msix.PackagingTool.Driver~~~~0.0.1.0
[2018-12-21 18:50:19] [Info] Deployment Image Servicing and Management tool
[2018-12-21 18:50:19] [Info] Version: 10.0.17763.1
[2018-12-21 18:50:19] [Info] Image Version: 10.0.17763.194
[2018-12-21 18:50:19] [Info] [=                          3.0%                           ] 
[2018-12-21 18:50:19] [Info] [===                        5.9%                           ] 
[2018-12-21 18:50:19] [Info] [===                        5.9%                           ] 
[2018-12-21 18:50:19] [Info] [==========================100.0%==========================] 
[2018-12-21 18:50:19] [Info] Error: 0x800f0954
[2018-12-21 18:50:19] [Info] DISM failed. No operation was performed. 
[2018-12-21 18:50:19] [Info] For more information, review the log file.
[2018-12-21 18:50:19] [Info] The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
[2018-12-21 18:50:19] [Error] dism.exe failed, exit code = -2146498220
[2018-12-21 18:50:19] [Error] Failed to install MSIX Packaging Tool Driver.
[2018-12-21 18:50:19] [Error] Error Occurred: Microsoft.Packaging.SDKUtils.ProcessRunner.ProcessRunnerException: Process dism.exe failed with exit code -2146498220.
   at Microsoft.Packaging.SDKUtils.ProcessRunner.ProcessRunnerBase.ValidateExitCode()
   at MsixGenerator.LocalOrRemoteExecution.PrepareComputerLocalOrRemoteSession.<>c.<FODInstallationAsync>b__3_0()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MsixGenerator.LocalOrRemoteExecution.PrepareComputerLocalOrRemoteSession.<FODInstallationAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MsixPackagingTool.Model.ApplicationPackageWorkflow.PrepareComputerModel.<FixRequiredPrepareComputerTasks>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MsixPackagingTool.ViewModel.ApplicationPackageWorkflow.PrepareComputerViewModel.<RequiredPrepareComputerTasksMethod>d__30.MoveNext()
[2018-12-21 18:50:32] [Info] Spawning background worker thread.
[2018-12-21 18:50:32] [Info] Cleaning up the virtual machine
[2018-12-21 18:50:38] [Info] ************************************************************
[2018-12-21 18:50:38] [Info]  Closing MSIX Packaging Tool
[2018-12-21 18:50:38] [Info] ***

 

 

Thanks

 

    

5 Replies

    • Deleted's avatar
      Deleted

      James PikeThanks for pointing to this direction! I finally got it working by signing in into the Feedback Hub. Although it's not mentioned as a requirement, it seems to be necessary in order to install the driver. In my case, with error 0x80131500, this was a reproducible cause.

    • Tim Mangan's avatar
      Tim Mangan
      MVP

      I have found that the driver will fail to install in this way if the VM does not have access to the internet.  I'm not sure why that is the case; being connected to a local network is not enough.

       

      If you need to package in an offline VM, you should connect it to the internet, start packaging to the point that the driver gets installed and then cancel.  You can then take your snapshot and be disconnected from then on.

Resources