Forum Widgets
Latest Discussions
App Installer executable without using Microsoft Store
Is it possible to get the App Installer executable offline to install? I need to install it on numerous machines but I do not want to install it using Microsoft Store because our company policy block Microsoft Store. Is there an offline installer for this? https://www.microsoft.com/en-us/p/app-installer/9nblggh4nns1?activetab=pivot:overviewtab
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-disabled
How to install MSIX Package on windows build 17692
Hi, I installed windows preview build 17692 and created MSIX using preview SDK 17692, As per this release notification https://blogs.windows.com/buildingapps/2018/06/19/windows-10-sdk-preview-build-17692-available-now/ (To install the application – just click on the MSIX file) I should be able to install MSIX file by double clicking but this file type seems to be unknown to windows 10 preview build 17692. Am I doing anything wrong here? Or double click is not supported yet, any alternate way to deploy? Regards, Mayank
Deployment Add operation with target volume C: on Package
HI All, I signed one msix package and when i tried to double click and install i am getting this error - AppX Deployment operation failed for package <Package name> with error 0x800B010C. The specific error text for this failure is: Deployment Add operation with target volume C: on Package <package name> from: (<package name>) failed with error 0x800B010C. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. Deployment Add operation with target volume C: on Package <package name> from: (package name) failed with error 0x800B010C. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. Is anyone seen this error before and what could have caused this ? i am trying to install on Win 10 1809. jvintzel can you advise plz ?Windows 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.Error parsing app package
I have been all over the other threads about this question but nothing seems to fix my problem. No matter what I do, my .appinstaller doesn't work. I keep getting : Error in parsing the app package. First off let me say I can access both the .appinstaller file and the .appxbundle file using the direct URLs. Also, I am able to install using .appxbundle and I have a signed certificate. I also tried doing the loopback exemption but that didnt work either. Here is the XML to my .appinstaller <?xml version="1.0" encoding="utf-8"?> <AppInstaller Uri="http://dev.xxxxxx.com/MSIXPrototype/HelloWorldPackage.appinstaller" Version="1.0.7.0" xmlns="http://schemas.microsoft.com/appx/appinstaller/2017/2"> <MainBundle Name="xxxx" Version="1.0.7.0" Publisher="CN=my_cert" Uri="http://dev.xxxxxx.com/MSIXPrototype/HelloWorldPackage_1.0.7.0_x64.appxbundle" /> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="0" /> </UpdateSettings> </AppInstaller> In addition, I have added all the MIME types to my apache httpd.conf file as such : AddType application/appinstaller .appinstaller AddType application/msixbundle .msixbundle AddType application/appxbundle .appxbundle AddType application/msix .msix AddType application/appx .appx I would appreciate any help on this. Thanks!
Machine-wide Package Provisioning (Install for All Users)
Is there no other way to provision (and uninstall) a package for all users other than to use the PowerShell commands (Add-AppProvisionedPackage, Remove-AppPackage)? Context: We are building an ASP.NET Core application hosted as a windows service. Need to display a notification icon in the tray for all users (needs to run at login time) Need to deploy a WPF UI application for all users All components need to be deployed in a single side-loaded MSIX package for all users. As far as I can tell PowerShell is the only way to accomplish this. Unfortunately that is not acceptable for non-technical end users who are used to simply double-clicking on the setup.exe to install software. Does this go against MSIX fundamentals, or is this something that might be possibly added in the future? If there's no other way to do this, could I suggest we introduce an 'AllUsers' restricted capability to the appxmanifest file that flags the package so that when a user double-clicks the package to install it, it gets provisioned for all users (naturally would require prompting for elevated privileges). Similarly, any user who tries to uninstall the package should get prompted for elevated privileges - once elevated, the uninstall should uninstall for all users. Without this functionality, I think we will be stuck using MSI well into the future for our nice new .NET Core applications.
