Hello,
Thank you very much for the sent resources!
If possible, could you please upload your MSIX package somewhere (e.g. on GDrive) and send me a download link for that as well?
I've had the wrong impression that somehow with the download link, we can obtain the package, but that's not the case with Microsoft Store - we can only install it from there.
The reason why we need the package is so we can debug it further to find the root cause of this.
I apologize this has taken this long and I thank you for your further patience on this (hopefully we will solve this asap).
Best regards,
Catalin
Suggested Articles
Re: MSIX "elevation" capability not being respected - Windows Store app
email sent with download link
Re: MSIX "elevation" capability not being respected - Windows Store app
Hello Darren,
Just wanted to update you on this issue that we are investigating.
So it looks like there's a problem with the RegOpenKeyExW function since the 24H2 update - this function often returns NULL.
We are currently investigating possible methods that we can use instead of this until something official from Microsoft hopefully comes.
Thank you for your further patience on this!
Best regards,
Catalin
Just wanted to update you on this issue that we are investigating.
So it looks like there's a problem with the RegOpenKeyExW function since the 24H2 update - this function often returns NULL.
We are currently investigating possible methods that we can use instead of this until something official from Microsoft hopefully comes.
Thank you for your further patience on this!
Best regards,
Catalin
Re: MSIX "elevation" capability not being respected - Windows Store app
Excellent, thank you for the update
Re: MSIX "elevation" capability not being respected - Windows Store app
wingers,
As @Catalin indicated, this is likely a Microsoft issue.
I have been tracking my own issue, and will additional provide symptoms that you can verify against your issue to see if they line up. Additionally, I have seen some other reports of issues with an MSIX package on 24h2:
* https://techcommunity.microsoft.com/dis ... orm=MG0AV3
* https://answers.microsoft.com/en-us/win ... orm=MG0AV3
* An email report from a friend with a package not working on 24H2 that works on 23H2. That app did not involve elevation, but I am awaiting more details.
In my case, the elevation occurs, and then the new app dies before showing any UI, and no error dialogs appear. However, there are additional symptoms that show and elevation may or may not be the cause.
* In the event viewer, Windows Logs\Applications: Category=.Net Runtime EventId=1026
* In Process Monitor you can verify a second launch of the application, and after it starts you can double-click on a line for the process, go to the Process tab and look for a property named "Integrity". A value here of "High" means that elevation did occur.
This shows that elevation occurred, and the .Net Runtime event (in my case) points to a "Type" issue in the inner exception which occurred as the main window's XAML was being processed, causing the crash. I am still investigating this issue and will eventually be reporting it to Microsoft as a conflict for some packages as soon as I finish my investigation. In fact, in my case there are three WPF applications in the package and only one shows the issue.
You might want to check for these symptoms and report back on if they match up.
As @Catalin indicated, this is likely a Microsoft issue.
I have been tracking my own issue, and will additional provide symptoms that you can verify against your issue to see if they line up. Additionally, I have seen some other reports of issues with an MSIX package on 24h2:
* https://techcommunity.microsoft.com/dis ... orm=MG0AV3
* https://answers.microsoft.com/en-us/win ... orm=MG0AV3
* An email report from a friend with a package not working on 24H2 that works on 23H2. That app did not involve elevation, but I am awaiting more details.
In my case, the elevation occurs, and then the new app dies before showing any UI, and no error dialogs appear. However, there are additional symptoms that show and elevation may or may not be the cause.
* In the event viewer, Windows Logs\Applications: Category=.Net Runtime EventId=1026
* In Process Monitor you can verify a second launch of the application, and after it starts you can double-click on a line for the process, go to the Process tab and look for a property named "Integrity". A value here of "High" means that elevation did occur.
This shows that elevation occurred, and the .Net Runtime event (in my case) points to a "Type" issue in the inner exception which occurred as the main window's XAML was being processed, causing the crash. I am still investigating this issue and will eventually be reporting it to Microsoft as a conflict for some packages as soon as I finish my investigation. In fact, in my case there are three WPF applications in the package and only one shows the issue.
You might want to check for these symptoms and report back on if they match up.
Re: MSIX "elevation" capability not being respected - Windows Store app
The report to Microsoft for the corresponding to my possibly similar issue mentioned above may be found at: https://techcommunity.microsoft.com/dis ... ct/4359996
Re: MSIX "elevation" capability not being respected - Windows Store app
Hey Tim,
Thank you for your contribution on this!
We have indeed concluded that this is a Microsoft bug within the new 24H2 OS after carefully analyzing this with the App Assure Team from Microsoft.
Until an official fix is available, both we and the team from Microsoft are trying different possible workarounds. So far we haven't managed to find one that works.
So far, our issues were only regarding the elevation and the root cause was that some registry entries were not available/couldn't be read.
However, in your case, this seems like 24H2 brings in more issues, not just the elevation one.
Fingers crossed that Microsoft manages to fix this in a timely manner.
Best regards,
Catalin
Thank you for your contribution on this!
We have indeed concluded that this is a Microsoft bug within the new 24H2 OS after carefully analyzing this with the App Assure Team from Microsoft.
Until an official fix is available, both we and the team from Microsoft are trying different possible workarounds. So far we haven't managed to find one that works.
So far, our issues were only regarding the elevation and the root cause was that some registry entries were not available/couldn't be read.
However, in your case, this seems like 24H2 brings in more issues, not just the elevation one.
Fingers crossed that Microsoft manages to fix this in a timely manner.
Best regards,
Catalin
Re: MSIX "elevation" capability not being respected - Windows Store app
Hello,
This has been fixed in version 22.4 of Advanced Installer, released on January 29th, 2025.
Please note that this is only a workorund we found with the help of Microsoft team until a fix will be available on their end.
Best regards,
Catalin
This has been fixed in version 22.4 of Advanced Installer, released on January 29th, 2025.
Please note that this is only a workorund we found with the help of Microsoft team until a fix will be available on their end.
Best regards,
Catalin