![]() Having traces of both cases, working and not working could help you understand what was happening even without really knowing why. Probably a netsh trace you could invoke to help supplement both. Otherwise ProcMon might help supplement your remote machine's event log. We can use WPRUI to help diagnose Boot problems but I don't know if the same scenario trace sufficiently covers this one. is the crash occurring during the normal timeout event or did the crash cause the black screen and then a subsequent timeout is normal? Supposedly ![]() ![]() Regarding your crash symptom, I think somehow you need to establish the timing of the events. I am presented with a login prompt and I don't want to use a mouse or keyboard. And then sometimes, by using Narrator, the previously unseen screen elements mysteriously appear.īTW I have a related case that I am still trying to solve: my OSK was left open on another non-Touch monitor. Would be possible to delay the login prompt timeout by using Narrator to explore the otherwise unseen and unusable controls. doesn't this simulate the same symptoms a user would have if they couldn't login (no input possible, for example)? In fact, in that scenario, black screen instead of login prompt, it Sounds like a video driver (or RFX) problem. It stays for some seconds and then the remote desktop connection gets disconnected without any error message. Those guys have found no solution so far, possible to get help here? 3 Answers Sorted by: 3 Make a config girectory so that chrome-remote-desktop instalation is recognized in the chrome/chromium/firefox addon: mkdir /.config/chrome-remote-desktop /opt/google/chrome-remote-desktop/chrome-remote-desktop -stop Change specific cofigs to prevents session clobbering: (Remote will use the same sesion as host. It seems to be the very same problem as described here: Antivirus is Windows defender and I don't think that firewall/antivirus is causing the issue because after rebooting it works for some time and then stops for no reason It is not network or client related, tried to connect with different client machines to the Windows 10 target machine from different networks with different users, including adminstrator accountĤ. It is reproducable, happens since late DecemberĢ. Will work fine for some time and than get stuck again. When rebooting the Windows 10 target machine remote desktop login ![]() Local logins and logins via Google Remote Desktop are still possible. On the Windows 10 target machine eventlog shows that winlogon crashed, this happens every time the user tries to connect. It stays for some seconds and then the remote desktop connection gets disconnected User can connect via remote desktop for some time and at some point they only get a black screen when connecting. I have a Windows 10 machine with remote desktop enabled. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |