Got a case of black screen session

[cesare]

Hello

this night we got the update of Windows 10 to "Windows 10 Creators Update", version 1703, (all was done automatically).

We took the opportunity to update TsPlus to version 10.30.5.21

We got after about 2 hours of user working one case of black screen session: the session is alive, we can use explorer into it, but the desktop of it is black and not responsive, see screenshot please.

Don't know if problem is due to Windows 10 or TsPlus update, for sure we never had such case previously.

Do you have an idea why this happaned, any suggestions ? How to investigate more on this case ?

Thanks in advance for any help.

[admin]

Hello,

Could you assign the remote desktop application and connect using a standard RDP client (generated client or native Microsoft) ? If this issue persist please apply the latest update again and reboot.

[cesare]

Thanks for the reply.

The user who got the case of black screen has only assigned the "Microsoft Remote Desktop" (he is assigned only that), see the attached screen shot.

Anyway following your suggestion I have installed also very latest version of today (10.30.5.22) and let's see if the case of black screen will happen again.

If you have other suggestion they will be appreciated.

Thanks again.

[cesare]

Hello

also today a case of black screen session to some users.

Their session is "alive": user can explore disk, folders, open application, etc... but the desktop is black, see the screenshot.

All the other users who is assigned only "Floating Panel" + our application are not having such issue.

It "seems" that users who is assigned only "Microsoft Remote Desktop" are having such issues.

What can we do ?

Need to assign something else to the above user also ?

Thanks in advance for any help.

[John]

Hello,

Sorry for this annoyance.
We did fix it yesterday.
Please download the latest Update Release patch whihc includes this fix.

Kind regards

John

[cesare]

Hello

thanks for the reply.

I have installed latest TsPlus to version 10.30.5.23 and I confirm that the problem seems SOLVED.

Thanks again for the help.