Open jbennink opened 1 year ago
Been getting this with a few users recently too. Tends to be that a redownload of the .appinstaller and a PC restart that fixes it, though I've had some users need to go the extra mile and use DISM
to restore their machine's health. Seems like some sort of weird caching issue but not sure
@jbennink - As of now, this is only available for Win 11. For Win 10, you can try to uninstall and reinstall.
Are there any plans to backport persistent identities for Win 10?
@jbennink @benaclejames Please see this thread for the cause of the random version-change-related install failures (with workaround):
I ran into this issue recently and have used this guide to fix it. On Windows 11 this seems to do the trick. But now I am hearing from Windows 10 machines that they can't install the app package and get an error "Cannot open app package" reason: "Error in parsing the app package".
The only thing I changed in the appinstaller file is the version number, and the msixbundle url. When I go back to a version from before the publisherbridge change it also works!
Can someone confirm this is supportong on windows 10 22H2, I'm testing on a VM:
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.