This absolutely sounds like an MS problem, not previously sparkling, conforming hardware.Ĭan -anyone- help me? Is anyone at MS working on this? Is there -any- solution? I firmly believe that it is NOT someone else's fault. ultravnc 1240 X86 setup: UltraVNC 1.2.2.4 distribution for 32-bit operating systems. So, on Windows 7 and prior to 1809, VNC works fine, but postġ809 it doesn't. Many people have said that prior to 1809, VNC worked fine. It appears from my reading that this problem started with 1809 and many users have gotten irritated with MS that it hasn't been fixed. All I get on remote machines to the T420 is a blank screen. Here's the real rub: I upgraded a much more recent Lenovo T420 to Win 10 and I cannot get VNC to work after more endless research., tweaking Aero, and on and on. Both as a server and to view remotely.Ĭlearly, any update requiring a re-boot will fail. However, VNC works FINE on this machine after the upgrade. I did endless research on the Critical Event in the Event viewer (having to do with "ZuneMusic" of all things) to no avail. I have to power-off twice, go to Automatic Diagnose, then "exit to Win 10" and ![]() The upgrade went ok except that it FREEZES -every time- on boot. The first one I moved was an old Lenovo T61p. I am in the process of moving everything from Win 7 to Win 10. VNC works perfectly on the Win 7 machines. ![]() I am a hobbyist and have 9 Windows PC's at home. ![]() VNC is -very- important to me, and this question is really about VNC.
0 Comments
Leave a Reply. |