T
TSalamon
Hi,
I recently upgraded a Lenovo P53 running Win10 1809 to Win10 1909. The Lenovo P53 is typically accessed via Remote Desktop (RDP) from an HP Probook 640 G1 running Win10 1809 and located at home. The HP accesses the Lenovo P53 over our company's VPN.
The Lenovo P53 hosts a FlexLM license manager and needs to be available 24/7 within the corporate network, so there isn't an option to take this machine home.
Prior to upgrading the Lenovo P53 to Win10 1909 there were no issues with running Remote Desktop using the VPN. However, after the upgrade to Win10 1909, I would receive the following error when trying to log onto the Lenovo P53 if the machine was restarted.
The workaround for this was to physically go into work and log directly onto the Lenovo P53. Once this was done the RDP session would typically work fine.
In an effort to resolve the issue, my IT department recommended upgrading the drivers and firmware on the Lenovo P53 and setting a registry timeout value to a longer time (30000 milliseconds) per the following Microsoft article
I went ahead and completed the driver/firmware update and registry modification, but it seems to have made the problem worse, as, in addition to not being able to log on after a restart, there are times when I get logged out of the RDP session and am unable to reconnect, observing the same error in the image above.
I've looked at the event viewer logs, and the one common element is that I receive Critical Event IDs 10110 and 10111 (see images below) whenever the RDP connection doesn't work, with Event ID 10111 referencing a Microsoft Remote Display Adapter being offline due to a crash.
The machine also has the following Display Adapters
Would anyone have any idea as to why these errors are now occurring after the Win10 1909 upgrade on the Lenovo P53?
And what might be potential fixes to allow RDP to work without these errors, both on logon after restart as well as on reconnection?
I would appreciate anyone's help on this, as it is becoming extremely difficult to work due to the unpredictability of RDP.
Thanks.
Todd
Continue reading...
I recently upgraded a Lenovo P53 running Win10 1809 to Win10 1909. The Lenovo P53 is typically accessed via Remote Desktop (RDP) from an HP Probook 640 G1 running Win10 1809 and located at home. The HP accesses the Lenovo P53 over our company's VPN.
The Lenovo P53 hosts a FlexLM license manager and needs to be available 24/7 within the corporate network, so there isn't an option to take this machine home.
Prior to upgrading the Lenovo P53 to Win10 1909 there were no issues with running Remote Desktop using the VPN. However, after the upgrade to Win10 1909, I would receive the following error when trying to log onto the Lenovo P53 if the machine was restarted.
The workaround for this was to physically go into work and log directly onto the Lenovo P53. Once this was done the RDP session would typically work fine.
In an effort to resolve the issue, my IT department recommended upgrading the drivers and firmware on the Lenovo P53 and setting a registry timeout value to a longer time (30000 milliseconds) per the following Microsoft article
A service does not start, and events 7000 and 7011 are logged in Windows Server - Windows Server
Describes a problem in which a service times out before it starts. Explains how to work around this problem by increasing the value of the ServicesPipeTimeout registry entry.
docs.microsoft.com
I went ahead and completed the driver/firmware update and registry modification, but it seems to have made the problem worse, as, in addition to not being able to log on after a restart, there are times when I get logged out of the RDP session and am unable to reconnect, observing the same error in the image above.
I've looked at the event viewer logs, and the one common element is that I receive Critical Event IDs 10110 and 10111 (see images below) whenever the RDP connection doesn't work, with Event ID 10111 referencing a Microsoft Remote Display Adapter being offline due to a crash.
The machine also has the following Display Adapters
Would anyone have any idea as to why these errors are now occurring after the Win10 1909 upgrade on the Lenovo P53?
And what might be potential fixes to allow RDP to work without these errors, both on logon after restart as well as on reconnection?
I would appreciate anyone's help on this, as it is becoming extremely difficult to work due to the unpredictability of RDP.
Thanks.
Todd
Continue reading...