Share via

Windows App - Compatibility with Windows 10 LTSC and Windows 11 IoT Enterprise LTSC

Brandon Heinz 20 Reputation points
2026-02-02T14:38:26.9233333+00:00

Hello all,

OS:

Windows 10 Enterprise LTSC Build 1809

Windows 11 IoT Enterprise LTSC 24H2

We currently have two OS mentioned above for our local devices that connect to a VMWare platform. We will be soon migrating to Azure. Issue is we would not want to use remote desktop client due to it being phased out in/not receiving security updates come Q3. We will want to use the Windows App but it appears these two versions have very limited compatibility due to LTSC. Though there are Microsoft Forms showing compatibility there is clearly limitations. Using a repository to install required dependencies is not a realistic solution to do for 600 devices. What is a viable workaround? All help is greatly appreciated.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments
Answer accepted by question author
  1. VPHAN 25,000 Reputation points Independent Advisor
    2026-02-02T17:53:13.87+00:00

    Hello Brandon Heinz,

    First let me just explain in details this: the core technical conflict lies in the minimum operating system requirements for the new Windows App. This application relies on modern Windows APIs, specific versions of the .NET runtime, and UI frameworks (like WinUI and WebView2) that are not natively present or fully supported in the Windows 10 Enterprise LTSC 2019 (Build 1809) kernel. While Microsoft supports LTSC for critical infrastructure, modern "Store-class" apps like the Windows App generally require a minimum of Windows 10 version 1903 or often 2004 to function correctly without massive, instability-inducing dependency injection. Attempting to sideload the Windows App and its requisite dependencies onto 1809 across 600 devices is indeed unrealistic and technically unsound, as you would essentially be trying to patch a legacy OS kernel to support a modern application framework it was never designed for.

    For your Windows 11 IoT Enterprise LTSC 24H2 devices, the situation is different. This OS version is built on a modern kernel that is fully compatible with the Windows App. However, because IoT Enterprise LTSC typically omits the Microsoft Store, you cannot rely on the standard consumer installation method. The viable workflow here is to obtain the offline installation package (MSIX/AppxBundle) for the Windows App. You can deploy this using Microsoft Endpoint Configuration Manager (MECM) or Microsoft Intune by utilizing the Add-AppxProvisionedPackage PowerShell cmdlet or the DISM tool during your imaging process. This ensures the app is installed at the system level for all users without requiring the Microsoft Store app to be present.

    Regarding the Windows 10 LTSC 1809 fleet, your most viable workaround, and the industry standard best practice for AVD on legacy systems, is to utilize the Remote Desktop client for Windows (MSI variant), specifically the msrdc.exe client, rather than the new "Windows App." It is crucial to distinguish between the deprecation of the generic "Remote Desktop" Store app and the continued support of the enterprise-grade MSRDC MSI client. While Microsoft is unifying branding under "Windows App," the standalone MSI installer for the Remote Desktop client remains the supported method for connecting to Azure Virtual Desktop on systems that cannot support the new unified application. This client supports the necessary AVD features (Teams optimization, multimedia redirection) and can be deployed silently via MSI switches (/quiet, /norestart) to your 1809 devices. This does not rely on the modern app frameworks that 1809 lacks and will provide the stability required until you can upgrade those endpoints to a newer LTSC release like 2021 or the upcoming 2024.

    I hope you've found something useful here. Should you have more questions, feel free to leave a message. If my answer helps you get more insight into the issue, it's appreciated to accept the answer. Have a nice day!

    VP

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 25,000 Reputation points Independent Advisor
    2026-02-24T18:55:31.3266667+00:00

    Hello Brandon Heinz,

    Has your issue been solved? If it has, please accept the answer so that it could be spread further to those in need too. If not, is there anything I can help you with? Please let me know. :)

    VP

    0 comments
  2. VPHAN 25,000 Reputation points Independent Advisor
    2026-02-10T13:05:32.0466667+00:00

    Hello again Brandon Heinz,

    Just following up. I've just found out your description lacks one critical detail regarding the end-user workflow: Do these devices require Teams Media Optimization or advanced peripheral redirection (e.g., scanners, serial devices)? This distinction is vital because it determines if the HTML5 Web Client is a viable stopgap or if a native client is strictly mandatory. Without this information, we cannot definitively rule out the browser-based solution which would save you from an immediate mass-OS migration.

    Regarding the technical resolution, the hard block on Windows 10 Enterprise LTSC 2019 (Build 1809) is absolute. The unified Windows App utilizes modern Windows UI Library (WinUI 3) and MSIX Core dependencies that effectively require Windows 10 Build 1903 or later; no registry modification or dependency injection can stabilize this on the 1809 kernel. If upgrading these 600 devices to Windows 10 IoT Enterprise LTSC 2021 (which supports the Windows App) is not feasible before March 2026, your only supported workaround is the Azure Virtual Desktop Web Client. Accessing AVD via an HTML5-capable browser (Edge/Chrome) removes the dependency on the installed msrdc.exe client entirely and is fully supported on LTSC 1809. This allows you to bypass the End of Support deadline while you plan the OS migration, provided your users can tolerate the lack of Teams offloading and limited peripheral support inherent to the web client.

    For the Windows 11 IoT Enterprise LTSC 24H2 workgroup devices, you do not need Intune to achieve automation. The "gray area" you perceive is resolved by leveraging a read-only Network Share and the DISM tool. Download the Windows App .msixbundle and its two required dependencies (Microsoft.UI.Xaml.2.8.x and Microsoft.VCLibs.140.00.UWPDesktop) and host them on a local server. You can then deploy a simple startup script (via Group Policy Object for the local machine or a Scheduled Task running as SYSTEM) that executes DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:"\\Server\Share\Package.msixbundle" /SkipLicense. This command provisions the app into the OS image itself, ensuring that any local user who logs in receives the app automatically, replicating the behavior of a machine-wide MSI installer without requiring a store connection or cloud management.

    VP

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.