Windows App compatibility and access limitations on Thin Clients (Windows 10 IoT / NComputing firmware) after Remote Desktop app end of support

Parth Patel 0 Reputation points

I need guidance on accessing remote sessions from Thin Client devices after the Remote Desktop app end of support (27 Mar 2026).

Environment:

  • End-user devices: Thin Clients
  • OS / firmware types:
    • Windows 10 IoT Enterprise
      • Thin Clients running custom NComputing firmware
      • Backend: Windows Server with RDP / RDS (full desktop or RemoteApps)

Issue:

  • Migration to the Windows App is recommended, but:
    • Windows App cannot be installed or is unsupported on: 
       - Windows 10 IoT–based thin clients

 - NComputing firmware–based thin clients

 - Devices have OS/firmware limitations, restricted admin access, and no Store/app support

 - This blocks user access and risks service disruption.

Assistance Required:

  1. Is Windows App is officially supported on:
    • Windows 10 IoT Enterprise
      • NComputing or firmware‑based thin clients
  2. Microsoft‑supported alternative access options for thin clients where Windows App cannot be installed
  3. Best‑practice RDS architecture for thin client scenarios post Remote Desktop app EoS
  4. Security/compliance guidance on temporary continued use of existing RDP clients, if requiredWe need Microsoft guidance on accessing remote sessions from Thin Client devices after the Remote Desktop app end of support (27 Mar 2026). Environment:
    • End-user devices: Thin Clients
    • OS / firmware types:
    • Windows 10 IoT Enterprise
    • Thin Clients running custom NComputing firmware
    • Backend: Windows Server with RDP / RDS (full desktop or RemoteApps)
    Issue:
    • Migration to the Windows App is recommended, but:
    • Windows App cannot be installed or is unsupported on:
      • Windows 10 IoT–based thin clients
      • NComputing firmware–based thin clients
    • Devices have OS/firmware limitations, restricted admin access, and no Store/app support
    • This blocks user access and risks service disruption.
    Assistance Required:
    1. Confirm whether Windows App is officially supported on:
      • Windows 10 IoT Enterprise
      • NComputing or firmware‑based thin clients
    2. Microsoft‑supported alternative access options for thin clients where Windows App cannot be installed
    3. Best‑practice RDS architecture for thin client scenarios post Remote Desktop app EoS
    4. Security/compliance guidance on temporary continued use of existing RDP clients, if required
0 comments No comments
Sign in to comment

