Simplify MSIX image creation with the MSIXMGR tool

%3CLINGO-SUB%20id%3D%22lingo-sub-2120029%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2120029%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F195573%22%20target%3D%22_blank%22%3E%40Stefan%20Georgiev%3C%2FA%3E%26nbsp%3BPlease%20provide%20support%20or%20example%20of%20using%20PowerShell.%20My%20quick%20dirty%20test%20failed%2C%20no%20error%2C%20just%20a%20GUID%20folder%20in%20the%20msixmgr%5Cx64%20path.%20I%20want%20to%20loop%20through%20all%20my%20MSIX%20pacakges.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EClear-Host%3C%2FP%3E%3CP%3E%24MSIXMGR%20%3D%20%22C%3A%5Cmsixmgr%5Cx64%22%3CBR%20%2F%3E%24MSIXPath%20%3D%20%22C%3A%5CMSIX1%22%3CBR%20%2F%3E%24CimFS%20%3D%20%22C%3A%5CCimFS%22%3C%2FP%3E%3CP%3E%24PackageName%20%3D%20%22NotepadPlusPlus_7.9.1.0_x64%22%3C%2FP%3E%3CP%3EIf%20(!(Test-Path%20-Path%20%24CimFS%5C%24PackageName))%20%7BNew-Item%20-ItemType%20directory%20-Path%20%24CimFS%5C%24PackageName%20%7C%20Out-Null%7D%3C%2FP%3E%3CP%3ECD%20%24MSIXMGR%3CBR%20%2F%3E.%5Cmsixmgr.exe%20-Unpack%20-packagePath%20%22%24MSIXPath%5C%24PackageName.msix%22%20-destination%20%22%24CimFS%5C%24PackageName%5C%24PackageName.cim%22%20-applyacls%20-create%20-vhdSize%20200%20-filetype%20%22cim%22%20-rootDirectory%20apps%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2143695%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2143695%22%20slang%3D%22en-US%22%3EI%20pretty%20much%20ran%20your%20script%20with%20my%20variables%20and%20worked%20as%20expected.%20I%20started%20my%20PowerShell%20in%20admin%20mode%20that%20is%20required%20since%20MSIXMGR%20needs%20to%20manipulate%20drive.%3CBR%20%2F%3E%3CBR%20%2F%3E%24MSIXMGR%20%3D%20%22C%3A%5CUsers%5Cssa%5CDownloads%5Cmsixmgr%5Cx64%22%3CBR%20%2F%3E%24MSIXPath%20%3D%20%22C%3A%5CUsers%5Cssa%5CDesktop%5C%22%3CBR%20%2F%3E%24CimFS%20%3D%20%22C%3A%5Ctemp%5Cdate%22%3CBR%20%2F%3E%3CBR%20%2F%3E%24PackageName%20%3D%20%22GPUZ_1.0.1.0_x64__74vyvr5aw93s6%22%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20(!(Test-Path%20-Path%20%24CimFS%5C%24PackageName))%20%7BNew-Item%20-ItemType%20directory%20-Path%20%24CimFS%5C%24PackageName%20%7C%20Out-Null%20%7D%3CBR%20%2F%3E%3CBR%20%2F%3ECD%20%24MSIXMGR%3CBR%20%2F%3E.%5Cmsixmgr.exe%20-Unpack%20-packagePath%20%22%24MSIXPath%5C%24PackageName.msix%22%20-destination%20%22%24CimFS%5C%24PackageName%5C%24PackageName.cim%22%20-applyacls%20-create%20-vhdSize%20200%20-filetype%20%22cim%22%20-rootDirectory%20apps%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2118585%22%20slang%3D%22en-US%22%3ESimplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2118585%22%20slang%3D%22en-US%22%3E%3CH1%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1270014698%22%20id%3D%22toc-hId-1269155563%22%3E%26nbsp%3B%3C%2FH1%3E%0A%3CH1%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--537439765%22%20id%3D%22toc-hId--538298900%22%3ESimplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3ENote%3A%26nbsp%3B%3C%2FFONT%3E%3C%2FSTRONG%3E%3CFONT%20size%3D%224%22%3EThe%20CIM%20functionality%20is%20currently%20under%20development.%20Please%20do%20not%20use%20in%20production%20environments.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20article%20is%20an%20overview%20of%20how%20to%20use%20the%20MSIXMGR%20tool%20and%20its%20usage%20in%20MSIX%20app%20attach.%20MSIXMGR%20takes%20an%20MSIX%20packaged%20application%20(.MSIX)%20and%20expands%20it%20into%20an%20MSIX%20image%20(VHD%20or%20VHDX).%20That%20resulting%20MSIX%20image%20(.VHD(x))%20is%20what%20we%20upload%20to%20a%20storage%20account%20using%20WVD%20MSIX%20app%20attach.%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1950073068%22%20id%3D%22toc-hId-1949213933%22%3E%26nbsp%3B%3C%2FH1%3E%0A%3CH1%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-142618605%22%20id%3D%22toc-hId-141759470%22%3EPrerequisites%3C%2FH1%3E%0A%3CP%3ETo%20successfully%20complete%20the%20steps%20in%20this%20article%20please%20confirm%20the%20following%20steps%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EDownload%20MSIXMGR%20from%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmsixmgr%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmsixmgr%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EMSIX%20packaged%20application%20(.MSIX%20file)%3C%2FLI%3E%0A%3CLI%3EAdministrative%20permissions%20on%20the%20machine%20where%20the%20MSIX%20image%20will%20be%20created.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3A%20MSIXMGR%20can%20also%20create%20CIM%20files%20but%20those%20can%20only%20be%20used%20on%20Windows%2010%2020H2.%20This%20is%20something%20we%20are%20working%20to%20address.%3C%2FFONT%3E%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1664835858%22%20id%3D%22toc-hId--1665694993%22%3E%26nbsp%3B%3C%2FH1%3E%0A%3CH1%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-822676975%22%20id%3D%22toc-hId-821817840%22%3ECreating%20MSIX%20image%3C%2FH1%3E%0A%3CP%3EExpansion%20is%20the%20process%20of%20taking%20an%20MSIX%20packaged%20application%20(.MSIX)%20and%20unzipping%20it%20into%20an%20MSIX%20image%20(.VHD(x)%20or%20.CIM%20file).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20are%20the%20steps%20to%20perform%20expansion%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EDownload%20MSIXMGR%20from%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmsixmgr%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmsixmgr%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EUnzip%20MSIXMGR.zip%20into%20a%20local%20folder%3C%2FLI%3E%0A%3CLI%3EOpen%20%3CSTRONG%3ECommand%20prompt%3C%2FSTRONG%3E%20%3CSTRONG%3E(CMD)%20%3C%2FSTRONG%3Ein%20elevated%20mode%3C%2FLI%3E%0A%3CLI%3ENavigate%20to%20the%20local%20folder%20from%20the%20second%20step%3C%2FLI%3E%0A%3CLI%3ERun%20the%20command%20below%20to%20generate%20an%20MSIX%20image%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CCODE%3Emsixmgr.exe%20-Unpack%20-packagePath%20%3CPATH%20to%3D%22%22%20package%3D%22%22%3E%20-destination%20%3COUTPUT%20folder%3D%22%22%3E%20%5B-applyacls%5D%20%5B-create%5D%20%5B-vhdSize%20%3CSIZE%20in%3D%22%22%20mb%3D%22%22%3E%5D%20%5B-filetype%20%3CCIM%3E%5D%20%5B-rootDirectory%20%3CROOTDIRECTORY%3E%5D%3C%2FROOTDIRECTORY%3E%3C%2FCIM%3E%3C%2FSIZE%3E%3C%2FOUTPUT%3E%3C%2FPATH%3E%3C%2FCODE%3E%3C%2FP%3E%0A%3CP%3EFor%20example%2C%3C%2FP%3E%0A%3CP%3E%3CCODE%3Emsixmgr.exe%20-Unpack%20-packagePath%20%22C%3A%5CUsers%5Cssa%5CDesktop%5CFileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix%22%20-destination%20%22c%3A%5Ctemp%5CFileZillaChanged.vhdx%22%20-applyacls%20-create%20-vhdSize%20200%20-filetype%20%22vhdx%22%20-rootDirectory%20apps%3C%2FCODE%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENavigate%20to%20the%20destination%20folder%20and%20confirm%20that%20an%20MSIX%20image%20(.VHDX)%20was%20created%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3ENote%3A%20%3C%2FFONT%3E%3C%2FSTRONG%3E%3CFONT%20size%3D%224%22%3EThe%20same%26nbsp%3Bcommand%20can%20be%20used%20to%20generate%20CIM%20and%20VHD%20by%20replacing%20the%20filetype%20and%20destination%20path%3C%2FFONT%3E%3CFONT%20size%3D%224%22%3E.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1513238449%22%20id%3D%22toc-hId-1512379314%22%3ECIM%20example%3C%2FH2%3E%0A%3CP%3E%3CCODE%3Emsixmgr.exe%20-Unpack%20-packagePath%20%22C%3A%5CUsers%5Cssa%5CDesktop%5CFileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix%22%20-destination%20%22c%3A%5Ctemp%5CFileZillaChanged.cim%22%20-applyacls%20-create%20-vhdSize%20200%20-filetype%20%22cim%22%20-rootDirectory%20apps%3C%2FCODE%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--294216014%22%20id%3D%22toc-hId--295075149%22%3EVHDX%20example%3C%2FH2%3E%0A%3CP%3E%3CCODE%3Emsixmgr.exe%20-Unpack%20-packagePath%20%22C%3A%5CUsers%5Cssa%5CDesktop%5CFileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix%22%20-destination%20%22c%3A%5Ctemp%5CFileZillaChanged.vhdx%22%20-applyacls%20-create%20-vhdSize%20200%20-filetype%20%22vhdx%22%20-rootDirectory%20apps%3C%2FCODE%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2320429%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2320429%22%20slang%3D%22en-US%22%3EI%20could%20see%20the%20same%20situation.%20Maybe%20it%20is%20due%20to%20the%20MSIX%20package%3F%20Certain%20packages%20can%20be%20created%20as%20CIM%20without%20problems.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2331252%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2331252%22%20slang%3D%22en-US%22%3EIs%20vhdSize%20required%20when%20creating%20a%20CIM%20as%20shown%20in%20the%20example%20above%3F%20When%20looking%20at%20the%20msixmgr.exe%2C%20vhdSize%20is%20only%20used%20for%20VHD%20and%20VHDX.%20I%20am%20trying%20to%20convert%20packages%20to%20CIM%20and%20they%20all%20fail%20with%2080070058.%20I%20tried%20leaving%20vhdSize%20off%20the%20commandline%20but%20I%20receive%20the%20same%20message.%20Trying%20to%20figure%20out%20the%20proper%20commandline.%20I%20also%20read%20their%20might%20be%20an%20issue%20with%20msixmgr%20that%20has%20to%20do%20with%20file%2Ffolder%20length.%20Is%20this%20true%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2335068%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2335068%22%20slang%3D%22en-US%22%3EI'm%20having%20the%20same%20problem%2C%20seems%20like%20a%20bug%20and%20hopefully%20will%20be%20fixed%20soon.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2421668%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2421668%22%20slang%3D%22en-US%22%3EIs%20this%20possibly%20related%20to%20(%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fmsix-packaging%2Fissues%2F437%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fmicrosoft%2Fmsix-packaging%2Fissues%2F437%3C%2FA%3E)%20%3F%20This%20is%20the%20error%20I%20get%20when%20attempting%20to%20package%20a%20sample%20app%20(azure%20data%20studio).%20The%20issue%20is%20the%20same%20even%20when%20files%20are%20in%20a%20very%20shallow%20path%20(c%3A%5Ca)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2572278%22%20slang%3D%22en-US%22%3ERe%3A%20Simplify%20MSIX%20image%20creation%20with%20the%20MSIXMGR%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2572278%22%20slang%3D%22en-US%22%3EThis%20has%20been%20fixed%3C%2FLINGO-BODY%3E
Microsoft

 

