tech@waterbrook.org's community posts

Thanks.

So for what it is worth, when this issue occurred, one of the things I did do was to wipe and reload Windows 10 fr om scratch. Updates ran that brought it up to 2004. So, something in the 2004 patch, along with the particular integrated display card is wh ere it all goes south.

What will be interesting is that I do have another identical laptop (latitude E5540) currently on Windows 7. I will be upgrading that as well to Windows 10, and will see if the same behaviour is exibited.

Thanks again...

Thanks Polina.

I went ahead and did an update on another Windows 10 platform to the 2004 patch. I did not have the issues as mentioned above.

For reference of the workstation in question, it was a:
Dell Latitude E5540, 12 GB, 256 GB SSD
Windows 10 Pro w/patch 2004
- Intel HD 4400 graphics card

Thanks,

James

So a few things I tried.

1) Ran the viewer from three different computers. Two @ Windows 7 (6.12.2.0 & 6.10.10.0 respectively), One @ Windows server 2016 (6.10.10.0)
Same results seen from all three computer viewers. The Start menu icons are small. If I connect to other machines from these same viewers mentioned above running Windows 10 w/1909 (not upgraded to 2004 patch), start menu is fine (not shrunk).

2) Added path exception for the HOST (it is only running MS Defender at the moment). Same for the viewers on the three machines mentioned above.

3) All video drivers are up to date/latest.

I have not yet upgraded the other two Windows 10 w/1909 machines to the 2004 patch. Sort of concerned of loosing functionality with RU when I do that (The icons are so small, it's almost impossible to navigate).

Thanks,

James

Hey Polina,

So, to answer to some of the statements, un-checking Legacy capture mode still gives me the issues, so it will need to remain at this time.

Capture Alpha Blending windows did not resolve the display of the start menu. All it did is change the mouse pointer to a dot on the remote system after the Beta upgrade.

Upgraded to the Beta and tried all again. Unfortunately, no change in behavior. I will note, however, that Symantec Antivirus did not like the new version of Beta Viewer. Was unsure of the program, asked if it should be quarantined (Covid issues maybe?) :)

Suggestions?

Thanks,

James

Hey Folks,

Reviving this thread. The system in question was wiped and reloaded to Windows 10, patch 2004. Loaded latest HOST client, and like before, blank screen when attempting to remote in (but the Icon view in Viewer displays properly). Just like seen above.

I set the "Use Legacy capture mode" on the Host, and can log in.  I do, however, get another strange anomaly. The "Start" menu is extremely small/tiny. See the following uploaded images.


If I RDP into the remote system, all is normal with the start menu (let me know if you wish for a screenshot of that).

So, not sure why I would have to use Legacy capture mode, and not sure why the menu is squeezed down so small. Prior to 2004 patch, these issues did not occur.

Thoughts/suggestions?
Thanks,

James

Hey Polina,

That indeed worked. Did as you asked. Program asked to restart HOST (service I presume), then attempted to connect and can now see the screen once again.

Let me know if there is something else you would like me to test. Not sure what in the Windows 2004 feature update patch would cause the issue.

Thanks,

James

Hey Conrad,

Indeed I did. It made no difference.

I did attempt to update video drivers (Dell latitude E5540). Dell website showed drivers, but when attempted to install, stated that I already had newer drivers (Maybe from the Windows update).

I also tried the option in the HOST settings "Driver -> Install Video driver", that too did not change anything.

Thanks,

James

Viewer 6.10.10.0
Server 6.10.10.0

Hey Folks,

First off, love the product, has always worked well.

So I upgraded one of the Windows 10 clients to the 2004 major release update from Microsoft. Now when I connect to the workstation, the screen is black/blank however, If I hover over the icon in the Viewer of that same machine, I can see the current image of what "should be" viewable on the connection. Here is the icon:


Here is the shot of the attempted connect:


I've tried changing color format from default of 16 bit, down to 8 bit, and up to 24 bit. No difference.

I was in this remotely earlier in the day, prior to the upgrade, so I was good with it working prior to updating to 2004.
I did not do the update remotely (I was on site at the time).

Any help/thoughts would be great.

Thanks,

James

Thanks,