Remote desktop connection caused host to lose a monitor and other settings

Hello
After a successful remote desktop login, on the host I can now no longer detect the 2nd monitor. Screen resolution on remaining monitor is off, it's gone over to use Microsoft Basic Display Adapter even though it was using the correct adapter previously.
Both previously working display adapters now show Code 12 error: "this device cannot find enough free resources that it can use". The system has also become very slow, when I right-click the desktop, it takes up to 30 sec for the menu to appear.
Anyone had a problem like this? I have restarted the computer several times, reverted system to a working state last week, done another successful remote desktop login/logout from my laptop to this computer.
Windows 8.1 Pro
Displays: Dell U2412M
Intel R HD Graphics 4600
Thank you in advance for any help/tips to help solve this problem!

This error message can also appear if the BIOS did not allocate enough resources to the device, I want to know how much RAM do you have on your computer, because the Display Adapter calls for extra RAM to run the monitor.
If you don’t have enough RAM to allocate, the monitor won’t start, that’s why the computer becomes very slow.
Here I suggest a possible solution:
Adjust the amount of memory dedicated to video/graphics. You can change that in BIOS. there might be an option in your PC's BIOS that lets you change the amount of system memory used for video/graphics.
You'll just need to find it in the BIOS, the BIOS options in the Advanced settings,
the option varies depends on the BIOS version
you can set the maximum memory that it can take to a lowest value.
Regards
Wade Liu
TechNet Community Support

Similar Messages

If I instal Lion, will I lose M.Office and other settings?

My iMac is running on Snow Leopard 10.6.8 and I am considering installing the latest OS Lion. However, I have Microsoft Office, iWork and other programs installed in my computer that I didn't want to lose. I also have a configuration for VPN access for the company I work for which would be very complicated to get that configuration installed again.
Does anyone think that by installing Lion I would lose all that?
I appreciate your coments!
Thanks!

Lion might muck with your VPN. Absent details, I can't say for sure. It most likely will have no effect.
A Lion upgrade won't change or cause you to lose any of your software or data. Of course, anything might happen and so you should create a full bootable backup before upgrading, just in case.
You do need to check if any of the software you are using requires Rosetta, which is the PowerPC emulation code used to run older software designed for pre-Intel Macs. If you're using MS Office 2011 and a recent vintage of iWork, both will work fine under Lion. Be sure to update your software before upgrading your OS, and investigate compatibility with Lion so you'll know in advance what will and won't work.

"remote desktop connection has stopped working" When printing from remote desktop connection

I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
-I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
diffrent machines just not the Windows 7 machine.

Hi,
Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections. If you are making Connections using a single
monitor do not use this setting.
So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Meanwhile sharing article with you for more information.
Remote Session Environment
http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
Hope it helps!
Thanks.

Remote Desktop Connection - internal error

My laptop is running Windows 8.1 and since yesterday has starting giving problems when connecting to remote PCs using Remote Desktop Connection.
It asks for the password and then shows 'Configuring remote session' for about 30 seconds and then displays 'An internal error has occurred'. Another PC on the same network is able to connect to the remote PC without problem. I've tried connecting
to four other PCs with this laptop and two work and three don't.
I've tried changing various settings such as bitmap caching and clipboard sharing etc. Nothing makes a difference.
I've also used system restore to reverse recent windows updates and that hasn't helped either.
Any ideas?
What can cause 'An internal error has occurred'? Will it be writing to a log somewhere that I can look at to find further information about the error?
Thanks
Andy

I'm not sure if you meant there could be a problem with the user profile on the laptop or the one on the server I'm trying to connect to?
However, it seems to be the latter. I just created a new user account on the server and can now remote into it from my laptop. If I try the original user account again (Administrator) then I get the internal error message. Other client
PCs can still log-in to the server using the same Administrator account without problem.
Is there something I can do (either to client or server) to clear the fault with the Adminstrator account without wiping that account on the server?

Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS) improves display
and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
remote connections for family, non-commercial use.
Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
T. Webster

Hi,
It depends on the quality of the network connection to run the software smoothly throuth RDP. And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
Regarding more information about RDP, please take a look at the following articles:
Remote Desktop app help
Remote Desktop Connection: frequently asked questions
Best regards
Michael Shao
TechNet Community Support

Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

Hey guys,
I have been searching for and trying fixes for this for 3 days, and I've gotten no where. Thanks in advance for trying to help me out.
Here's the situation:
I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN. This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need. After a fresh
installation, I added the AD and DNS roles and promoted the server to the PDC. Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role). The installation fails, but I can't find any explanation as to why.
I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc. including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker. I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing. I also
cannot find RDMSDeploymentUI.txt log.
I've also tried to deploy this using Powershell using this command:
New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database. However, I can
get the session host and every other component to install using role-based deployment, except the Connection Broker.
I've run an SFC scan, which found no issues. I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
I'm completely at a loss. Has anyone encountered this before? Any suggestions would be greatly appreciated. Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
information at all?
I would greatly appreciate any help anyone could offer. I'm willing to try anything. Thanks for taking the time to read this.
Sincerely,
Dominick

