Windows 11 Pro Remote Desktop black screen

Question

Windows 11 Pro Remote Desktop black screen

Andrew Hansford 0

RDP connections to the machine result in a connection with a black screen that eventually returns error code 0x3:0xf on the local machine.

The remote target shows no indication that a connection is attempted (like locking the attached display).

All found recommendation have yielded no change in behavior.

When a connection is made the "Windows Remote Display Adapator" is never seen on the remote machine. Attempting to install this Microsoft Device on Windows 11 displays the error:

"The device is not working properly because Windows cannot load the drivers required for this device (Code 31)"

Is there anywhere to look (like a log) that would indicate why windows cannot load a driver provided by Microsoft?

2 answers

Your answer

Answer 1

Domic Vo 17,825 Independent Advisor

Hello Andrew Hansford,

The black screen with RDP error 0x3:0xf combined with the “Windows Remote Display Adapter” failing to load with Code 31 points to a driver initialization failure in the Remote Desktop stack. In Windows 11, the Remote Display Adapter is a virtual device that gets enumerated when an RDP session is established. If it cannot load, the session will fail before the remote system even registers the connection, which explains why the target machine shows no lock screen activity.

To answer your direct question: yes, you can look at logs to determine why the driver fails. The primary source is the System log in Event Viewer (eventvwr.msc). Navigate to Windows Logs > System and filter for Source = Kernel-PnP and Source = RemoteDesktopServices-RdpCoreTS. Kernel-PnP will log detailed driver load failures, including the exact error code and whether the INF file or catalog signature was rejected. RdpCoreTS will log session initialization errors that correspond to the 0x3:0xf failure.

Additionally, check the DriverFrameworks-UserMode log under Applications and Services Logs > Microsoft > Windows > DriverFrameworks-UserMode > Operational. This log records UMDF driver load attempts and failures, including the Remote Display Adapter. If Code 31 is being thrown because of a dependency or signature issue, you will see it here.

For deeper analysis, you can enable Analytic and Debug logs for Remote Desktop. In Event Viewer, right‑click Applications and Services Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS > Analytic, select Enable Log, then reproduce the connection attempt. This will capture low‑level RDP stack events.

If you want to trace the driver load sequence, you can also use Procmon from Sysinternals with a filter on Process Name = svchost.exe and Operation = Load Image or RegOpenKey for the Remote Display Adapter driver. This will show you exactly which registry keys and files are being accessed. The driver is registered under:

HKLM\SYSTEM\CurrentControlSet\Services\RdpVideoMiniport

and its binaries are located in %SystemRoot%\System32\drivers\rdpvideominiport.sys. If the file is missing, corrupted, or mismatched with the OS build, Code 31 will occur.

In short, the logs you should check are: System (Kernel-PnP, RdpCoreTS), DriverFrameworks-UserMode Operational, and optionally the Analytic logs for RdpCoreTS. These will tell you why Windows cannot load the Microsoft‑provided driver. If the driver binary itself is corrupted or mismatched, the supported fix is to run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system components. If that does not resolve it, an in‑place upgrade repair of Windows 11 is the only way to restore the Remote Display Adapter driver.

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

Domic Vo.

Andrew Hansford 0 Reputation points

2026-02-03T23:10:47.12+00:00

I have already done a in-place upgrade repair. That did fix the error loading the January a security update from Microsoft but did not change the behavior of Remote Desktop. Even if I manually install the Remote Display Adaptor it refuses to load. I also not that the following do not load:

Printer driver ( forbidden by system policy )

Monitor driver ( forbidden by system policy )

Headphone ( forbidden by system policy )

Jack Mic ( forbidden by system policy )

HD Audio driver for Display port monitor ( forbidden by system policy )

Looks like this might be related

These however are corrected simply by updating the driver from within device manager. Meanwhile Microsoft Remote Display Adaptor cannot be installed even manually by hand (From install legacy devices) (Error 31)
Andrew Hansford 0 Reputation points

2026-02-09T20:13:48.19+00:00

The only thing I see in the logs is Kernel-PnP

The driver \Driver\WUDFRd failed to load

