UltraVNC 1.2.1.0 Beta

[Rudi De Vos]

Beta
**artifact fix windows 8 > when fast capture (hookdll) is used.
**faster reconnect when session switch (user logon -> default desktop, user switching etc.)

OLD: https://uvnc.eu/download/test/winvnc_test1_2110.zip
Latest bins viewtopic.php?t=31554

[Sainsuper]

Is w8hook.dll alway included in uvnc 1.2.0.9 >? It should be prensent in same path of vnc or it is not more necessary?

[Rudi De Vos]

w8hook dll was only used for win8 and win10

From 1.2.0.9, we have 3 different exe.
XP,Vista,WIN7: The win7 version has the w8hook embedded.

The test versions are build with the latest compiler (win7>) and have the w8hook embedded.
Test versions require a min win7 OS.

[Sainsuper]

Thanks rudy, but only w8hook is embedded or schook too? On windows 7 < dll is necessary?

[Rudi De Vos]

only w8, this isn't a real hook, but a collection of functions that are OS depended. using different exe it was easier to embed the functions. Vnchook and schook need to be seperate dll, so they can work as hooks.

No/Yes
embedded w8hook require WDM1.2 video driver!!

win7 -> no wdm1.2 exist
win8/10 -> standard wdm 1.2, but users still can install old win7 video driver without wdm 1.2 support

To have some fallback in case the video driver isn't wdm 1.2>, install vnchook and schook as backup.

capture.
mirror driver :tell the exact places that change on the screen, and video have direct video mem access, doesn't work with directx
video driver is placed in basic mode.

w8Hook :, wdm 1.2 tell the exact places that change on the screen, and video have direct video mem access, capture directx

schook,vnchook: give hints about changed screen positions hooking windows messages, handle hints first and when no hints are given use time to poll fullscreen.

poll: capture screen and scan for changes

[Sainsuper]

Thanks rudi for explanation!

[dborth]

I'm still seeing the same artifacts appearing on Windows 2012 R2.

I also see a second issue, UltraVNC crashes when running in user mode in an RDP session when you disconnect from the session while a VNC client connection is open. When you reconnect to the RDP session, you see a app crash screen and you have to reload UltraVNC.

[Rudi De Vos]

vncviewer sponsered feature added

Extra option
vncviewer.exe -position x y w h
This overwrite all settings and put window at x,y with width and height w,h

Extra option in Gui
Save Position [v]
Save last position (host based).
Each connection save his own last position, based on the connection name.
overwritten by commandline -position
overwrite viewer size/pos gui settings.
exist also as commandline -savepos

OLD: https://uvnc.eu/download/1210/vncviewer_Pos.zip
Latest bins viewtopic.php?t=31554

[ultrVNCFan]

I'm still seeing the same artifacts appearing on Windows 2012 R2.

I also see a second issue, UltraVNC crashes when running in user mode in an RDP session when you disconnect from the session while a VNC client connection is open. When you reconnect to the RDP session, you see a app crash screen and you have to reload UltraVNC.

I am seeing the same.

[Rudi De Vos]

added
ultravnc.ini

Code: Select all

[admin]
alternate_shell=
rdpmode=1

alternate shell, when another shell is used then explorer.exe
sample alternate_shell=mycustomshell.exe
rdpmode (1 add session selection, 0 behave as before)

second try to get rid of the artifacts, please check if this behave better

OLD: https://uvnc.eu/download/1210/winvnc_RDPtest3.zip
Latest bins viewtopic.php?t=31554

[ddbivens]