Also Found this:
1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain
controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that
the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update.
Note: There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation
without this KB and see what happens.
For more information, Refer below link...
http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

Close ... before going for a specific Cisco app ... lets find out some details:
Host we need more details:
What is your server environment (Windows Server, or Mac OS X Server, or Linux)?
What security is implemented in your environment - as what is restricted (RDP for all or specifc credentials on all machines? Are you part of local admin group to the server you wish to connect)?
Does your environment Support CISCO IPSec connection? If so use Settings> VPN and IPSec tab to enter VPN details, if not then go with above suggestion. IF your restricted to RSA then either built in VPN settings or 3rd party app for RSA would suffice.
Finally, there are many RDP applications out there I use "Mocha RDP Light" (free minimal ads when launched not when connecting).

Remote Desktop Connection keeps disconnecting

I have BT Hub 3 (recently upgraded to Broadband Unlimited at the end of Jan 2015).
Up until recently I was able to Remote Desktop into my work computer (via VPN tunnel) with no problems at all.
Around March 6th, I began to experience problems with the Remote Desktop Connect (RDP), in that it now makes an initial connection and then disconnects (typically within a few seconds, occasionally after a couple of minutes).
It will then cycle through a number of reconnection attempts, all with the same result, before it finally drops altogether with the message:
'The Remote Desktop Services Session has ended. Connection to the remote computer was lost, possibly to network connectivity problems'.
I have tried restoring both machines back to a date when i know the connection was working - no joy. I've also tried deleting an re-creating now VPN and RDP connections - no joy. I've researched online and tried various other things, but still have the same problem.
I've tried connecting using a laptop (via my wirelss connection) with the same result. My manager has RDP'd in from his home machines and has had no problem at all.
This leads me to consider whether the problem is with the router/BT Hub itself. I've tried the online diagnostic tools with no resolution to this problem.
Has anyone else experienced the same problem?

Oh well, I suppose that after more than 2 months of frustration with this issue, the BTCare Community is unable to help me.
I can be fairly sure that it's not my machine as it's also happened using a laptop, plus I've even reset my PC right back to its original factory state just to sure that nothing had become corrupted.
The network guys where I work have also looked at this and can find nothing at that end to cause this problem.
I've even borrowed another BT Hub and tried it through that - same problem.
So where does the answer lie? VPN issue? I've tried other VPN options - same problem. RDP problem? I've practically exhausted the list of suggested solutions that can be found by trawling the internet.
I even upgraded the broadband cable to replace the cheap old thing that has been working perfectly well in terms of broadband, again, to eliminate this as a possibility. Now I'm stumped.
To me, it looks like the problem lies between my router and the workplace network, i.e. a physical problem among the miles of lines connecting the two. Of course I don't want to shell out for a BT engineer to come out to investigate, so I thought that the combined wisdom of this community may have been able to help.
Sadly not.

Remote Desktop Connection

