Error
2 TopicsEncountered 0x80131500 code while using MSIX Packaging Tool
Hi Guys, Recently, when I tried to use MSIX Packaging Tool to convert the exe file to MSIX, I got the 0x80131500 error. Checking the log, I got the following part [2025-07-31 7:14:04 PM] [Debug] MakeAppx : error: Failure at (packageWriter3->AddPayloadFiles( addedFiles, preparedFiles, performanceOptions.memoryLimit)) - 0x8007007b - The filename, directory name, or volume label syntax is incorrect. [2025-07-31 7:14:04 PM] [Debug] Cleaning up output file "\\?\%UserProfile%\OneDrive\Desktop\My-Package_1.0.0.0_x64__tn3vmbmc1d5kj_1.msix". [2025-07-31 7:14:04 PM] [Debug] MakeAppx : error: Failure at (CreatePackage( overwrite, hashAlgorithm, fileList, outputPath, manifestStream.Get(), forceCompressionNone, performanceOptions, encryptPackage, encryptionOptions, cgmPath, mainPackagePathForResourceExemption, makepriExeFullPath)) - 0x8007007b - The filename, directory name, or volume label syntax is incorrect. [2025-07-31 7:14:04 PM] [Debug] MakeAppx : error: Package creation failed. [2025-07-31 7:14:04 PM] [Debug] MakeAppx : error: 0x8007007b - The filename, directory name, or volume label syntax is incorrect. [2025-07-31 7:14:04 PM] [Error] MakeAppx.exe failed, exit code = 1 [2025-07-31 7:14:04 PM] [Debug] Finalizing the conversion state [2025-07-31 7:14:04 PM] [Debug] Getting environment object from %UserProfile%\AppData\Local\Packages\Microsoft.MSIXPackagingTool_8wekyb3d8bbwe\LocalState\MsixGenerator.ConversionState.xml [2025-07-31 7:14:04 PM] [Warning] Error Occurred: Microsoft.Msix.Utils.ProcessRunner.ProcessRunnerException: Process MakeAppx.exe failed with exit code 1. at Microsoft.Msix.Utils.ProcessRunner.ProcessRunnerBase.ValidateExitCode(Int32[] validCodes) at Microsoft.ApplicationVirtualization.Packaging.Packager.FinalizePackageViaMakeAppx(IPackageFiles packageFiles, String manifestPath, String appvManifestPath, String registryHivePath, Boolean useExistingRegisterHive, String userRegistryHivePath, String userClassesRegistryHivePath, String packagePath, String msixMappingPath, CompressionOption compression, MsixPackageInputProperties msixPackageInputProperties, CancellationTokenSource cancellationTokenSource) at MsixGenerator.MsixPackageEditor.FinalizePackage(CancellationTokenSource cancellationTokenSource, Boolean modifyExistingPackage) at MsixPackagingTool.ViewModel.PackageEditorWorkflow.MasterPackageEditorViewModel.SavePackageEditorChanges_BackgroundWorker(Object sender, DoWorkEventArgs doWorkEventArgs) at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) So far, it seems that \\?\%UserProfile% is causing the issue. But I am not sure how to solve it. The following is the manifest file I used. <?xml version="1.0" encoding="utf-8"?> <Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:uap10="http://schemas.microsoft.com/appx/manifest/uap/windows10/10" xmlns:desktop7="http://schemas.microsoft.com/appx/manifest/desktop/windows10/7" xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" IgnorableNamespaces="uap uap10 desktop7 rescap"> <!--Package created by MSIX Packaging Tool version: 1.2024.405.0--> <Identity Name="My-Package" Publisher="CN=Dummy Publisher" Version="1.0.0.0" ProcessorArchitecture="x64" /> <Properties> <DisplayName>My-Package</DisplayName> <PublisherDisplayName>Dummy Publisher</PublisherDisplayName> <Description>Dummy description.</Description> <Logo>Assets\StoreLogo.png</Logo> <uap10:PackageIntegrity> <uap10:Content Enforcement="on" /> </uap10:PackageIntegrity> </Properties> <Resources> <Resource Language="en-us" /> </Resources> <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22000.1" /> </Dependencies> <Applications> <Application Id="MyApplication" Executable="VFS\AppVPackageDrive\MyApplication\MyApplication.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements BackgroundColor="transparent" DisplayName="MyApplication" Square150x150Logo="Assets\MYAPPLICATION-Square150x150Logo.png" Square44x44Logo="Assets\MYAPPLICATION-Square44x44Logo.png" Description="MyApplicatiion"> <uap:DefaultTile Wide310x150Logo="Assets\MYAPPLICATION-Wide310x150Logo.png" Square310x310Logo="Assets\MYAPPLICATION-Square310x310Logo.png" Square71x71Logo="Assets\MYAPPLICATION-Square71x71Logo.png" /> </uap:VisualElements> </Application> </Applications> <Capabilities> <rescap:Capability Name="runFullTrust" /> </Capabilities> </Package> Could someone help me solve this issue? Thanks!82Views0likes1CommentSignTool Error: This file format cannot be signed because it is not recognized.
Trying to sign the msix signtool sign /fd sha256 /f $env:CODEBUILD_SRC_DIR\qwe.pfx /t http://timestamp.digicert.com "$env:CODEBUILD_SRC_DIR\PackageBuild\$APP_VERSION\qweqwe-$env:BRANCH_$APP_VERSION.msix" SignTool Error: This file format cannot be signed because it is not recognized. SignTool Error: An error occurred while attempting to sign: C:\codebuild\tmp\output\src605\src\asd.org\zxc\asd\PackageBuild\0.40.0.0\qweqe-0.40.0.0.msix Using AWS windows 2019.2 core codebuild image Installed windows 11 SDK 10.0.22621.0 when I copy the msix to redular windows 2019 server and run the same command - no issues. package has signed. MakeAppx from the same installation works also with no issues.1.6KViews0likes0Comments