Error installing WindowsAppSDK on windows server 2022

[klemensurban]

Package deployment result : 0x8000000b Install failed. Please contact your software vendor.
ExtendedError: 0x8000000b The operation attempted to access data outside the valid range
ErrorMessage: Deployment Add operation with target volume C: on Package Microsoft.WindowsAppRuntime.1.1_1003.565.600.0_x64__8wekyb3d8bbwe from: (MSIA653.tmp) failed with error 0x8000000B. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.One or more install operations failed. Result: 0x8000000b

when attemting to install on windows server 2022

no support on server 2022 (2019?)? -> no WinUI 3 on Terminal Servers .. -> have to stay with WPF ?

best regards k.u.

[sachintaMSFT]

WinAppSDK framework package failing to install on Server 2022 is a known issue tracked internally by https://task.ms/40529191. The fix for this issue is currently scheduled to be serviced to Server 2022 in October.

Are you seeing the issue on Sever 2019, as well ?

[klemensurban]

Hi, i was just able to test this on windows server 2019; on this os WinAppSDK install without an error / a warning best regards, klemens Bundesministerium für Bildung, Wissenschaft und Forschung Abteilung Praes/13 – IKT DI Klemens Urban Leiter Referat Praes/13b +43 1 531 20-9720 Minoritenplatz 5, 1010 Wien ***@***.******@***.***> www.bmbwf.gv.at<http://www.bmbwf.gv.at/> Von: sachintaMSFT ***@***.***> Gesendet: Montag, 8. August 2022 22:02 An: microsoft/WindowsAppSDK ***@***.***> Cc: Urban Klemens ***@***.***>; Author ***@***.***> Betreff: Re: [microsoft/WindowsAppSDK] Error installing WindowsAppSDK on windows server 2022 (Issue #2829) WinAppSDK framework package failing to install on Server 2022 is a known issue tracked internally by https://task.ms/40428533. Are you seeing the issue on Sever 2019, as well ? — Reply to this email directly, view it on GitHub<#2829 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOFSNBF7245YBB2G3D2L23VYFRRZANCNFSM55ZHYW2A>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[sachintaMSFT]

Thanks @klemensurban for testing. That is in line with our expectation that the issue is only on Windows Server 2022. As slated earlier, the fix will be in the OS itself and the fix is currently scheduled to be serviced to Server 2022 in October.

[Andrew-lll]

@sachintaMSFT @davidortinau

Scope:

It appears that all current MAUI developers working on Server 2022 are blocked by this. Unfortunately, waiting months until October to be able to develop apps in .net MAUI is simply not possible for our developers (which is probably the case elsewhere, and many developers must run Server to emulate the prod env).

Workarounds?

Is there any intermediate step that can be done to workaround the issue until then:

• a manually installable optional patch for Server 2022?
• workaround instructions to manually install WindowsAppRuntime1.1?
• a last installable version of WindowsAppRuntime? Previous versions of VS2022 preview + MAUI (VS2022 17.2?) have ran without issue on Server 2022 - is there an earlier version of the WindowsAppRuntime that we can manually roll back to, or that MAUI can roll back to in order to regain Server 2022 support?

Prevention:

For the MAUI team, adding Server 2022 to the pre-release testing pipeline would catch these issues before they reach the customer

[michael-hawker]

This has been blocking the Windows Community Toolkit for months now in trying to update our new infrastructure for testing and now our main repository as well. We are stuck on 1.0.x until this is resolved.