I'm running bootcamp Windows 8 on a MacBook Pro and a MacMini (on home network).
I have them set up for remote access. At home on the same network, I can remote desktop to the MacMini using the local IP address with no problems.
I then wanted to access it from an external network so I enabled the default 3389 port in my firewall settings and set up this port to my MacMini in my router settings. I reserved the IP address for the MacMini as well.
I was able to successfully connect from an external network at least once but once my external IP address changed, I was no longer able to get it to work after updating the IP address. The computer is on because I can access it using TeamViewer and I use
that to check the current IP address of the MacMini when I'm trying to connect.
To get around the dynamic IP problem, I signed up for a dyndns account and set up a host name. I can use a port check and the host name ***.dyn-o-saur.com resolves to the correct IP address (i.e., the whatismyip.com result on the MacMini).
I have tried changing the port to 8888 in case TeamViewer or some other application was using 3389 but that hasn't fixed the problem either. I've checked the port (using http://www.t1shopper.com/tools/port-scan/) and I get this message:
***.dyn-o-saur.com is responding on port 8888 (ddi-tcp-1).
I have the dynUpdater v5.0.1 installed on both computers and it says the host is inactive (however since the hostname is resolving properly I assume this means the app is not working but it shouldn't be affecting my ability to connect?).
Some help please?

Hi,
Firstly, we need to refer to this article and configure the settings.
Allow Remote Desktop connections from outside your home network
http://windows.microsoft.com/en-us/windows7/allow-remote-desktop-connections-from-outside-your-home-network
From you description, I think you have done this part. However, please keep to use port 3389 and make sure that you can RDP to your Windows 8 via the
Public IP address from Internet.
Then, as you have dynamic public IP address, we need some way to track the changes of your public IP address. Yes, dyndns is one of the methods, you need to make sure that it
can resolve the host name you registered to the correct Public IP address so that you can always RDP you Windows 8 via host name when you outside your home.
If you need assistance about dyndns, please contact their support.
Thanks.
Jeremy Wu
TechNet Community Support

Remote Desktop Connection using the WRT54GC

I replaced a wired router with a Linksys WRT54GC wireless router. Connected to the wired router was a wireless router configured as an access point. I have 2 laptops and I successfully connected to the Internet from both. I was also able to connect to one of the laptops through the wireless access point using Remote Desktop Connection. The only difference between the configuration with the previous router and the Linksys is that the laptop with the Remote Desktop software (the host) was hard wired. Using the Linksys I can successfully access the Internet from both laptops. I can also get to the host computer over the LAN using Remote Desktop Connection. I CANNOT however access the host computer outside the LAN. I configured the router correctly using port forwarding and a 3389 port. I checked "enabled" and entered the IP Address of the host laptop (the one with the Remote Desktop Function). I disabled all security in the router. I have a dynamic address through dyndns.org and have setup the DNS portion of the router accordingly. Can you explain why I can no longer access my home computer remotely using Remote Desktop with the Linksys.

Are you able to access Remote Desktop Connection directly connecting to the modem.

Remote desktop connection blocked by cisco security agent

Hi,
I have a deployment of a Management Center for Cisco Security Agents 6.0.2 and i just noticed that the agent is blocking the remote desktop connection to the hosts, the agent installed on the server shows me the event but i'm not able to see it logged on the Management Center (i can see logged any other events), i'm not sure what rule should i enable in order to allow this connection.
Do you have any ideas???
Thanks in advance...

Hi,
Remote desktop connection uses the highest possible security level encryption method between the source and destination.
In Windows Vista or later versions of Windows, the remote desktop connection uses the SSL (TLS 1.0) Protocol and the encryption is Certificate-based.
TS Gateway can also make the connection more secure, enhance security, see detailed information in this link
http://technet.microsoft.com/en-us/library/cc731264(WS.10).aspx
Don't forget some known offical antii-virus software, they can also protect the connetion from network attack.
Yolanda Zhu
TechNet Community Support

Remote desktop connection problem windows 8

Hi everybody,
I hope you can help us. We run a software package that uses a remote desktop connection. When the program is minimised for more than a couple of minutes, the connection disconnects and takes a while to reconnect. We've been in touch with the guys that run
the program and they've said that there's no problem on their end and that it must be on our end. It's happening with all three computers at one location and it's not happening with our two computers in our other location.
I've been in touch with the online support guys in microsoft and they couldn't help. So I'm wondering if any of you can help us (in laymans terms please!).
All our computers run Windows 8.
Thanks in advance.

Hi,
Thank you for your posting in Windows Server Forum.
Yes, you can check with 2 different settings. 1) By Collection properties (Server 2012\R2) and RDP-Tcp connection under Remote Desktop Service Manager (Server 2008 R2). 2) The other setting is related to GPO (Set time
limit for active but idle Remote Desktop Services sessions) as following path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
You can check below link (Configuration 1) for more information.
[Forum FAQ] Restrict number of Active Sessions in RDS 2012 and 2012 R2
http://social.technet.microsoft.com/Forums/en-US/00c2252b-8ec0-489f-8da2-07a434a9b5a2/forum-faq-restrict-number-of-active-sessions-in-rds-2012-and-2012-r2?forum=winserverTS
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Desktop Connection has stopped working

Using Build 10041. Occurs on 2 separate systems I have when trying to use Remote Desktop Connection through a 2012 R2 RDS Gateway. I am able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE
crashing. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
Eventlog has the following:
Log Name:      Application
Source:        Application Error
Date:          3/25/2015 2:50:21 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7
Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315
Exception code: 0xc0000005
Fault offset: 0x000000000046d78c
Faulting process id: 0x2164
Faulting application start time: 0x01d06734abf028a0
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005
Faulting package full name:
Faulting package-relative application ID:
JW

Tried this with no luck. I have the same issue as the OP. It was failing on 10041 and is still failing with an AV on 10049. See below event log entry after registering mstscax.dll and rebooting. Still failing.
Log Name:      Application
Source:        Application Error
Date:          4/11/2015 12:18:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Chuck1
Description:
Faulting application name: mstsc.exe, version: 10.0.10049.0, time stamp: 0x55137bff
Faulting module name: mstscax.dll, version: 10.0.10049.0, time stamp: 0x55137d3f
Exception code: 0xc0000005
Fault offset: 0x000000000046d74c
Faulting process id: 0x1870
Faulting application start time: 0x01d0748c29e55e06
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 83921b7c-e07f-11e4-960f-40f02f7ad3a4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-11T19:18:21.000000000Z" />
    <EventRecordID>73626</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Chuck1</Computer>
    <Security />
</System>
<EventData>
    <Data>mstsc.exe</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137bff</Data>
    <Data>mstscax.dll</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137d3f</Data>
    <Data>c0000005</Data>
    <Data>000000000046d74c</Data>
    <Data>1870</Data>
    <Data>01d0748c29e55e06</Data>
    <Data>C:\WINDOWS\system32\mstsc.exe</Data>
    <Data>C:\WINDOWS\system32\mstscax.dll</Data>
    <Data>83921b7c-e07f-11e4-960f-40f02f7ad3a4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

Remote desktop connection caused host to lose a monitor and other settings

Similar Messages

Maybe you are looking for