Device PCI\VEN_8086&DEV_AD03&SUBSYS_0CFF1028&REV_01\3&11583659&0&20
Status: 0xC0000365
Domic Vo 17,825 Reputation points Independent Advisor

2026-02-09T20:37:08.82+00:00
Hello Andrew Hansford,

Thank you for sharing the log details. The entry you’re seeing:

Code

The driver \Driver\WUDFRd failed to load Device PCI\VEN_8086&DEV_AD03&SUBSYS_0CFF1028&REV_01\3&11583659&0&20 Status: 0xC0000365

indicates that the Windows User‑Mode Driver Framework (WUDFRd) service could not initialize a device driver for the Intel PCI device (VEN_8086 = Intel, DEV_AD03). The status code 0xC0000365 corresponds to STATUS_DEVICE_HARDWARE_ERROR, which means Windows attempted to start the driver but the hardware reported a failure condition.

This is slightly different from the Remote Display Adapter issue we discussed earlier. In this case, the failure is tied to a physical PCI device (likely an Intel graphics or chipset component) rather than the virtual RDP video miniport. When WUDFRd fails to load for a hardware device, it can cascade into Remote Desktop failing to initialize its virtual adapter, since RDP relies on the graphics stack being healthy.

Next steps you can try:

Open Device Manager and check the device with hardware ID PCI\VEN_8086&DEV_AD03. It should show a yellow exclamation mark if the driver failed.

Right‑click the device > Properties > Driver tab to confirm the driver version and status.

Update the driver from the OEM (Dell, Lenovo, HP, etc.) or directly from Intel’s support site.

If the driver is already current, try uninstalling it from Device Manager and then scanning for hardware changes to force a reload.

Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to ensure system components are intact.

If the hardware error persists even with the latest driver, it may point to a firmware/BIOS dependency or a failing device. In that case, checking for BIOS updates from the system vendor would be the next step.

Domic Vo.
Andrew Hansford 0 Reputation points

2026-02-12T22:53:06.9533333+00:00

The device in the error is an intel platform framework provider. The error looks to be coincidental. The driver is up to date. I did get it to work by: Setting the disks to AHCI mode in the BIOS instead of the Dell Default RAID mode. I have no idea how that is related but after doing that (in preparation for installing Linux) it worked. Something else may have changed or it unjammed something.
I stil get the same warnings about "Redirection of additional supported devices is disabled by policy" but it actually works. Thanks for the help
Domic Vo 17,825 Reputation points Independent Advisor

2026-02-13T02:16:39.6633333+00:00

Thank you for your message that it works. I hope hope you don’t mind leaving an accept answer to support me and the community ❤️

Answer 2

To troubleshoot the black screen issue with Remote Desktop Protocol (RDP) on Windows 11 Pro, particularly with the error code 0x3:0xf, you can consider the following steps:

Check RDP Configuration: Ensure that Remote Desktop is enabled on the target machine and that the firewall settings allow RDP connections. You can verify this by checking the inbound rules in Windows Firewall.
Driver Issues: The error regarding the "Windows Remote Display Adapter" not loading properly (Code 31) indicates a driver issue. You can check the Device Manager for any issues with the display adapter. If the driver is not functioning, try updating it or uninstalling and reinstalling the driver.
Event Viewer Logs: You can check the Event Viewer for any logs related to Remote Desktop connections or driver loading issues. Look under "Windows Logs" -> "System" and "Application" for any relevant error messages that might provide more insight into the problem.
Network Configuration: Ensure that there are no network-related issues preventing the connection. This includes checking if the remote machine is reachable via ping and ensuring that the correct ports are open.
Anti-Virus and Security Software: Sometimes, security software can interfere with RDP connections. Temporarily disable any anti-virus or firewall software to see if it resolves the issue.
Microsoft Support: If the problem persists, consider reaching out to Microsoft Support for further assistance, especially if you are unable to resolve driver issues or find relevant logs.

These steps should help you diagnose and potentially resolve the black screen issue with RDP on your Windows 11 Pro machine.

Share via

Windows 11 Pro Remote Desktop black screen

2 answers

Your answer