I had this same exact issue, uninstalling KB5055528 fixed it for my client who uses RDP to connect to his office workstation from home.
RDP stops with error code 0x3 (0x11)
Hello,
I noticed an issue with the RDP connection to my home PC about a week ago. The error code is 0x3 (extended error code is 0x11).
While checking the solution online, I reinstalled the GPU driver, disabled the RDP and re-enabled it, uninstalled the Microsoft Display Adapter, etc.
The issue is still the same.
Related to Microsoft Remove Display Adapter, I see in the eventviewer, it is installed since 2025.04.11. (This is about the same time, when I noticed the problem first time.)
It shows errors as well, related to starting problem:
Device SWD\RemoteDisplayEnum\RdpIdd_IndirectDisplay&SessionId_0003 had a problem starting.
Driver Name: rdpidd.inf
Class Guid: {4d36e968-e325-11ce-bfc1-08002be10318}
Service: WUDFRd
Lower Filters:
Upper Filters: IndirectKmd
Problem: 0x0
Problem Status: 0xC00000E5
Around that time, the KB5055528 got installed as well.
Via Windows App on my phone I receive the following error:
The graphics display components in the remote session failed to start up.
Error Code 0x11
Is this a known issue maybe?
Thank you in advance!
Windows for home | Windows 11 | Display and graphics
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
7 additional answers
Sort by: Most helpful
-
Anonymous
2025-05-15T00:16:28+00:00 There isn't one, because every single subsequent cumulative update will add the breaking change in KB5055528. In fact, that update itself will eventually come back itself unless you use a tool to permanently ignore it. So essentially, you can never update Windows ever again if you are having this error. I suppose a complete reinstall MAY fix it but that is insane.
I work with Microsoft at an Enterprise level, and their senior support don't even know and can't seem to find out what the particular change is that has broken this. They are as clueless as Clifford B there, whose answer, by the way, is word for word what Copilot tells you if you ask it about this error.
Not a single fix available online will fix this particular issue. Once again we are the testers of Microsoft's half baked products
-
Anonymous
2025-04-21T16:51:52+00:00 Hello,
Welcome to the Microsoft Community Forum. Please accept our warmest regards and sincerest hope that all is well despite the situation you find yourself in.
It seems like you're dealing with a complex issue related to Remote Desktop Protocol (RDP) and the Microsoft Remote Display Adapter. The error codes and symptoms you described, including the installation of KB5055528, suggest a potential conflict or driver-related issue. Here's what you can try:
- Rollback KB5055528: Since the problem started around the time this update was installed, you can try uninstalling it. Go to Settings > Update & Security > Windows Update > View Update History > Uninstall Updates. Locate KB5055528 and uninstall it. Restart your PC and check if the issue persists.
- Update or Reinstall Display Drivers: Ensure you have the latest GPU drivers from your manufacturer's website. If you've already reinstalled them, try using a tool like Display Driver Uninstaller (DDU) to completely remove the drivers before reinstalling them.
- Check Group Policy Settings: Some RDP settings might conflict with the Remote Display Adapter. Use
gpedit.mscto access Group Policy Editor and review settings related to hardware acceleration, RemoteFX optimizations, and UDP connections. - Disable Microsoft Remote Display Adapter: If the adapter is causing issues, you can disable it temporarily. Open Device Manager, locate the Microsoft Remote Display Adapter under Display Adapters, right-click, and select Disable Device. Test your RDP connection afterward.
- Registry Fix: If the problem persists, you might need to edit the registry. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WUDFRdand ensure the service is set to start automatically. Be cautious when editing the registry—back up your data first. - System Restore: If none of the above works, consider restoring your system to a point before the issue began. Go to Control Panel > Recovery > Open System Restore and select a restore point.
Hope this helps.
Best Regards,
Clifford B.
Microsoft Community Moderator
-
Anonymous
2025-04-28T16:32:39+00:00 - Rollback KB5055528: Since the problem started around the time this update was installed, you can try uninstalling it. Go to Settings > Update & Security > Windows Update > View Update History > Uninstall Updates. Locate KB5055528 and uninstall it. Restart your PC and check if the issue persists.
This worked for me. I found and removed KB5055528 on the machine I was trying to Remote Desktop into, and it resolved the 0x3 0x11 error. I am now able to RDP into that machine. Thank you for your post!
-
Anonymous
2025-05-22T01:55:05+00:00 I have the same problem. Any solution yet Dear Microsoft? Could somebody help?