Simplify MSIX image creation with the MSIXMGR tool

 

Note: The CIM functionality is currently under development. Please do not use in production environments.

 

This article is an overview of how to use the MSIXMGR tool and its usage in MSIX app attach. MSIXMGR takes an MSIX packaged application (.MSIX) and expands it into an MSIX image (VHD or VHDX). That resulting MSIX image (.VHD(x)) is what we upload to a storage account using WVD MSIX app attach.

 

Prerequisites

To successfully complete the steps in this article please confirm the following steps:

  • Download MSIXMGR from https://aka.ms/msixmgr
  • MSIX packaged application (.MSIX file)
  • Administrative permissions on the machine where the MSIX image will be created.

Note: MSIXMGR can also create CIM files but those can only be used on Windows 10 20H2. This is something we are working to address.

 

Creating MSIX image

Expansion is the process of taking an MSIX packaged application (.MSIX) and unzipping it into an MSIX image (.VHD(x) or .CIM file).

 

These are the steps to perform expansion:

  • Download MSIXMGR from https://aka.ms/msixmgr
  • Unzip MSIXMGR.zip into a local folder
  • Open Command prompt (CMD) in elevated mode
  • Navigate to the local folder from the second step
  • Run the command below to generate an MSIX image

msixmgr.exe -Unpack -packagePath <path to package> -destination <output folder> [-applyacls] [-create] [-vhdSize <size in MB>] [-filetype <CIM | VHD | VHDX>] [-rootDirectory <rootDirectory>]

