I can't access via remote desktop to my PC

FerranBurriaGuiteras-1567 1 Reputation point
2023-11-21T07:46:29.6566667+00:00

Hello,

A while ago I had problems with Windows 10 and accessing my PC via remote desktop. Then I updated to Windows 11 and nothing has changed.

The fact is that I try to access using my Microsoft account (the same one I use to log in to Windows) and it doesn't work, it denies my connection all the time.

In the event viewer I saw this:

An account failed to log in.
Subject:
Security ID: NULL SID
Account name:		-
Account Domain:-
Login ID: 0x0
Login type: 3
Account with login error:
Security ID: NULL SID
Account name: (my outlook.com account appears here)
Account Domain:-
Error information:
Error reason: Unknown username or incorrect password
Status: 0xC000006D
Substate: 0xC000006A
Process information:
Caller process ID: 0x0
Caller process name:-
Network information:
Workstation Name:-
Source network address: ***.***.***.***
Source port: 0
Detailed authentication information:
Login process: NtLmSsp
Authentication package: NTLM
Services transited:-
Package name (NTLM only):-
Key length: 0

Does it make sense that I can login into PC but not via remote desktop?

Anything I can check? If you need more information, please, let me know.

Thank you.

Best.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Anonymous
    2023-11-22T08:22:46.99+00:00

    Hello,

    I've come across several methods that could prove helpful for you:

    1. You may resolve the issue by creating a local account first. Logged in with a local account and later linked to Microsoft account
    2. The absence of password synchronization between the machine and Microsoft account can be addressed by logging in once with the complete password on the remote computer.
    3. Try signing in with the full password of the Microsoft account at least once instead of using the PIN.

    Reference link: Unable to access a remote computer through Remote Desktop Connection when using a Microsoft Account

    Regards,

    Karlie

    0 comments No comments

  2. FerranBurriaGuiteras-1567 1 Reputation point
    2023-11-22T10:07:48.78+00:00

    Hello Karlie,

    I tried the first option, and now I can login to remote computer but...the connection crashed after login window appears.

    In event viewer I have to new events:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
      <EventID>1000</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>100</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2023-11-22T10:04:03.5348238Z" /> 
      <EventRecordID>70391</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="28040" ThreadID="24264" /> 
      <Channel>Application</Channel> 
      <Computer>Raynor</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="AppName">LogonUI.exe</Data> 
      <Data Name="AppVersion">10.0.22621.1</Data> 
      <Data Name="AppTimeStamp">cf0f816d</Data> 
      <Data Name="ModuleName">Windows.UI.Xaml.dll</Data> 
      <Data Name="ModuleVersion">10.0.22621.2715</Data> 
      <Data Name="ModuleTimeStamp">981d05ca</Data> 
      <Data Name="ExceptionCode">c000027b</Data> 
      <Data Name="FaultingOffset">00000000008727e0</Data> 
      <Data Name="ProcessId">0x513c</Data> 
      <Data Name="ProcessCreationTime">0x1da1d2b3872032d</Data> 
      <Data Name="AppPath">C:\WINDOWS\system32\LogonUI.exe</Data> 
      <Data Name="ModulePath">C:\Windows\System32\Windows.UI.Xaml.dll</Data> 
      <Data Name="IntegratorReportId">9034350f-a3b7-4ec6-a0de-7ddde4100329</Data> 
      <Data Name="PackageFullName" /> 
      <Data Name="PackageRelativeAppId" /> 
      </EventData>
      </Event>
    
    

    And:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" /> 
      <EventID>1001</EventID> 
      <Version>0</Version> 
      <Level>4</Level> 
      <Task>0</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2023-11-22T10:04:05.7203371Z" /> 
      <EventRecordID>70392</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="28040" ThreadID="24264" /> 
      <Channel>Application</Channel> 
      <Computer>Raynor</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="Bucket">2009955750693566406</Data> 
      <Data Name="BucketType">4</Data> 
      <Data Name="EventName">APPCRASH</Data> 
      <Data Name="Response">No disponible</Data> 
      <Data Name="CabId">0</Data> 
      <Data Name="P1">LogonUI.exe</Data> 
      <Data Name="P2">10.0.22621.1</Data> 
      <Data Name="P3">cf0f816d</Data> 
      <Data Name="P4">combase.dll</Data> 
      <Data Name="P5">10.0.22621.2506</Data> 
      <Data Name="P6">b4ec9250</Data> 
      <Data Name="P7">8001010e</Data> 
      <Data Name="P8">000000000008fa43</Data> 
      <Data Name="P9" /> 
      <Data Name="P10" /> 
      <Data Name="AttachedFiles">\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8e04a669-9767-4424-938c-46318e741645.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eac27dcd-f7af-4710-a260-e7d30fc0ae49.tmp.WERInternalMetadata.xml WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20231119_1_EC_0_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e32a101e-fbad-46a9-af01-24c7438c7f2f.tmp.etl WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e8a3ac97-fe07-4ece-80c8-0126cf8b81cf.tmp.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2af443ec-da54-4602-9a3c-90dd00b749f6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f76efb77-8e7e-4c85-92d4-aa1b20ebf617.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.69fc3f8c-6822-4559-a691-033443296a98.tmp.xml</Data> 
      <Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LogonUI.exe_e7fcc1c28fd58ab23f6d11be0e42229dc7d230_18349c6c_9a294a6b-dd66-45c1-b2d6-387f944e7883</Data> 
      <Data Name="AnalysisSymbol" /> 
      <Data Name="Rechecking">0</Data> 
      <Data Name="ReportId">9034350f-a3b7-4ec6-a0de-7ddde4100329</Data> 
      <Data Name="ReportStatus">268435456</Data> 
      <Data Name="HashedBucket">5e3448b78a851a966be4cc1b2657f7c6</Data> 
      <Data Name="CabGuid">0</Data> 
      </EventData>
      </Event>
    

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.