Forum Widgets
Latest Discussions
The ms-appinstaller protocol has been disabled.
I just found out that users can no longer install my MSIX from my website. This is a WPF application packaged with "Windows Application Packaging Project" (wapproj). When users click the "Get the app" button they now see the error below saying the protocol has been disabled. Why is this? Is this permanent? Is there a way to enable it? There's a short mention of this in the docs but it doesn't mention why this is happening or how to enable it. https://docs.microsoft.com/en-us/windows/msix/app-installer/installing-windows10-apps-web Is this no longer supported? <html> <body> <h1> MyApp Web Page </h1> <a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubApp.msix"> Install app package </a> <a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubAppBundle.msixbundle"> Install app bundle </a> <a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubAppSet.appinstaller"> Install related set </a> </body> </html> The ms-appinstaller protocol has been disabled. Please ask the vendor to update the weblink. For more information go to aka.ms/ms-appinstaller-disabledWindows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.
We use MSIX for one of our LOB applications at my organization. We recently updated some machines to Windows 10 2004 to test it before rolling it out to the rest of the company. One problem we have noticed is that repeatedly that if we update an MSIX package on these systems and then issue a second update, the second update always fails. The event viewer logs multiple errors, most just being generic "the msix package failed to install", etc. However, there is one peculiar one. We found it under: Microsoft-Windows-AppXDeploymentServer/Operational Event Id 497 Error 0x80070002: Opening the Msixvc package from location AppName_x64.msixbundle failed. Please check whether the Msixvc support services are installed. In addition, this is logged under AppXDeployment - Operational: Event ID: 302 Failed to start system service: appxsvc with error: 0x8007045B We could not find any documentation on this error anywhere on MSDN. To work around this, we have to restart the machine. Afterwards it is able to update the MSIX package. Is this a known issue with Windows 10 2004? Can anyone here provide more information or can they provide any suggestions on how to stop this from happening? Edit: We also had a user go ahead and update their machine to Windows 10 2004 without notifying us and now they are getting the same problem as well. Edit #2: I also left this in the feedback hub in Windows 10; if there are any additional channels that I should use, please let me know.
Winforms .exe in MSIX Package Does Not Startup After Auto Update
We are deploying a classic Winforms .exe via MISX. Approximately 20% of the time, the application does not start automatically after an auto update completes. After an update and failed start, we can trigger the application to startup by just typing random text into the Windows search bar. Another way we can trigger it to start is to re-launch the application via the start menu item, but of course two instances will then be running. We are testing with 5 separate workstations that have Windows 10 1903. I have logging in the Main method of the application in program.cs, so I can see that nothing attempts to execute after the auto update until the user intervenes. This has lead me to believe that there is nothing in the application itself causing the issue, but rather the MSIX framework or a configuration option. The appinstaller file - <?xml version="1.0" encoding="utf-8"?> <AppInstaller Uri="{AppInstallerUri}" Version="{Version}" xmlns="<a href="<a href="<a href="http://schemas.microsoft.com/appx/appinstaller/2018" target="_blank">http://schemas.microsoft.com/appx/appinstaller/2018</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/appinstaller/2018</a" target="_blank">http://schemas.microsoft.com/appx/appinstaller/2018</a</a>>" target="_blank"><a href="<a href="http://schemas.microsoft.com/appx/appinstaller/2018</a" target="_blank">http://schemas.microsoft.com/appx/appinstaller/2018</a</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/appinstaller/2018</a</a" target="_blank">http://schemas.microsoft.com/appx/appinstaller/2018</a</a</a>>>"> <MainBundle Name="{Name}" Version="{Version}" Publisher="{Publisher}" Uri="{MainPackageUri}"/> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="true" UpdateBlocksActivation="true"/> <AutomaticBackgroundTask/> <ForceUpdateFromAnyVersion>true</ForceUpdateFromAnyVersion> </UpdateSettings> </AppInstaller> The appxmanifest - <?xml version="1.0" encoding="utf-8"?> <Package xmlns="<a href="<a href="<a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10</a</a>>" target="_blank"><a href="<a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10</a</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10</a</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10</a</a</a>>>" xmlns:uap="<a href="<a href="<a href="http://schemas.microsoft.com/appx/manifest/uap/windows10" target="_blank">http://schemas.microsoft.com/appx/manifest/uap/windows10</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/uap/windows10</a" target="_blank">http://schemas.microsoft.com/appx/manifest/uap/windows10</a</a>>" target="_blank"><a href="<a href="http://schemas.microsoft.com/appx/manifest/uap/windows10</a" target="_blank">http://schemas.microsoft.com/appx/manifest/uap/windows10</a</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/uap/windows10</a</a" target="_blank">http://schemas.microsoft.com/appx/manifest/uap/windows10</a</a</a>>>" xmlns:rescap="<a href="<a href="<a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a</a>>" target="_blank"><a href="<a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a</a>" target="_blank"><a href="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a</a" target="_blank">http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities</a</a</a>>>" IgnorableNamespaces="uap rescap"> <Identity Name="IMSPolicy.local" Publisher="CN=Foo, O=Foo, L=MyTown, S=MyState, C=US" Version="1.0.14.0" /> <Properties> <DisplayName>MyApp</DisplayName> <PublisherDisplayName>FooPublisher</PublisherDisplayName> <Logo>Images\StoreLogo.png</Logo> </Properties> <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" /> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.14393.0" MaxVersionTested="10.0.14393.0" /> </Dependencies> <Resources> <Resource Language="x-generate"/> </Resources> <Applications> <Application Id="App" Executable="$targetnametoken$.exe" EntryPoint="$targetentrypoint$"> <uap:VisualElements DisplayName="MyApp Dev" Description="MyApp application package" BackgroundColor="transparent" Square150x150Logo="Images\Square150x150Logo.png" Square44x44Logo="Images\Square44x44Logo.png"> <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png" Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png"/> <uap:SplashScreen Image="Images\SplashScreen.png" BackgroundColor="white"/> </uap:VisualElements> </Application> </Applications> <Capabilities> <Capability Name="internetClient" /> <rescap:Capability Name="runFullTrust" /> </Capabilities> </Package>
Shortcut pointing to Batch script (.bat file) - PSF Tool not worked.
Hi All, Scenario: I have an app with multiple shortcuts, in those one shortcut's Target is "cmd.exe" and argument is path of a batch script file(.bat file). I have tried to create MSIX package with the help of PSF Tool. while testing I am able to launch every shortcut, except this one (which has batch script). I tried the below things: 1. As we know there is no communication between MSIX container and the native cmd.exe file, I have copied cmd.exe (which is not recommendable) file into msix package and tried to launch the shortcut. It didn't work. 2. In config.json file, replaced cmd.exe with the psflauncher.exe in place of target, which mean this psflauncher will call the .bat file to execute. It didn't work 3. In config.json file, placed .bat file path in Target place with out any arguments. It didn't work. Is there any thing else to try other than above, please advise and guide. Thanks in Advance.
Can we have multiple fixes at the same time
Dear Experts, Assume i have a msix package that needs multiple fixes like 1)FRF 2)Registry 3)Trace Can we have the three fixes together ? i have been trying this but was not lucky enough.. Below is the config.json i was trying { "applications": [ { "id": "MyPackagex64", "executable": "VFS/ProgramFilesX64/ConEmu/MyPackage64.exe", "workingDirectory": "VFS/ProgramFilesX64/MyPackage" }, { "id": "ConEmuAAx64A1", "executable": "VFS/ProgramFilesX64/ConEmu/MyPackage64.exe", "workingDirectory": "VFS/ProgramFilesX64/MyPackage" } ], "processes": [ { "executable": "MyPackage64", "fixups": [ { "dll": "FileRedirectionFixup64.dll", "config": { "redirectedPaths": { "knownFolders": [ { "id": "ProgramFilesX64", "relativePaths": [ { "base": "MyPackage/", "patterns": [ ".*" ] } ] } ] } } }, { "dll": "TraceFixup64.dll", "config": { "traceMethod": "outputDebugString", "traceLevels": { "default": "always" }, "breakOn": { "filesystem": "unexpectedFailures" } } } ] }, { "executable": "MyPackage64", "fixups": [ { "dll": "FileRedirectionFixup64.dll", "config": { "redirectedPaths": { "knownFolders": [ { "id": "ProgramFilesX64", "relativePaths": [ { "base": "MyPackage/", "patterns": [ ".*" ] } ] } ] } } }, { "dll": "TraceFixup64.dll", "config": { "traceMethod": "outputDebugString", "traceLevels": { "default": "always" }, "breakOn": { "filesystem": "unexpectedFailures" } } } ] } ] }
MSIX Command Line Argument
Hey guys, I'm trying to convert an App-V package to an MSIX package. I've tried using the packager to make a new package from scratch, and I've tried converting the package. Normally, my program's shortcut launches an executable with a command line argument. MSIX doesn't seem to support this in the manifest XML file, unlike App-V. I've listed a comparison of both below. App-V manifest item (has arguments, is working): <appv:Extension Category="AppV.Shortcut"> <appv:Shortcut> <appv:File>[{Programs}]\Microsoft Dynamics\GP 2015\GP.lnk</appv:File> <appv:Target>[{ProgramFilesX86}]\Microsoft Dynamics\GP2015\Dynamics.exe</appv:Target> <appv:Icon>[{ProgramFilesX86}]\Microsoft Dynamics\GP2015\Dynamics.exe.0.ico</appv:Icon> <appv:Arguments>Dynamics.set</appv:Arguments> <appv:WorkingDirectory>[{ProgramFilesX86}]\Microsoft Dynamics\GP2015\</appv:WorkingDirectory> <appv:ShowCommand>1</appv:ShowCommand> <appv:ApplicationId>[{ProgramFilesX86}]\Microsoft Dynamics\GP2015\Dynamics.exe</appv:ApplicationId> </appv:Shortcut> </appv:Extension> MSIX manifest item (doesn't have arguments, isn't working): <Application Id="DYNAMICS" Executable="VFS\ProgramFilesX86\Microsoft Dynamics\GP2015\Dynamics.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements BackgroundColor="transparent" DisplayName="GP" Square150x150Logo="Assets\Square150x150Logo.png" Square44x44Logo="Assets\Square44x44Logo.png" Description="GP"> <uap:DefaultTile Wide310x150Logo="Assets\Wide310x150Logo.png" Square310x310Logo="Assets\Square310x310Logo.png" Square71x71Logo="Assets\Square71x71Logo.png" /> </uap:VisualElements> </Application> How can I edit my MSIX package so that the start menu items launch with the appropriate command line arguments?MSIX Packageing Tool / signtool certificate issues
1) I have a valid (paid for) code signing certificate from a well known CA that has a password so I can't use the in tool signing (which is something you should support!). The 17134 SDK is present. So I pulled the command out of the log file and modified as follows (but with the proper password): "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17134.0\x64\signtool.exe" sign /a /v /debug /fd SHA256 /f "C:\Users\Admin\Desktop\strongname.pfx" /p "xxxThePasswordxxx" "C:\Users\Admin\Desktop\TMEdit\Setup_TMEdit.msix" Which fails. The relevant output being: After EKU filter, 1 certs were left. After expiry filter, 1 certs were left. After Private Key filter, 1 certs were left. The following certificate was selected: Issued to: TMurgent Technologies, LLP Issued by: COMODO RSA Code Signing CA Expires: Mon Jun 21 19:59:59 2021 SHA1 hash: A5CD580A89C438FB9B87753BB05F383560EB366F The following additional certificates will be attached: Issued to: COMODO RSA Code Signing CA Issued by: COMODO RSA Certification Authority Expires: Mon May 08 19:59:59 2028 SHA1 hash: B69E752BBE88B4458200A7C0F4F5B3CCE6F35B47 Done Adding Additional Store SignTool Error: An unexpected internal error has occurred. Error information: "Error: SignerSign() failed." (-2147024846/0x80070032) #2 Reading up on this we get to cause of issue number 2: The name of the publisher in CN form in the manifest (input from the MSIX Manifest tool) must exactly match that of the certificate: Inside the certificate, The publisher name is CN=TMurgent Technologies, LLP which, unfortunately, is the legal name of the entity so that isn't changing! The MSIX Package Tool does not allow a comma in the input field.
