Re: Black Screen after upgrading to Windows 10 on the remote machines

That doesn't bode well for me. The monitors will probably be in sleep 
mode when I try to connect outside of working hours. I'm going to have 
to make sure they shut down their computers but leave the monitors on so 
that the wakeonlan also wakes up the monitors.

On 2019-05-21 9:21 a.m., [email protected] wrote:
> Tried your test.
> On the first try I couldn't connect. Checking, my laptop is set to Sleep
> when the lid closes.
> Changed that setting to "Do Nothing" and I can connect with the lid closed
> (from Win 8.1 to Win 10).
> I saw the first comment in the referenced thread about the Privacy setting.
> Mine was off.
> I turned it on, rebooted (I lose the connection obviously).
> After reboot I can still connect. Privacy setting has no effect. Note the I
> do not use a Microsoft account to login.
>
> Regards,
>
> Terry >
>
> -----Original Message-----
> From: Gary Dale <[email protected]>
> Sent: Monday, May 20, 2019 5:10 PM
> To: [email protected]
> Subject: Re: Black Screen after upgrading to Windows 10 on the remote
> machines
>
> Actually you can. See this thread from Microsoft support (which also blames
> 1803):
> https://answers.microsoft.com/en-us/windows/forum/all/black-screen/113b2f3b-
> 755e-4e93-a254-a20101d6492c
>
>
> On 2019-05-20 4:22 p.m., [email protected] wrote:
>> Can't test your specific config because I only have one Win 10 machine and
>> it's a laptop so I can't turn the monitor off.
>>
>> >From Win10Pro to Win8.1Pro with monitors off. Works fine.
>>
>> My laptop was purchased two years ago with 1803 or maybe earlier. It
>> is now
>> 1809 and winver reports it as such.
>> See attached screen shot. Also has the Enterprise version which is 1607.
>>
>> Windows...can't live with it, can't live without it. :-/
>>
>> Terry >
>>
>> -----Original Message-----
>> From: Gary Dale <[email protected]>
>> Sent: Monday, May 20, 2019 1:58 PM
>> To: [email protected]
>> Subject: Re: Black Screen after upgrading to Windows 10 on the remote
>> machines
>>
>> I tried connecting from a Win 7 VM to Windows 10 with the same result.
>> Connecting to Windows 10 Enterprise server may be different.
>>
>> The problem may also be related specifically to winver 1803 (April 30,
>> 2018 update). I used that ISO for my "upgrade" because the 1809 update
>> didn't fit on a single-layer DVD. It may also be present in the 1809
>> update
>> - I wouldn't know. Both the computers report winver 1803.
>>
>> I'm not sure what the winver has to do with it, but I note that even
>> though
>> both computers are fully updated, they report the winver they were
>> installed
>> from. I also note that problem reports with VNC & Windows
>> 10 seem to start shortly after 1803 was released.
>>
>>
>>
>> On 2019-05-20 2:44 p.m., [email protected] wrote:
>>> No solution for you, but I regularly connect from my Win10Pro 64-bit
>>> system to an Enterprise server (I think that's what it's called. It's
>>> a Win10 based server for a POS system). No problems. I also connect to
>>> systems with the monitors turned off. Also no problem.
>>>
>>> Terry >
>>>
>>> -----Original Message-----
>>> From: Gary Dale <[email protected]>
>>> Sent: Monday, May 20, 2019 11:43 AM
>>> To: [email protected]
>>> Subject: Black Screen after upgrading to Windows 10 on the remote
>>> machines
>>>
>>> I had to "upgrade" a couple of workstations to Windows 10 Pro (from 7
>>> Pro) to handle new hardware. Unfortunately I can't connect to either
>>> of them remotely now. All I see at my end no matter what viewer I use
>>> is a black screen.
>>>
>>> Googling suggests this is a common problem with Windows 10 winver 1803
>>> but I haven't found a solution for TightVNC. They both should be
>>> running
>>> 2.8.11 but I can't confirm this.
>>>
>>>
>>>
>>> ___________________________________________________________
>>> TightVNC mailing list, [email protected]
>>> To change your subscription or to UNSUBSCRIBE, please visit
>>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>>>
>>>
>> ___________________________________________________________
>> TightVNC mailing list, [email protected]
>> To change your subscription or to UNSUBSCRIBE, please visit
>> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>
> ___________________________________________________________
> TightVNC mailing list, [email protected]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>
>


___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list