1.2.0.9 Viewer: I am having an issue where "VNCViewer has stopped working" after being connected for about 5 minutes (time and time again). I can "Close" the viewer as it tries to find a solution on-line and I can reconnect immediately. After another +-5 minutes, it fails again. The times from my AppCrashViewer shows: 12/23/15 9:30:36, 9:35:10, 9:41:32, 9:46:02, 9:50:36. This is from my home PC connected to work PC via a VPN tunnel. However, I have the same problem at work on the same network client/server. I am connecting from a Windows 7/64bit to XP, Win7/32or64bit and the same thing happens. Below is the the AppCrash log:
Version=1
EventType=BEX64
EventTime=130953558363466399
ReportType=2
Consent=1
UploadTime=130953558363766399
ReportIdentifier=85f4ec5f-a984-11e5-b6f6-b870f4ce1e3a
IntegratorReportIdentifier=85f4ec5e-a984-11e5-b6f6-b870f4ce1e3a
Response.BucketId=81661919
Response.BucketTable=27
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=vncviewer.exe
Sig[1].Name=Application Version
Sig[1].Value=1.2.0.9
Sig[2].Name=Application Timestamp
Sig[2].Value=5637d514
Sig[3].Name=Fault Module Name
Sig[3].Value=vncviewer.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=1.2.0.9
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5637d514
Sig[6].Name=Exception Offset
Sig[6].Value=00000000000de709
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=cabc
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=cabc2a6fe04155dfb469fcdb7094b228
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=9d33
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=9d33ee270ec8fd95202301f85fde391e
UI[2]=C:\Program Files\UltraVnc\vncviewer.exe
UI[3]=VNCViewer has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\UltraVnc\vncviewer.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\system32\kernel32.dll
LoadedModule[3]=C:\windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\COMCTL32.dll
LoadedModule[5]=C:\windows\system32\msvcrt.dll
LoadedModule[6]=C:\windows\system32\GDI32.dll
LoadedModule[7]=C:\windows\system32\USER32.dll
LoadedModule[8]=C:\windows\system32\LPK.dll
LoadedModule[9]=C:\windows\system32\USP10.dll
LoadedModule[10]=C:\windows\system32\SHLWAPI.dll
LoadedModule[11]=C:\windows\system32\WINMM.dll
LoadedModule[12]=C:\windows\system32\WS2_32.dll
LoadedModule[13]=C:\windows\system32\RPCRT4.dll
LoadedModule[14]=C:\windows\system32\NSI.dll
LoadedModule[15]=C:\windows\system32\COMDLG32.dll
LoadedModule[16]=C:\windows\system32\SHELL32.dll
LoadedModule[17]=C:\windows\system32\ADVAPI32.dll
LoadedModule[18]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[19]=C:\windows\system32\IMM32.dll
LoadedModule[20]=C:\windows\system32\MSCTF.dll
LoadedModule[21]=C:\Program Files (x86)\AVG\AVG2015\avghooka.dll
LoadedModule[22]=C:\windows\system32\api-ms-win-core-synch-l1-2-0.DLL
LoadedModule[23]=C:\windows\system32\ole32.dll
LoadedModule[24]=C:\windows\system32\d3d9.DLL
LoadedModule[25]=C:\windows\system32\VERSION.dll
LoadedModule[26]=C:\windows\system32\d3d8thk.dll
LoadedModule[27]=C:\windows\system32\dwmapi.dll
LoadedModule[28]=C:\windows\system32\RICHED32.DLL
LoadedModule[29]=C:\windows\system32\RICHED20.dll
LoadedModule[30]=C:\windows\system32\uxtheme.dll
LoadedModule[31]=C:\windows\system32\CRYPTBASE.dll
LoadedModule[32]=C:\windows\system32\LavasoftTcpService64.dll
LoadedModule[33]=C:\windows\system32\MSWSOCK.dll
LoadedModule[34]=C:\windows\system32\IPHLPAPI.DLL
LoadedModule[35]=C:\windows\system32\WINNSI.DLL
LoadedModule[36]=C:\windows\system32\OLEAUT32.dll
LoadedModule[37]=C:\windows\system32\SspiCli.dll
LoadedModule[38]=C:\windows\System32\wshtcpip.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=81661919/nBucketTable=27/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=VNCViewer
AppPath=C:\Program Files\UltraVnc\vncviewer.exe

[ddbivens]

1.2.0.9 Viewer feedback. I should have clarified on my earler post that the viewer disconnects after 5 minutes when I am very active and workng on the remote PC. I have connected to a remote PC and left the viewer alone (working with other programs and ignoring the viewer window) and the connection has stayed connected much longer. The viewer screen goes black after a while and when I try to interact with the remote PC, I get nothing in the viewer window. Clicking the Screen Refresh icon, windows icon, or send C-A-D icon does not cause the viewer to show the remote screen. However, if I look at the remote PC, my keystrokes, mouse moves and clicks are happening on the remote PC. I just can't see the remote screen in the viewer. I found that I can click the "Show Connection Options" icon and click the OK button in the window and the screen will refresh immediately. It remains connected until either 1) I work hard with the remote PC for 5 minutes or so and it disconnects (see my other post) or 2) I ignore the viewer for a while and the screen goes black (time varies).
Please understand how much I believe in UltraVNC. I use it daily and am only providing feedback because IT IS THE BEST! I am only trying to help. Thanks for listening.

[Skyfighter]

@ddbivens
Update your viewer...sounds like a bug which got fixed with v1.2.0.9u1

[ddbivens]

I downloaded the updated VNCViewer from the link above for the vncviewer_Pos.zip file. I am not sure, but this looks like the 32bit viewer. I also noticed that the viewer process seems to stay active in memory after I disconnect from the remote PC by closing the viewer using the 'x'. I can see it in Task Manager, but nowhere else. I used Task Manager to close the "vncviewer.exe *32" process and retried the connect, disconnect several times. Most of the time the viewer stays active in memory. Since this viewer appears to be the 32bit version, based on the process name, is there a download link for the updated 64bit viewer?
Thanks,

[Rudi De Vos]

Thanks for the feedbacks.

vncviewer_Pos.zip = 32 bit
All errors from a 32 exist in 64bit.
During first tests we don't make a 64bit, a 32bit just behave a little slower on a 64bit system compared to a native
64bit, but all bugs are the same.

