Home > Remote Desktop > Remote Desktop Mstsc.exe Error

Remote Desktop Mstsc.exe Error

Contents

The only other thing I would do is rollback from SP3, I have heard other (all-be-it antidotal), stories of people not liking SP3 for various reasons. That was the answer for me!!!! Thanks. Artem Russakovskii Yay! this contact form

Maybe that will work for you? Jun 26, 2014 at 12:23am Interestingly enough, this suggestion helped resolve the error I was experiencing with remote users connecting to a Windows Server 2012 R2 with remote desktop services enabled. local computers have the printers connected with the \\printserver sharing.Run mstsc as admin causes the same issue. :(I can't run mstsc from the winsxs folder... Does bitcoin have the potential to be subject to a hard fork where miners are forced to choose which fork they will accept, like Etherum?

Remote Desktop Connection Has Stopped Working Windows 7 Ntdll Dll

If the square root of two is irrational, why can it be created by dividing two numbers? Chipotle Mark4643 Jun 8, 2016 at 04:53pm Upgrading the print drivers just fixed this on Windows 10 upgrading from 7. PaulM8 In the Windows Application event log I found it was a newly installed HP printer on the network causing my RemoteApp RDP session to crash within seconds of starting.

I love windows, i'ts kept me employed for 20+ years :) Friday, September 13, 2013 4:58:00 AM Mipp said... 1.5 years later I installed my new w8.1 pro and had that Marked as answer by Wilson Jia Thursday, September 10, 2009 3:13 AM Thursday, September 10, 2009 3:13 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion Clearing this cache worked a treat. –justinsteven Jul 11 '11 at 4:05 1 You should get additional + for the "don't ask why" bit :) –Zlatko Mar 28 '13 at Faulting Module Name Ntdll.dll Remote Desktop Open CMD command shell 2.

Thank you 🙂 Mahdi Yousefi none of above solution worked for me, i found my answer when i disable AutoLogin for last user in Windows 10, OR 8, 8.1 remote desktop Mstsc Ntdll.dll Error Recent Topics 0 SATA M.2 PCIe card? The file The permission The fix Note: The file is also present in C:\Windows\SysWOW64 on 64-bit Windows, but didn't need to be renamed on my system for this Any thoughts? © Copyright 2006-2016 Spiceworks Inc.

Browse other questions tagged remote-desktop rdp windows-8.1 or ask your own question. Remote Desktop Connection Has Stopped Working Server 2012 I disable Printers as a shared resource. Thanks for sharing this workaround, Mahdi. It only happens if I log in to the remote computer with a thin client, then a thick client and back to the thin client.

Mstsc Ntdll.dll Error

I changed the owner of the amd_64_microsoft-windows-t..minalservicesclient_ folder to myself from TrustedInstaller. It took me 3 weeks to use the correct search keywords in google to find that easy solution on your site. Remote Desktop Connection Has Stopped Working Windows 7 Ntdll Dll Privacy statement  © 2016 Microsoft. Remote Desktop Stopped Working Windows 7 I wasn't the only with this issue - glad you're working now Fonzie Squaccuara Filter out the sh*t next time you write a troubleshooting article, nobody cares about your feelings and

So there was something on my computer that was causing the Remote Desktop application to quit unceremoniously. weblink Unfortunately, now some of the user's printers are missing (when connected tot he terminal server). Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted Solved the problem by removing an invalid Printer on the client machine. Remote Desktop Has Stopped Working Windows 10

Currently I'm involved in virtually every aspect of maintaining a production network and related system critically responsible for $1m+ of business revenue (to include software/DB architecture and development). Really displeased with all of this. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up navigate here This only happens with RDP connections to Windows 8 / Server 2012.

The resolution I have found has been to revert to an older version of MSTSC as described here: http://it.tmod.pl/Blog/EntryId/115/Remote-Desktop-Connection-crashes.aspx . Remote Desktop Crashes Windows 10 What are the difficulties of landing on an upslope runway Bitwise rotate right of 4-bit value Could IOT Botnets be Stopped by Static IP addressing the Devices? Here is the error message from the event viewer: Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 07/18/2012 Time: 10:07:26 AM User: N/A Computer: (X'D

Also, I've used RDP in the past on Windows 8.1 without problems, it's only on the new HP laptop. –Andrie Schoombee Jul 9 '15 at 15:04 Have you tried

Try to update this DLL. This type of approach may also solve the issue for those looking to use printers or audio as a local resource in the remote environment. Md. Remote Desktop Crashing Windows 10 Only I am running Windows 7 Pro SP1.

http://serverfault.com/questions/5959/alternative-remote-desktop-software. Renaming the file in System32 works like a charm. I have not been able to get RDP to work for 6 months, despite trying the other workaround you cite, plus other suggestions that I have found online. his comment is here In the event log on my laptop I get the following error (Event ID 1000): Faulting application name: mstsc.exe, version: 6.3.9600.17415, time stamp: 0x5450434f Faulting module name: ntdll.dll, version: 6.3.9600.17736, time

Alas, these suggestions made no difference for me so I started digging. Both server and my test subject had version 12.18 installed. Pimiento egberto7453 Jan 15, 2014 at 07:34pm Is there anything new on this?