Remote Desktop Connection closed immediately after connection established.

Hi, I hope you're doing good today.

Try this and see if that helps.

https://www.kapilarya.com/remote-desktop-connec...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Regards.

Hello WenpengZhang,

Some cases regarding this issue were about missing .dll file.

In this case perform a system file check:

- Press Windows Key + X to open Win + X menu. Now select Command Prompt (Admin) from the list. If this option isn’t available, you can also use PowerShell (Admin).

- When Command Prompt opens, enter sfc /scannow.

- SFC scan will now start. This process can take up to 20 minutes so don’t interrupt it.

- If SFC scan doesn’t solve the issue, or if you can’t run SFC, you might have to use DISM scan. To do that, just start Command Prompt as administrator and run DISM /Online /Cleanup-Image /RestoreHealth command. Keep in mind that DISM scan can take more than 20 minutes, so don’t interrupt it.

- Once the DISM scan is finished, check if the problem still persists. If it does, repeat the SFC scan again.

Let me know how it works

Hi Pedro,

Thank you for the solutions, I have checked the services list and even turned off the firewall, but issue is still there. 

Also, there is no any pop-up window says "Remote Desktop Connection has stopped working" in my situation.

Hi Mark,

Thank you, it is scanning now. I will post update here if it works.

Ok. Will see how it goes

Hi Mark,

The scan is done, but the issue has been fix. BTW, I can access to Windows server 2012 or higher version without any problem, but only have the issue when connecting to Windows server 2008.

The following is the scan result:

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

And the following is a part of the CBS.log

2018-10-29 17:25:33, Info                  CSI    000055e3 [SR] Verify complete
2018-10-29 17:25:33, Info                  CSI    000055e4 [SR] Repairing 1 components
2018-10-29 17:25:33, Info                  CSI    000055e5 [SR] Beginning Verify and Repair transaction
2018-10-29 17:25:33, Info                  CSI    000055e6 Hashes for file member [l:12]'OneDrive.lnk' do not match.
 Expected: {l:32 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
 Actual: {l:32 b:134f6ae149d8f4617c0def2f4414b4ee7905f8c7914b90436b3e4a35a0e3ca3c}.
2018-10-29 17:25:33, Info                  CSI    000055e7 [SR] Cannot repair member file [l:12]'OneDrive.lnk' of Microsoft-Windows-OneDrive-Setup, version 10.0.17134.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-10-29 17:25:33, Info                  CSI    000055e8@2018/10/30:00:25:33.897 Primitive installers committed for repair
2018-10-29 17:25:34, Info                  CSI    000055e9 Hashes for file member [l:12]'OneDrive.lnk' do not match.
 Expected: {l:32 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
 Actual: {l:32 b:134f6ae149d8f4617c0def2f4414b4ee7905f8c7914b90436b3e4a35a0e3ca3c}.
2018-10-29 17:25:34, Info                  CSI    000055ea [SR] Cannot repair member file [l:12]'OneDrive.lnk' of Microsoft-Windows-OneDrive-Setup, version 10.0.17134.1, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-10-29 17:25:34, Info                  CSI    000055eb [SR] This component was referenced by [l:116]'Microsoft-Windows-OneDrive-Setup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.17134.1.f647690e04ff7e43581b577deaab5f78'
2018-10-29 17:25:34, Info                  CSI    000055ec Hashes for file member [l:12]'OneDrive.lnk' do not match.
 Expected: {l:32 ml:4096 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
 Actual: {l:32 b:134f6ae149d8f4617c0def2f4414b4ee7905f8c7914b90436b3e4a35a0e3ca3c}.
2018-10-29 17:25:34, Info                  CSI    000055ed Hashes for file member [l:12]'OneDrive.lnk' do not match.
 Expected: {l:32 ml:4096 b:9905f2e7a5d33c75361570345fa4441c69ee318f39111cbc9dd9da49dbdf4561}.
 Actual: {l:32 b:134f6ae149d8f4617c0def2f4414b4ee7905f8c7914b90436b3e4a35a0e3ca3c}.
2018-10-29 17:25:34, Info                  CSI    000055ee [SR] Could not reproject corrupted file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk; source file in store is also corrupted
2018-10-29 17:25:34, Info                  CSI    000055ef CSIPERF - FilePI Queue 191ms
2018-10-29 17:25:34, Info                  CSI    000055f0@2018/10/30:00:25:34.296 Primitive installers committed for repair
2018-10-29 17:25:34, Info                  CSI    000055f1 [SR] Repair complete
2018-10-29 17:25:34, Info                  CSI    000055f2 [SR] Committing transaction
2018-10-29 17:25:34, Info                  CSI    000055f3 Creating NT transaction (seq 1)
2018-10-29 17:25:34, Info                  CSI    000055f4 Created NT transaction (seq 1) result 0x00000000, handle @0x5e0
2018-10-29 17:25:34, Info                  CSI    000055f5@2018/10/30:00:25:34.314 Beginning NT transaction commit...
2018-10-29 17:25:34, Info                  CSI    000055f6@2018/10/30:00:25:34.320 CSI perf trace:
CSIPERF:TXCOMMIT;12855
2018-10-29 17:25:34, Info                  CSI    000055f7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
2018-10-29 17:27:35, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2018-10-29 17:27:35, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-10-29 17:27:35, Info                  CBS    Execution Engine Finalize
2018-10-29 17:27:35, Info                  CBS    Execution Engine Finalize
2018-10-29 17:27:35, Info                  CBS    Ending the TiWorker main loop.
2018-10-29 17:27:35, Info                  CBS    Starting TiWorker finalization.
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-10-29 17:27:35, Info                  CBS    CBS Engine already deativated
2018-10-29 17:27:35, Info                  CBS    CBS Engine already deativated
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: WcpUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: DrupUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: DpxUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: SrUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2018-10-29 17:27:35, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-10-29 17:27:35, Info                  CBS    Ending TiWorker finalization.
2018-10-29 17:27:35, Info                  CBS    Ending the TrustedInstaller main loop.
2018-10-29 17:27:35, Info                  CBS    Starting TrustedInstaller finalization.
2018-10-29 17:27:35, Info                  CBS    Ending TrustedInstaller finalization.

If system files are corrupted than you can create a Windows 10 installation Disc and perform a repair on the computer.

Create Windows 10 installation media: https://www.microsoft.com/en-us/software-downlo...

Windows 10 Manual Upgrade & Installation guide: https://answers.microsoft.com/en-us/windows/for...

Steps for repairing:

- Insert the installation DVD or USB and boot Windows 10 from it.
- In the ‘Windows setup’ page select the ‘language to install’,‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’.
- Click on ‘Repair your computer’ and select ‘Troubleshoot’.
- Click on ‘Advanced options’ and select‘Startup Repair’ and select the operating system.

Steps for checking your disk:

- Insert the installation DVD or USB and boot Windows 10 from it.
- In the ‘Windows setup’ page select the ‘language to install’,‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’.
- Click on ‘Repair your computer’ and select ‘Troubleshoot’.
- Click on ‘Advanced options’ and click on command prompt.
- Run the following command from the command prompt and press enter.
chkdsk /f /r X:( drive letter)
- Press Y when you are prompted to check the disk the next time that the system restarts.
- Restart the computer.

Important: When you run the check disk, there are chances of losing data so you can take a backup before running check disk.

Let me know if you have more questions