Share via

Windows app

Rakesh Patil 0 Reputation points
2026-01-21T12:07:20.65+00:00

When im trying to connect pooled AVD using microsoft app its not connect but same if im doing using webaccess its works GEttimg bellow error [Window Title] Remote Desktop [Content] An authentication error has occurred (Code: 0x80080005). Remote computer: kgsvmavddev-11.corp.kgsolutions.com [^] Hide details [OK] [Expanded Information] Error code: 0x0 Extended error code: 0x0 Timestamp (UTC): 2026-01-20T07:00:06.107Z Activity ID: 393e0c04-e312-4e7f-996f-cb62fa6a0000 Press Ctrl+C to copy.

Azure Virtual Desktop
Azure Virtual Desktop

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


1 answer

Sort by: Most helpful
  1. Hemalatha 14,440 Reputation points Microsoft External Staff Moderator
    2026-01-22T05:20:43.6233333+00:00

    Hello @Rakesh Patil

    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?


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.