For example,

msixmgr.exe -Unpack -packagePath "C:\Users\ssa\Desktop\FileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix" -destination "c:\temp\FileZillaChanged.vhdx" -applyacls -create -vhdSize 200 -filetype "vhdx" -rootDirectory apps

 

  • Navigate to the destination folder and confirm that an MSIX image (.VHDX) was created

 

Note: The same command can be used to generate CIM and VHD by replacing the filetype and destination path.

 

CIM example

msixmgr.exe -Unpack -packagePath "C:\Users\ssa\Desktop\FileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix" -destination "c:\temp\FileZillaChanged.cim" -applyacls -create -vhdSize 200 -filetype "cim" -rootDirectory apps

 

VHDX example

msixmgr.exe -Unpack -packagePath "C:\Users\ssa\Desktop\FileZillaChanged_3.51.1.0_x64__81q6ced8g4aa0.msix" -destination "c:\temp\FileZillaChanged.vhdx" -applyacls -create -vhdSize 200 -filetype "vhdx" -rootDirectory apps

 

 

 

 

 

 

 

7 Replies

@Stefan Georgiev Please provide support or example of using PowerShell. My quick dirty test failed, no error, just a GUID folder in the msixmgr\x64 path. I want to loop through all my MSIX pacakges.

 

Clear-Host

