User Profile
Toastgun
Copper Contributor
Joined 9 years ago
User Widgets
Recent Discussions
AppInstaller OnLaunch Update check does not start the application after update
Hello We are currently developing an application that needs to check updates before launch. Therefore we implemented the following Appinstaller: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <AppInstaller Uri="https://somehost/someappinstaller.appinstaller" Version="1.0.1.36" xmlns="http://schemas.microsoft.com/appx/appinstaller/2018"> <MainPackage Name="SomeCompany.SomeApp" Version="1.0.1.36" Publisher="CN=Somepublisher" Uri="https://somehost/someupdatedpackage.msix" ProcessorArchitecture="x86"/> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="true" UpdateBlocksActivation="true"/> <AutomaticBackgroundTask/> <ForceUpdateFromAnyVersion>true</ForceUpdateFromAnyVersion> </UpdateSettings> </AppInstaller> If we now have version 1.0.0.37 of SomeApp installed a window will show up to guide us to update the app: If i now click update the app will update but it will not start afterwards. The Eventlog is showing Eventlog Id 323 with error 0x80070490 reference the old version of SomeApp: Fehler 0x80070490: Das Paket "SomeCompany.SomeApp_1.0.0.37_x86__wpr0009ygztjt" kann not be registered: Element not found. When I try to launch the app using it's app alias with the command line I get the following error This message is basically saying that the file could not be accessed but what troubles me most that the path is pointing to version 1.0.0.37 so the version which has been replaced by the update. My fear is the following: The appinstaller has currently a bug which is not pointing to the outdated file after update. So the app will not launch after an update. Or am I using something wrong here?Cloud only Entra ID Domain Services and Seamless SSO from Entra ID Joined machines
Hello I am currently implementing Entra ID Domain Services with one customer (he has no on-premises active directory). We now face the issue that an Entra ID joined client is not able to access ressources on machines that are joined to Entra ID Domain Services without entering his username and password. The authentication fails with incorrect username and password (event id 200) message and the Security-Kerberos eventlog reports that it was not able to contact a domain controller for the AzureAd Domain (so he is not using the Domain name of the target domain). However has someone already tried this and is there something I am overlooking or is that something that simply can not work. Thank you very much in advance for any ideas.iOS Microsoft Defender Compliance Policy not showing compliance despite successfull setup of the app
I am having an issue on multiple tenants and after a lot of try and error I am not getting it. All tenant enroll their devices through the Apple DEP in supervised mode and deploy the Microsoft Defender app using a VPP token with a device based license. The app is successfully installed on the devices and users are able to sign in to the app and the defender is showing everything is green. However the Compliance policy does not switch to compliant even after long waiting and the security center is not showing the device. Strangely this is not happening always... around half of the enrollments switch to compliant while the other half does not. Sometimes the issue also resolve by reinstalling the app. I have this issue on multiple tenants. I am using the Filter profile with auto enrollment (which also does not start always) but the VPN onboarding has the same issue. So if someone else had this issue and has an idea where this comes from: Please give me a comment.Re: MSIX package signing issue with certificate installed in a certificate store
This issue looks to me more related to your package rather then the certificate (As the message states: Sign tool Error: This file format cannot be signed because it is not recognized.). I had this issue once and in the end recreating the package with fresh binaries. You can try building a very simple MSIX/APPX package and sign it. That way you can make sure that it is really not about the certificate.Re: Write to non virtualized %APPDATA% location from MSIX installed binary
davidanthoff Yes there is. Check out the following article from Advanced Installer: https://www.advancedinstaller.com/msix-disable-registry-file-redirection.html Please keep in mind that packages created this way can not be directly installed nor can the deployed through the Microsoft Store. But you can install them using command line or an MDM solution.
