You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Edition Windows 10 Enterprise
Version 22H2
Installed on 24/05/2022
OS build 19045.2846
Experience Windows Feature Experience Pack 120.2212.4190.0
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: fdec14ed-d6ca-9bd6-f0f7-de3b30915aa3
Version Independent ID: 7ff21924-0311-5f70-7087-4a1669ee8afe
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
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.
The text was updated successfully, but these errors were encountered: