msix-packaging icon indicating copy to clipboard operation
msix-packaging copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

[BUG]

Open jbyway opened this issue 3 years ago • 4 comments

Project MSIX SDK or Win7Msix

Describe the bug Creation of CIM files from a MSIX package fails with HRESULT 0x80070050 or 0x80070003.

To Reproduce

  • Error appears to be repeatable when original MSIX package includes long file paths nested within the file (250+ characters). Tested with VSCode package created by myself.
  • Failure message occurs after non fatal error occurs when attempting to delete the temp directory that's created to unpack the msix in to and called within the msixmgr.cpp file at "createAndAddtoCIM".
  • Temp directory that remains shows parts of the msix contents that were not deleted and presumably failed to be extracted into the cim tmp files in the destination directory. These files are above 250 characters.
  • Moving the msixmgr.exe to c:\x\msixmgr.exe and changing the temp directory to not use the GUID seems to resolve if msix files are then below ~250+ characters when extracted. Doing this by modifying the line in msixmgr.cpp "std::wstring tempDirPathString = currentDirectory + L"\unpack";" and replacing the "+ uniqueIdString" with "\unpack" and recompiling msixmgr.exe allowed my cim to create. Screenshot 2021-03-17 143101 Screenshot 2021-03-17 161415

Expected behavior Files should be unpacked to the temp directory and subsequently placed into a CIM file. Attempting with an alternative MSIX package works when file path is shorter during unpack stage.

Screenshots If applicable, add screenshots to help explain your problem.

Platform Windows 10 20H2

Additional context Attempted with NotePadPlusPlus which was successful. VSCode failed. msixtrace_000001.zip

jbyway avatar Mar 17 '21 05:03 jbyway

I have the same problem with different apps. (Visual Studio Code, Visual Studio, SQL Management Studio...) With the vhdx format I do not have the problem, but I prefer the cim format to get best performance. Do you have a estimated resolution date for this problem?

juanpecatala avatar Mar 24 '21 12:03 juanpecatala

I have the same issue, tried converting Adobe Acrobat MSIX to CIM

PMLIO avatar May 06 '21 17:05 PMLIO

Same issue with Azure Data Studio

iancohn avatar Jun 04 '21 14:06 iancohn

Also having the same issue converting applications like Adobe illustrator, creating file paths like "C:_\3909c748-1052-4783-b24e-e4878cfe7c26\AdobeIllustrator-25.2.3_1.0.1.0_x64__fzp20gpn88db2\VFS\ProgramFilesX64\Adobe\Adobe Creative Cloud Experience\js\node_modules\ref-napi\node_modules\node-addon-api\src\Release\obj\nothing\nothing.tlog", exceeding the 260 character limit.

dextraa9791 avatar Jun 15 '21 12:06 dextraa9791

https://github.com/microsoft/msix-packaging/pull/463

Issue has been fixed in the above Pull Request

pratiksinha07 avatar Apr 25 '23 06:04 pratiksinha07