Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Full Screen Problems
#1
I have windows 10 and ASG remote Desktop 2016, I run dual monitors at 1920x1080

Ever since moving to Windows 10 I started having problems occasionally where the full screen window wont display correctly

For example the window is bigger than my monitor without scroll bars and I cant see the start bar in the remote computer.

If I just close the window and open it again everything seems to work fine. But its quite annoying.

The next time it happens I'll take a screen shot and post it here.
Reply
#2
Here is a example


Attached Files Thumbnail(s)
   
Reply
#3
Could you run "Components check" to see which size is reported for your monitor?
Regards/Gruss
Oliver
Reply
#4
(09-01-2017, 09:33 AM)DevOma Wrote: Could you run "Components check" to see which size is reported for your monitor?

RDP:
The installed RDP client is fully supported.
Installed version: 10.0.10586 (NLA supported)

HTTP/S:
Internet Explorer control was found but compatibility mode is active.
Installed version: 9.11.10586.0

VNC:
The internal VNC component is installed and working correctly.

ICA:
An error occured while trying to get the version of the Citrix-Receiver.

SSH, Telnet:
PuTTY was found and the installed version is the one that is supported.
Installed version: 0.66

VMware:
VMware vSphere Client not installed. Connect to console can't be used within the application.

HyperV:
PowerShell 2.0 or higher is installed. Communication with HyperV is possible.

General:
Local operating system version: Microsoft Windows NT 10.0.10586.0
Program version: 9.0.5385.0
Installation path: C:\Program Files (x86)\ASG-Remote Desktop 2016
Config file (user): C:\Users\jsblumbe\AppData\Roaming\ASG-RemoteDesktop\9.0
Config file (all): C:\ProgramData\ASG-RemoteDesktop\9.0
Settings file: C:\Users\jsblumbe\AppData\Roaming\ASG-RemoteDesktop\9.0

Display Setup:
Total Monitors: 2
All Monitors Same Bounds: Yes
All Monitors Same Working Area: Yes
Overall Monitor Bounds: {X=0,Y=0,Width=3840,Height=1080}
Monitor with Largest Bounds: 1
Monitor with Smallest Bounds: 1
Monitor with Largest Working Area: 1
Monitor with Smallest Working Area: 1
Monitor 1 Details:
  Device Path: \\.\DISPLAY1
  Device Name: Intel® HD Graphics 5500
  Is Primary: Yes
  Resolution: 1920x1080
  Working Area: 1920x1040
  Color Depth: 32 bit
Monitor 2 Details:
  Device Path: \\.\DISPLAY2
  Device Name: Intel® HD Graphics 5500
  Is Primary: No
  Resolution: 1920x1080
  Working Area: 1920x1040
  Color Depth: 32 bit
Graphics Card(s): Intel® HD Graphics 5500; 
DPI: 96
Windows Theme: Aero style
Symmetric Monitor Setup: Yes
Your Monitor Setup: ##
Reply
#5
(09-01-2017, 06:29 PM)I had the problem again, is this the right place to request help?One thing to note, is I had undocked my desktop used it, then plugged it in the next day and the first connection I open had the problem. jakeb1616 Wrote:
(09-01-2017, 09:33 AM)DevOma Wrote: Could you run "Components check" to see which size is reported for your monitor?

RDP:
The installed RDP client is fully supported.
Installed version: 10.0.10586 (NLA supported)

HTTP/S:
Internet Explorer control was found but compatibility mode is active.
Installed version: 9.11.10586.0

VNC:
The internal VNC component is installed and working correctly.

ICA:
An error occured while trying to get the version of the Citrix-Receiver.

SSH, Telnet:
PuTTY was found and the installed version is the one that is supported.
Installed version: 0.66

VMware:
VMware vSphere Client not installed. Connect to console can't be used within the application.

HyperV:
PowerShell 2.0 or higher is installed. Communication with HyperV is possible.

General:
Local operating system version: Microsoft Windows NT 10.0.10586.0
Program version: 9.0.5385.0
Installation path: C:\Program Files (x86)\ASG-Remote Desktop 2016
Config file (user): C:\Users\jsblumbe\AppData\Roaming\ASG-RemoteDesktop\9.0
Config file (all): C:\ProgramData\ASG-RemoteDesktop\9.0
Settings file: C:\Users\jsblumbe\AppData\Roaming\ASG-RemoteDesktop\9.0

Display Setup:
Total Monitors: 2
All Monitors Same Bounds: Yes
All Monitors Same Working Area: Yes
Overall Monitor Bounds: {X=0,Y=0,Width=3840,Height=1080}
Monitor with Largest Bounds: 1
Monitor with Smallest Bounds: 1
Monitor with Largest Working Area: 1
Monitor with Smallest Working Area: 1
Monitor 1 Details:
  Device Path: \\.\DISPLAY1
  Device Name: Intel® HD Graphics 5500
  Is Primary: Yes
  Resolution: 1920x1080
  Working Area: 1920x1040
  Color Depth: 32 bit
Monitor 2 Details:
  Device Path: \\.\DISPLAY2
  Device Name: Intel® HD Graphics 5500
  Is Primary: No
  Resolution: 1920x1080
  Working Area: 1920x1040
  Color Depth: 32 bit
Graphics Card(s): Intel® HD Graphics 5500; 
DPI: 96
Windows Theme: Aero style
Symmetric Monitor Setup: Yes
Your Monitor Setup: ##


Attached Files Thumbnail(s)
   
Reply
#6
Yes it is the right place for requesting support...

So the problem occurs only after undock and dock again your notebook - so there might be a problem with the display driver - the program is asking for the current screen size and try to open the window in that size - if the program do not get the correct size it might result in your issue...

I don't know how we should resolve this... Did you run Component Check right after docking your notebook to see if the screen size is correct?
Regards/Gruss
Oliver
Reply
#7
(16-01-2017, 09:58 AM)DevOma Wrote: Yes it is the right place for requesting support...

So the problem occurs only after undock and dock again your notebook - so there might be a problem with the display driver - the program is asking for the current screen size and try to open the window in that size - if the program do not get the correct size it might result in your issue...

I don't know how we should resolve this... Did you run Component Check right after docking your notebook to see if the screen size is correct?


DevOma, it happened again just after a reboot. It was docked the whole time.

I did run a component check right after the problem occurred and the screen size is exactly the same when it doesnt work. 

What should I do next?
Reply
#8
At the moment I have no idea what we can test and what could cause this issue - I try to think about what we can do/test next but currently I have no idea...
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)