1 answer

  1. Hemalatha 14,525 Reputation points • Microsoft External Staff • Moderator

    Thank you for reaching out. I understand you are preparing for the March 27, 2026 end of support for the classic Remote Desktop client and evaluating supported options for your Windows 10 IoT and NComputing-based thin client environment.

    Based on the current Microsoft guidance, please find the details below.

    Windows App Support on Thin Clients:

    • The new Windows App is officially supported on Windows 10/11 Pro and Enterprise editions.
    • Windows 10 IoT Enterprise is not currently listed as a formally supported platform. In some cases, the offline MSIX package may work if the device firmware and administrative policies allow sideloading, but this scenario is not officially validated or guaranteed by Microsoft.
    • Thin clients running custom NComputing firmware typically do not support Microsoft Store applications or the MSIX framework. Due to these firmware limitations and restricted administrative controls, the Windows App generally cannot be installed on such devices.

    Microsoft-Supported Alternatives:

    For environments where the Windows App cannot be deployed, Microsoft-supported alternatives include:

    • Using the HTML5-based web client for Azure Virtual Desktop or Remote Desktop Web Access. This allows users to access RemoteApps or full desktop sessions directly through a supported web browser without requiring a locally installed client.
    • Continuing to use the legacy Remote Desktop client until March 27, 2026. Please note that after this date the client may continue functioning, but it will no longer receive security updates or support.
    • Evaluating vendor-supported RDP solutions provided by thin client manufacturers such as NComputing, while ensuring compatibility and ongoing security maintenance with the vendor.

    Recommended Architecture and Best Practices:

    For thin client deployments, Microsoft generally recommends:

    • Publishing services through RD Gateway and RD Web Access to provide secure HTTPS-based access.
    • Implementing high availability for RD Connection Broker and separating infrastructure roles such as Gateway, Web Access, Broker, and Session Hosts.
    • Using RemoteApps where possible instead of full desktop sessions to reduce resource utilization and improve user experience.
    • Applying security controls such as MFA, Conditional Access policies, and Group Policy hardening for Session Hosts and user access.

    Security and Compliance Considerations:

    If the legacy Remote Desktop client must continue to be used temporarily after end of support, Microsoft recommends minimizing risk by:

    • Restricting access through RD Gateway or VPN-only connectivity
    • Enforcing MFA and Conditional Access policies
    • Limiting connectivity to approved Session Hosts only
    • Maintaining a documented migration and risk mitigation plan with a defined transition timelineThank you for reaching out. I understand you are preparing for the March 27, 2026 end of support for the classic Remote Desktop client and evaluating supported options for your Windows 10 IoT and NComputing-based thin client environment.

    References

    Troubleshooting Installing and Updating the Client (RD app → Windows App transition) https://learn.microsoft.com/windows-app/overview

    Remote Desktop client – supported configuration https://learn.microsoft.com/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients

    Connect to Azure Virtual Desktop with Thin Clients (HTML5 web client approach) https://learn.microsoft.com/azure/virtual-desktop/thin-clients

    About Remote Desktop Services (best-practice architecture) https://learn.microsoft.com/windows/win32/termserv/about-terminal-services

    Known issues and limitations of Windows App https://learn.microsoft.com/windows-app/troubleshoot-known-issues-limitations

    1. Hemalatha 14,525 Reputation points • Microsoft External Staff • Moderator

      Hello Parth Patel

      Just checking if above information was helpful! Please let me know if you have any queries in comments.

    2. Hemalatha 14,525 Reputation points • Microsoft External Staff • Moderator

      Hello Parth Patel

      If above provided information was helpful! Could you please accept the answer and upvote it. Thanks

    3. Parth Patel 0 Reputation points

      @Hemalatha

      [UPDATE — Architecture Clarified]

      Following the helpful responses above, I want to share updated context about our actual environment, as it changes the nature of the problem.

      Our actual setup (clarified):

      • Backend: Windows Server 2022 running RDS (Remote Desktop Services) — users get a full RDP desktop session on this server
      • Thin clients: Physical devices running Windows 10 IoT Enterprise or NComputing firmware. When powered on, they automatically connect to the server RDP session using the user's credentials. Users interact entirely within that server desktop — they have no admin access and cannot see the C: drive on the thin client device itself
      • Windows App installation: We have successfully installed Windows App (MicrosoftCorporationII.Windows365 v2.0.964.0) on the Windows Server 2022 machine using the offline MSIX package and PowerShell (Add-AppxPackage). It runs correctly when launched from an admin session on the server

      The real problem — now clearer:

      The thin client devices themselves are not where Windows App needs to run. The users' working environment IS the RDP session on the server. So the question is really:

      How do we make Windows App available and launchable to RDP users within their Windows Server 2022 desktop session?

      We've hit two issues on the server side:

      1. App only installed for Admin user: Add-AppxPackage installs per-user. RDP users logging in with their own accounts cannot see or launch Windows App. We are now testing Add-AppxProvisionedPackage to provision it system-wide so it registers automatically for every user at sign-in.
      2. App visibility in RDP sessions: Even after provisioning, we need to confirm whether Windows App (an MSIX/UWP app) launches correctly within an RDP session on Windows Server 2022, or whether there are additional RDS/UWP session compatibility considerations.

      Remaining questions for Microsoft:

      1. Is Windows App (MSIX) on Windows Server 2022 RDS supported for multi-user RDP sessions — i.e., can each RDP user independently launch and authenticate into Windows App within their own session?
      2. Are there any known issues with MSIX/UWP app activation inside RDP sessions on Server 2022 (e.g., UWP activation blocked, Start menu not reflecting provisioned apps per-user)?
      3. What is the recommended deployment method for Windows App in an RDS multi-user environment — Add-AppxProvisionedPackage, an MSI/MSIX transform, or another approach?[UPDATE — Architecture Clarified] Following the helpful responses above, I want to share updated context about our actual environment, as it changes the nature of the problem. Our actual setup (clarified):
        • Backend: Windows Server 2022 running RDS (Remote Desktop Services) — users get a full RDP desktop session on this server
        • Thin clients: Physical devices running Windows 10 IoT Enterprise or NComputing firmware. When powered on, they automatically connect to the server RDP session using the user's credentials. Users interact entirely within that server desktop — they have no admin access and cannot see the C: drive on the thin client device itself
        • Windows App installation: We have successfully installed Windows App (MicrosoftCorporationII.Windows365 v2.0.964.0) on the Windows Server 2022 machine using the offline MSIX package and PowerShell (Add-AppxPackage). It runs correctly when launched from an admin session on the server
        The real problem — now clearer: The thin client devices themselves are not where Windows App needs to run. The users' working environment IS the RDP session on the server. So the question is really:

        How do we make Windows App available and launchable to RDP users within their Windows Server 2022 desktop session?

        We've hit two issues on the server side:
        1. App only installed for Admin user: Add-AppxPackage installs per-user. RDP users logging in with their own accounts cannot see or launch Windows App. We are now testing Add-AppxProvisionedPackage to provision it system-wide so it registers automatically for every user at sign-in.
        2. App visibility in RDP sessions: Even after provisioning, we need to confirm whether Windows App (an MSIX/UWP app) launches correctly within an RDP session on Windows Server 2022, or whether there are additional RDS/UWP session compatibility considerations.
        Remaining questions for Microsoft:
        1. Is Windows App (MSIX) on Windows Server 2022 RDS supported for multi-user RDP sessions — i.e., can each RDP user independently launch and authenticate into Windows App within their own session?
        2. Are there any known issues with MSIX/UWP app activation inside RDP sessions on Server 2022 (e.g., UWP activation blocked, Start menu not reflecting provisioned apps per-user)?
        3. What is the recommended deployment method for Windows App in an RDS multi-user environment — Add-AppxProvisionedPackage, an MSI/MSIX transform, or another approach?
    Sign in to comment
Sign in to answer

Your answer