$MSIXMGR = "C:\msixmgr\x64"
$MSIXPath = "C:\MSIX1"
$CimFS = "C:\CimFS"

$PackageName = "NotepadPlusPlus_7.9.1.0_x64"

If (!(Test-Path -Path $CimFS\$PackageName)) {New-Item -ItemType directory -Path $CimFS\$PackageName | Out-Null}

CD $MSIXMGR
.\msixmgr.exe -Unpack -packagePath "$MSIXPath\$PackageName.msix" -destination "$CimFS\$PackageName\$PackageName.cim" -applyacls -create -vhdSize 200 -filetype "cim" -rootDirectory apps

I pretty much ran your script with my variables and worked as expected. I started my PowerShell in admin mode that is required since MSIXMGR needs to manipulate drive.

$MSIXMGR = "C:\Users\ssa\Downloads\msixmgr\x64"
$MSIXPath = "C:\Users\ssa\Desktop\"
$CimFS = "C:\temp\date"

$PackageName = "GPUZ_1.0.1.0_x64__74vyvr5aw93s6"

If (!(Test-Path -Path $CimFS\$PackageName)) {New-Item -ItemType directory -Path $CimFS\$PackageName | Out-Null }

CD $MSIXMGR
.\msixmgr.exe -Unpack -packagePath "$MSIXPath\$PackageName.msix" -destination "$CimFS\$PackageName\$PackageName.cim" -applyacls -create -vhdSize 200 -filetype "cim" -rootDirectory apps
I could see the same situation. Maybe it is due to the MSIX package? Certain packages can be created as CIM without problems.
Is vhdSize required when creating a CIM as shown in the example above? When looking at the msixmgr.exe, vhdSize is only used for VHD and VHDX. I am trying to convert packages to CIM and they all fail with 80070058. I tried leaving vhdSize off the commandline but I receive the same message. Trying to figure out the proper commandline. I also read their might be an issue with msixmgr that has to do with file/folder length. Is this true?
I'm having the same problem, seems like a bug and hopefully will be fixed soon.
Is this possibly related to (https://github.com/microsoft/msix-packaging/issues/437) ? This is the error I get when attempting to package a sample app (azure data studio). The issue is the same even when files are in a very shallow path (c:\a)
This has been fixed