The vncviewer_Pos.zip has an extra option to save the position of the viewer, so it open at the same spot again.
It was build after the u1, this is the latest build.

[Rudi De Vos]

viewer disconnects after 5 min:
I need to be able to simulate it to fix things.

PC running the vnc server.
*screensaver after 5 minutes ? if yes, does the saver change the resolution.
*Is the server running as service or started as application
*Do you clone the console or a rdp session

Tested on my server 2008r2, connection was open for 2 hours and i was still connected.
Some server/viewer pc options has to trigger something

Thanks
Rudi

[ddbivens]

I downloaded vncviewer_Pos.zip and put it to use. This update has fixed the 5 minute disconnect issue.
However I am still having the same problems as some of the other users have identified, namely the full refreshing of the screen (the screen goes black then it does a full redraw) every so often. It seems to be irregular timing so I am not sure what trigger is causing the redraw.
Also the initial connection to a PC will often show a black screen only. I can try the Show Connection Options / OK, but that does not help. Neither does the Refresh Screen button. Almost always I can disconnect and reconnect and the screen displays immediately.
Pls let me know if I can do any particular testing that might help discover the source of the problem.

[Rudi De Vos]

Please use latest bins
viewtopic.php?t=31554

It could be that some issue's were fixed in the release test bins and installers.

Thanks
Rudi

[ddbivens]

Thank you. I have downloaded the installers and will install and begin testing tomorrow. I will try to provide feedback as soon as I can. A coworker is out so I will be busy and might be a little slower than I would like to be. Thanks again.

[Kirck]

Hello, I have issues when I type the typical CTRL+C or CTRL+V with mayus enabled.

Thanks

[OSXFeatureRequest]

Feedback:

• It was very confusing to have the new "Save Position" on by default for existing saved connections. I spent half-an-hour debugging the cause of the unwanted behaviour.
• I am extremely pleased to see the clipboard problems fixed.

For what kind of server is the mirror driver useful for? It seems to cause more problems than it solves for me.

• No remote cursor option worked consistently with the mirror driver active.
• Remote machine was crashing (BSOD) on login with mirror driver and ultravnc client connected recently.
  • Incompatibility was likely caused by a Microsoft product or update, as I hadn't changed anything in UltraVNC and the problem does not occur without UltraVNC.
  • Upgraded to 1.2.1.0 (and associated mirror driver), problem still occurred.
  • Disabled mirror driver, crashing ceased.

[Rudi De Vos]

mirror driver is usefull for OS's till win7.
We don't have a lot of problems with the mirror driver if the real video driver is ati or nvidia.
There are reports that some drivers conflict with a mirror driver.

But:
A mirror driver mirror gdi and only gdi.
So when the mirror driver activate he put the driver in gdi mode and some applications doesn't like the mode switch.
It works in 99% of the cases and for for 99% of the software.
The mirror driver follow the MS guidelines...
It only works when vnc is runnings as service, driver activation is UAC only from Vista.
Drivers run at kernel level---> any error in memory cause a BSOD

[OSXFeatureRequest]

• Remote machine was crashing (BSOD) on login with mirror driver and ultravnc client connected recently.

I just want to follow up that it was a lack of system resources that was causing this (BSOD) crash, so probably just that tiny extra requirement from the mirror driver + all the software bloat from MS Office overwhelming the computer.

I'm still unclear on the benefit of the mirror driver, it seems to run more accurately without it.

[Rudi De Vos]

A mirror driver
-create a list of rectangles (screen changes)
Instead of scanning and comparing 10mb a frame, we now exact the change rects
-direct video access.
Normal you need to blit (copy video to system memory) to be able todo something with the mem
The mirror driver has direct access to the, you just can copy it.

Depending on system and video card blitting can be sloooow...on thoose systems using the mirror driver makes
a lot faster. Also the respons time to detect a change is a lot faster with the mirror driver.

Natural, the faster you cpu and the better video card you have the difference become smaller.

[OSXFeatureRequest]

I'm having a problem with freezing. When the host performs an action that demands a lot of CPU time (like opening or closing an application), the viewer freezes and does not recover unless minimised&restored or with the Request Screen Refresh command. No amount of waiting will make the viewer recover on its own.

Exactly:

• Viewer stops updating
• Host CPU fan briefly spins up (often, but not always)
• Host still receives input from viewer connection - even after several minutes of the viewer being frozen. If I'm looking at the host monitor, I can still interact with the mouse, for example.

My versions are 1.2.1.0 (downloaded 31 Jan 2016). My previous versions were 1.2.0.5. Both host and viewer are running Windows 7 64-bit and are connected by an ethernet cable. The earlier version did not have this problem.

Changing the following settings does not fix the problem:

• (viewer) Reconnection attempts
• (viewer) Timeout
• (host) mirror driver
• (host) SChook
• (host) multiple connections
• (host) RDPmode