Black Screen Remote Desktop Error Code 0x3 Extended Error Code 0x12 Windows 11 Pro

Question

Hello,

I couldn't find anyone else on the Internet having the same error/extended error combination.

The problem generally is solved after a reboot of the remote machine but it comes back after a while with black screen for a couple of minutes and then it exits with:

[Expanded Information]

Error code: 0x3

Extended error code: 0x12

I already tried to deactivate bitmap caching and UDP, lower down resolution, etc.

I'm running the last build of Windows 11 Pro on both machines with all updates installed.

Any clues?

Thanks.

[Client details]

Client version: 10.0.22621.1194 (x64)

Local OS: Windows 10 Pro x64 (10.0, Build 22621)

[Network details]

Transport protocol: UDP

Round-trip time: 3 ms

Available bandwidth: 39.77 Mbps

Frame rate: 0 FPS

[Remote computer details]

Remote session type: Remote desktop

Gateway name: Not in use

Gateway logon method: Not in use

Answer 1

This is literally insane but it worked for me! Thank you for the tip - I've been going crazy about this case. Some time before I could solve this problem unistalling Microsoft Remote Desktop Adapter from Device management but today it stopped to be a solution so your solution helped me and I don't know what should I do now without mstsc.

Answer 2

1. From the Start menu, search for the Settings app and open it.
2. Select Apps, then select Installed apps.
3. Find or search for Remote Desktop Connection, select the three dots to the right-hand side, then select Uninstall.
4. Confirm you want to uninstall the app by selecting Uninstall.
5. Restart your machine if the app prompts you in order to complete the installation.

Answer 3

Did you face of reoccuring of this problem? After I've removed Windows Remote Desktop App problem was solved but then it occured again. The only method for solving for now is installing Remote Desktop App again and uninstall it again - after system reboot there is no error while connecting.

The only event I see in the log when the problem occurs is (I have to mention that there is no any of that dump files at mentioned locations):

• System
  • Provider
    [ Name] Windows Error Reporting
    [ Guid] {0ead09bd-2157-539a-8d6d-c87f95b64d70}
    EventID 1001
    Version 0
    Level 4
    Task 0
    Opcode 0
    Keywords 0x8000000000000000
  • TimeCreated
    [ SystemTime] 2024-03-27T06:43:40.6286965Z
    EventRecordID 96953
    Correlation
  • Execution
    [ ProcessID] 45156
    [ ThreadID] 44700
    Channel Application
    Computer HOST
  • Security
    [ UserID] S-1-5-18
• EventData
  Bucket
  BucketType 0
  EventName LiveKernelEvent
  Response No data
  CabId 0
  P1 193
  P2 81e
  P3 ffffffffc000013f
  P4 2
  P5 0
  P6 10_0_22631
  P7 0_0
  P8 256_1
  P9
  P10
  AttachedFiles \?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20240327-0943.dmp \?\C:\WINDOWS\SystemTemp\WER-172837796-0.sysdata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.beb3e7dc-2514-4eeb-82c1-cb5a82649461.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.33b97f1e-2629-4f1e-a3c9-327bcc01e412.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.dbbb507b-a044-4b2d-8499-df8d895bcb03.tmp.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.953e856b-5250-4cc1-9f28-dd54e8576074.tmp.xml
  StorePath \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_bbd3bc55ff4a2d56fea4fecee08a7f83ff276285_00000000_cab_aefe9d19-a418-45f3-adcb-9581f6dd9c18
  AnalysisSymbol
  Rechecking 0
  ReportId aefe9d19-a418-45f3-adcb-9581f6dd9c18
  ReportStatus 2049
  HashedBucket
  CabGuid 0

Somebody help!

Answer 4

Hello,

I have the same problem.

Do you already have a solution?

Computer-host: Dell Vostro 3020 - Intel graphics - Win11Pro

Computer-client: Lenovo Thinkpad - Win11Pro

Another client have the same problem

I tried all the solutions but with no results, after a few hours I couldn't connect (black screen).

After restart computer work some time.

Somebody help!

Answer 5

I'm still facing the same and only reboot helps to be able to reconnect.