Manually triggering update of an app when running windows in assigned access (Kiosk mode) doesn´t work. I have read others facing the same issue and it feels like there is a bug in windows Kiosk mode. But maybe there is some reason for this behaviour? I have an app that I sideload using an appinstaller ..
I have created a wpf app and have been learning how to deploy it as a side loaded windows store app through an appinstaller package. I now want to launch the app through a shell command with parameters. I did setup a protocol, but it doesnt seem to open the app. to make things worse ..
I’m trying to follow the Microsoft documentation but I’m confused as to why my appinstaller is failing: <?xml version="1.0" encoding="utf-8"?> <AppInstaller xmlns="http://schemas.microsoft.com/appx/appinstaller/2018" Uri="https://xxxxxx.blob.core.windows.net/installer/Package.appinstaller" Version="18.104.22.168"> <MainPackage Name="MyApp" Version="12.21.289.0" Publisher="CN=xxxxxx" ProcessorArchitecture="x64" Uri="https://xxxxxx.blob.core.windows.net/installer/MyApp.msix"/> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="1" /> <AutomaticBackgroundTask/> </UpdateSettings> </AppInstaller> If I run the MSIX file, it installs as it should. I’ve been trying to follow this: https://docs.microsoft.com/en-us/windows/msix/desktop/azure-dev-ops ..