WindowsAppSDK
WindowsAppSDK copied to clipboard
microsoft
`WindowsAppSDKRuntime` looks like version mismatch
why?
Originally posted by @shelllet in https://github.com/microsoft/WindowsAppSDK/discussions/2626#discussioncomment-2955347
You've installed 1.1.0 but at runtime are looking for >=1.1.1. Try the 1.1.1(+) installer and you should be right as rain
The hint is in the package full names' version and the Bootstrap initialize MinVersion parameter
Microsoft.WindowsAppRuntime.1.1_1000.516.2156.0_...
Microsoft.WindowsAppRuntime.1.1 == release 1.1
1000.516.2156.0 == MSIX major version encodes minor.patch as NNPPP thus 1000 == 01.000 == 1.0. Put it all together and you get release 1.1.0
OTOH the Bootstrapper is looking asking for minversion = 1001.524.1918.0, i.e. version must be >= 1001.524.1918.0. That MSIX major version element = 1001 which as mentioned is minor.patch encoded as NNPPP == 01.001 == 1.1 and thus it's requiring >= 1.1.1
Also simply on the face of it the packages are both release 1.1 but the minversion MSIX version number requested is higher than the MSIX version number installed. 1001.524.1918.0 > 1000.516.2156.0
but there is no 1.1.1 version of WindowsAppRuntime for download.
i remember that i download latest version of WindowsAppRuntime in this link https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads
but there is no 1.1.1 version of WindowsAppRuntime for download.
i remember that i download latest version of WindowsAppRuntime in this link https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/downloads
Hmmm. I thought that link was updated to latest 1.1.x when a servicing update was released. Will look into it
As mentioned if you scroll down a bit you can find downloads for every release down to the individual patch level. Try the 1.1.1 installer from there
@shelllet Scroll a bit further down -
this does't work either, it seems like to load Microsoft.WinAppRuntime.DDLM.1000.468.658.0-x6-p2_1000.468.658.0_x64__8wekyb3d8bbwe , but this is not applicable.
That's odd how the x64 package installed but it thinks the x86 is already present and fails.
Please run the following command and share the output:
powershell -c "$(get-appxpackage microwinapprun*).packagefullname"
Is your app x86 or x64? Bootstrapper looks to match a DDLM package matching your architecture so knowing that plus the get-appxpackage output will help to figure out what's going on
it seems like to load Microsoft.WinAppRuntime.DDLM.1000.468.658.0-x6-p2_1000.468.658.0_x64__8wekyb3d8bbwe , but this is not applicable.
BTW that's not being loaded. Bootstrapper is enumerating all framework packages registered to your account and FOREACH checking if the package's Name starts with the expected prefix, then checks if it meets the requested majorMinorVersion, architecture and minVersion. Packages matching the expected prefix are WinAppSDK packages; after that point you're guaranteed to get a message logged if it meets all criteria or if it fails along the way, that it doesn't match and what check it failed.
All part of the enumeration algorithm. Nothing gets loaded until there's a successful matching candidate from the enumeration.
Your debugger output pane shows only 1000.* packages being enumerated. Makes sense it fails as you're looking for >=1.1.1. Question is if 1.1.1 packages are installed and if not why. So next step is get-appxpackage
No real keyboard atm or I'd share a link to the specific enumeration code. I think it's FindViaEnumeration() in dev/WindowsAppSDK_Bootstrap(?)/*.cpp
powershell -c "$(get-appxpackage micro_win_apprun*).packagefullname"
That's odd how the x64 package installed but it thinks the x86 is already present and fails.
Please run the following command and share the output:
powershell -c "$(get-appxpackage micro_win_apprun*).packagefullname"
Is your app x86 or x64? Bootstrapper looks to match a DDLM package matching your architecture so knowing that plus the get-appxpackage output will help to figure out what's going on
C:\Users\admin>powershell -c "$(get-appxpackage microwinapprun*).packagefullname"
C:\Users\admin>powershell -c "$(get-appxpackage microsoft.winapprun*).packagefullname" Microsoft.WinAppRuntime.DDLM.2.460.358.0-x6_2.460.358.0_x64__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.2.460.358.0-x8_2.460.358.0_x86__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.3.469.1654.0-x6_3.469.1654.0_x64__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.3.469.1654.0-x8_3.469.1654.0_x86__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.468.658.0-x6-p2_1000.468.658.0_x64__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.468.658.0-x8-p2_1000.468.658.0_x86__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.485.2229.0-x6-p3_1000.485.2229.0_x64__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.485.2229.0-x8-p3_1000.485.2229.0_x86__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x6_1000.516.2156.0_x64__8wekyb3d8bbwe Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x8_1000.516.2156.0_x86__8wekyb3d8bbwe
when i reinstall Microsoft.WindowsAppRuntime.DDLM.1.1.msix from unzipped folder.
Microsoft.WinAppRuntime.DDLM.1001.524.1918.0-x6_1001.524.1918.0_x64__8wekyb3d8bbwe showed in the list.
may be the WindowsAppRuntimeInstall.exe can't install Microsoft.WinAppRuntime.DDLM.1001.524.1918.0-x6_1001.524.1918.0_x64__8wekyb3d8bbwe
From the list of DDLMs I’d guess you’ve previously run the installer for…
- 1.0.2
- 1.0.3
- 1.1-preview2
- 1.1-preview3
- 1.1.0
@sachintaMSFT @cwruss tag you're it
From the list of DDLMs I’d guess you’ve previously run the installer for…
- 1.0.2
- 1.0.3
- 1.1-preview2
- 1.1-preview3
- 1.1.0
@sachintaMSFT @cwruss tag you're it
👍 i also ran 1.1.1 ( WindowsAppRuntimeInstall.exe) Now, i can confirmed the 1.1.1 version of WindowsAppRuntimeInstall.exe can't work correctly.
👍 i also ran 1.1.1 ( WindowsAppRuntimeInstall.exe) Now, i can confirmed the 1.1.1 version of WindowsAppRuntimeInstall.exe can't work correctly.
Several bugs were fixed recently. Does this repro with the 1.1.3 installer?