UltraVNC

After installing the W10 21H2 January update, I haven't had disconnects. Super annoying in Dec / Jan. Who knows whether there was something in the update or it just needed a reboot cycle to clean up something.

1.3.6 on Windows 10 21H2 x64. A certain software / action is causing "Server closed connection" "-Manual closed" "-Network disconn". You can re-connect and continue. It seems to be reproducible. Server is running in service mode. Poll Full Screen, System HookDLL and Low Accuracy (100% CPU) are ...

I had this problem with 1.3.6 x64 install on Windows 10 21H2. Tried uninstalling / re-installing several different times with a couple of different combinations of check boxes.

Desktop icons show up.

Start menu folder never does.

Yes Wi-Fi. I have a really good dual band router with 4x4 MIMO. Client uses 802.11ac with >700 Mbps link speed. Server uses 802.11n with 52-144 Mbps link speed. Worked fine for years until 1.2.2.4.

Yes the server has 2 monitors on the GeForce GTX 650 Ti

Rudi De Vos wrote:Looks like not all videocards implement the ddengine method the same way.

NVidia GeForce GTX 650 Ti with 419.35 (~March 2019) WHQL driver, BTW

Can you do a little test, i just can't repeat it. To avoid install/uninstall, Download the 1.224 as zip and extract in a temp folder. Run winvnc from this folder, make sure the 1223 version isn't running, this create a default ultravnc.ini. in this folder, this are the same settings we use on ...

Are you using the ddengine ( tray should indicate it while connected) What's your cpu ? Re-installed 1.2.2.4 to answer your question. Yes if I hover over the tray icon when connected, the tooltip has a "ddengine" suffix. Core i5-3350P 3.1 GHz. 8 GB RAM. It's old, but no slouch. Runs 1.2.2.3 fine ...

Updated from 1.2.2.2 to 1.2.2.4 on Windows 10 x64. Everything was so slow. It was hard to use.

I right click a lot. It is either not registering, not rendering, or really slow to render. Unusable.

I went back to 1.2.2.2 and everything is normal. Even with the 1.2.2.4 viewer.

I got bored with stability and usability of 1.2.1.7 and 1.2.2.0 alpha. Current setup as follows: viewer 1.2.2.0 x86 March 15 build on Win 7x64. 'auto' (Hextile encoding?) server 1.2.1.6 x64 clean install on Win 10 (fall creators update) in service mode with 'recommended' settings for Win10 Both ...

console app to test ddengine cap of the video card https://www.uvnc.eu/download/1220/test_ddengine.zip This is what it gave: Initialize MonitorManager Initialize OneDesktop Initialize OneDesktop stopOneDesktop StartOneDesktop UpdateDesktop stopOneDesktop StartOneDesktop UpdateDesktop BLIT apdaper 0 ...

Can you check 1° extract zip in a temp folder 1° stop uvnc_service service ( cmd: net stop uvnc_service) 3° run winvnc from temp folder 4* start vncviewer from temp folder and connect to localhost This give some kind of endless mirror effect, but exclude network and most security between server/vi ...

Rudi De Vos wrote:It's always possible that you have a OS >win8 but a video driver that doesn't support wdm 1.2.
What's the video card and driver version you have on the server ?

NVIDIA GeForce GTX 650 Ti. dxdiag reports WDDM 2.3. WinHQL certified driver. Win 10 x64 Fall Creators Update (build 1709).

Server: Windows 10 x64. UVNC running as service. 802.11n wireless, 2.4 GHZ access point Client: Windows 7 x64. 802.11ac wireless, 5 GHZ access point Dual band access point. Server and client on the same LAN Recommended viewer settings for LAN (Hextile, CopyRect encoding, etc.). On the server, after ...

Update: I switched to the 1.2.1.5 viewer on Windows 7 x64. Server is still 1.2.1.7 on Windows 10 running as a service.

Within a minute or two after minimizing, the 1.2.1.5 viewer also crashes.

Running UltraVNC Viewer 1.2.1.7 on Windows 7 x64. After minimizing the viewer window, the viewer crashes after a few minutes. every time. Server is Windows 10 x64 running the same version. Viewer options are Hextile Full Colors Auto size / 90% scaling Forget which version I was running before ...

Using UVNC viewer 1.2.1.0 x64 on Windows 7 x64. The client and server have the same resolution. I don't want to run the viewer full screen, so I have it set for auto size/pos by 90%. When I connect to the server the first time, I get a window that shows the entire screen of the server. So I can see ...