![]() ![]() Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. If the Answer is helpful, please click "Accept Answer" and upvote it. This contact information may change without notice Please Note: Microsoft provides third-party contact information to help you find technical support. How To Fix Black Screen While Using Remote Desktop Connection Note: This article only applies to Macbook Pro 16' 2019 models running the new AMD Navi GPU chipsets. Please recall when our issue first happen, which update patches we installed recently may be cause current issue?Ģ.Can we run below command in command prompt(open as admin) on both local win10 and remote win10 then check if it can find and solve system file issue ?ĭism /online /cleanup-image /restorehealthģ.Do you check if other device(other local win10, Mac, android device) can remote access the destination PC successfully?Ĥ.If we do clean boot on local win10, when we remote access the remote pc, will the same issue happen?ĥ.If the issue persist, please check if below link can help you? If the remote system is tight on RAM, it may be because Spotlight is being a pig.0.Could you please enter winver in command prompt on both local win10 computer and remote win10 then look the os version and os version number ?ġ.Can you enter below powershell command on both local win10 and remote win10 then look which update patches have been installed on your win10 recently? I've had best success clamping down on Spotlight (which, imho, isn't very useful) and restricting it by either marking most of my drives and directories "private". The finger the I would also point is at mdutil, the spotlight indexer, which just gets out of control, especially on a system with a lot of large drives with a lot of small files. But that's a really short term solution (buys another 15-90 seconds, usually). but that doesn't last for long:Īnd then sudo kill XXXX once I know what what procid I'm targeting. I always disable the option to Lock on Session End as this is sometimes also a problem, but I cannot find a pattern that causes the black screen. I switch apps on the remote system (loading things in and out of RAM)įrom practical standpoint, I've found that greping for the the screen sharing daemon and killing it forces the remote machine to respawn a new one that isn't blacked out. There is one remote mac (running latest version of TVhost 11 on OS10.10.5) that repeatedly turns into a black screen which prevents any further access which I can only circumvent by having someone on site to reboot.I've got huge uptime on the remote system (so.I'd second the idea that it may be a RAM issue - I'm noticing that it happens particularly when: While I can work around this glitch (I tend to just SSH in for maintenance), I thought I'd see if anyone out there has any suggestions! Screen sharing sometimes initiated via Remote Desktop, sometimes just clicking on Share Screen in the Finder. Hardware doesn't seem a factor either using a range of Mac Minis and Macbooks. Network connectivity doesn't seem to be a factor this happens both on a fast LAN and across the Internet with 400-500ms latency. Sometimes other areas of the screen will redraw themselves (usually when there is an actual change), but most the screen simply remains black, sometimes even repainting back to full black again. ![]() ![]() Moving the mouse will result in the area immediately under the pointer being redrawn correctly, and dragging a window (in the remote session) off screen then back on will redraw that window. As an ongoing issue (for at least the past three major OS X versions), I find that when trying to remote to another machine using Screen Sharing, the remote screen gets painted completely black. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |