Azure Virtual Desktop RemoteApp fails in Windows App with 0x80080005 for one user, but Web Client RemoteApp works

MN 50 Reputation points
2026-01-18T23:49:11.9466667+00:00

Summary

We have an Azure Virtual Desktop (AVD) deployment with Hybrid AD joined session hosts. One specific user is unable to launch RemoteApps from the Windows App client and consistently receives an authentication error (Code: 0x80080005). However, the same user can successfully launch the same RemoteApps using the AVD Web Client, and the same user can also RDP directly to the session host successfully.

Other users are able to launch the same RemoteApps successfully using Windows App.

This appears to be a Windows App client → RemoteApp launch/authentication issue specific to one user (not a host issue, not an app issue).


Environment

Azure Virtual Desktop (AVD)

Session hosts: Hybrid AD joined

Client: Windows App

Windows App version: 2.0.916.0

  Client version: **1.2.6873.0**

  
  RemoteApp deployment (published applications via AVD)
```---
## Issue Description

When launching a published RemoteApp via **Windows App**, the user receives:

**RemoteApp** **An authentication error has occurred (Code: 0x80080005).** Remote computer: `sessionhost-02.domain.com`

Expanded details show:

Error code: `0x0`

Extended error code: `0x0`

Example Activity ID: `c0ed86b9-e1b7-4f69-9e8c-5da8b6330000`

Example Timestamp (UTC): `2026-01-18T18:44:00.767Z`

This happens repeatedly with new Activity IDs each attempt.

---
## What Works / What Doesn’t

### ✅ Works

**AVD Web Client** User can sign in and successfully launch the same RemoteApps via web client:

`https://client.wvd.microsoft.com/arm/webclient`

**Direct RDP to the session host** From another PC, same user can RDP directly to the session host using mstsc successfully:

`sessionhost-02.domain.com`

**Other users using Windows App** Other users can launch the same RemoteApps normally via Windows App.

---
### ❌ Doesn’t Work

**Windows App → RemoteApp launch for this one user (`userA`)** Consistent failure with:

`An authentication error has occurred (Code: 0x80080005).`

Additionally, at times Windows App shows:

> “Your connection failed. Failed to initiate the connection. Please try restarting the application.”

Sometimes that error does not show Launch count / Timestamp / Activity ID, only a Session ID.

---
## Steps Already Taken / Troubleshooting Performed

### Client-side

Tested on **two separate PCs in two separate physical locations**

Removed/re-added the AVD workspace

Cleared credentials / forced sign-in again

Fully reinstalled Windows App

   Windows App version confirmed: `2.0.916.0`
   
```yaml
  Client version confirmed: `1.2.6873.0`
```### User assignment verification

Confirmed the user is assigned to the correct AVD Application Group (RemoteApp group)

Confirmed other users in the same group can launch RemoteApps via Windows App

### Host-side logs

Looked for `4625` failed logons in Security logs on the session host at the time of failure

   No relevant `4625` event was found for the RemoteApp launch failure attempts.
   
### Host pool RDP Properties

Current host pool RDP properties:


```php
use multimon:i:1;
devicestoredirect:s:*;
autoreconnection enabled:i:1;
bandwidthautodetect:i:1;
networkautodetect:i:1;
audiocapturemode:i:1;
redirected video capture encoding quality:i:2;
audiomode:i:0;
camerastoredirect:s:*;
redirectprinters:i:1;
enablecredsspsupport:i:1;
videoplaybackmode:i:1;
redirectclipboard:i:1;
redirectlocation:i:1;
singlemoninwindowedmode:i:0;
encode redirected video capture:i:1;
smart sizing:i:1;
dynamic resolution:i:1;
compression:i:1;
drivestoredirect:s:;
redirectcomports:i:1;
redirectsmartcards:i:1;
redirectwebauthn:i:1;
usbdevicestoredirect:s:;
alternate shell:s:c\:\\windows\\explore.exe


Current Ask / What We Need Help With

  1. Why would Windows App RemoteApp fail with 0x80080005 for only one user, while:
    • Web Client RemoteApp works
    • Direct RDP to the session host works
    • Other users can launch RemoteApps via Windows App normally
  2. What specific logs/diagnostics should we use to identify the failure reason tied to the Activity ID if the session host is not logging a failed logon?
  3. Is there a known issue with Windows App (2.0.916.0 / client 1.2.6873.0) causing RemoteApp authentication failures in AVD for certain users?
  4. Is there a supported way to force the Windows App RemoteApp launch to prompt for credentials (username/password) similarly to the web client behavior?
Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.


Answer accepted by question author
Anonymous
2026-01-22T05:20:03.8933333+00:00

Hi MN,

Thank you for sharing the error details.

Based on your description, we can confirm that this behavior is due to a known Microsoft issue impacting the Windows App for Azure Virtual Desktop.

Issue Summary:

  • You are unable to connect to a pooled AVD host using the Windows App
  • Connection works successfully via Web Access
  • Error observed: Authentication error (Code: 0x80080005)

Root cause:

This issue was introduced by the January 2026 Windows security update (KB5074109), which included a security hardening change in the Credential UI (CredUI) broker. This change unintentionally caused authentication failures when connecting via the Windows App in certain environments. The Web client is not affected, which explains why it works successfully.

Temporary Workaround:

Uninstalling KB5074109 is a supported and safe temporary workaround. The issue affects only the client device and does not impact the AVD session host or pooled environment.

Please note that this workaround should be considered temporary, as Microsoft does not recommend remaining unpatched long term.

Permanent Resolution:

Microsoft has released an Out-of-Band (OOB) update – KB5077744 (released on January 17, 2026), which permanently resolves this issue.

Upcoming Automatic Fix:

Microsoft has confirmed that this fix will also be included in the February 2026 regular Windows Update, which will be automatically delivered via Windows Update.

Recommended Next Steps:

  1. If possible, install KB5077744 from the Microsoft Update Catalog
  2. If not, temporarily uninstall KB5074109
  3. Install latest windows update January 24, 2026—KB5078127

We hope this helps. Please let us know if the issue persists after following the above recommendations.

Was this answer helpful?


1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-01-18T23:49:29.02+00:00

    The error code 0x80080005 typically indicates a permissions issue or a problem with the authentication process when using the Windows App to connect to Azure Virtual Desktop (AVD). Given that this issue is specific to one user while others can connect successfully, here are some potential reasons and troubleshooting steps:

    1. User-Specific Configuration: Since the user can access RemoteApps via the AVD Web Client and can RDP directly to the session host, the issue may lie in the configuration specific to the Windows App for that user. Check if there are any specific group policies or settings applied to this user that might affect their ability to authenticate through the Windows App.
    2. Credential Manager: Ensure that the user's credentials are correctly stored in the Windows Credential Manager. Sometimes, incorrect or outdated credentials can cause authentication failures. Clearing these credentials and re-entering them may help.
    3. Conditional Access Policies: Review any Conditional Access policies that might be affecting this user's access to the Windows App. If the user is subject to different policies than others, it could lead to authentication issues.
    4. Logs and Diagnostics: To identify the failure reason tied to the Activity ID, you can check the following logs:
      • Event Viewer on the session host for any relevant logs under Applications and Services Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS.
      • Azure AD Sign-in logs for any errors related to this user's sign-in attempts.
    5. Known Issues: As of the version mentioned (Windows App 2.0.916.0), there have been no widespread reports of issues causing authentication failures specifically for certain users. However, it is always good to check for any updates or patches that may address known bugs.
    6. Forcing Credential Prompt: Unfortunately, there is no direct supported method to force the Windows App to prompt for credentials in the same way as the web client. However, clearing cached credentials and reinstalling the app may prompt the user to enter their credentials again.

    In summary, focus on user-specific configurations, credential management, and any Conditional Access policies that might be affecting this user's ability to authenticate through the Windows App. Checking the appropriate logs will also provide more insights into the failure.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.