Hi, I have been able to solve my issues following the workarounds mentioned in this two different issues:
https://github.com/FreeRDP/FreeRDP/issues/5548 Administrative Templates -> Windows Compnents -> Remote Desktop Services -> Remote Desktop Session Host 1. Use WDDM graphics display driver for Remote Desktop Connections -> Disable 2. Use hardware graphics adapters for all Remote Desktop Services sessions -> Disable https://github.com/FreeRDP/FreeRDP/issues/4449 * Connect to the remote host using Microsoft Remote Desktop * Run "SystemPropertiesRemote.exe" (or manually open "System Properties - Remote") * Disable "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" Thanks for your help, Pablo De: Pablo Uribe Bastero <pablo.ur...@arin-innovation.com> Enviado el: viernes, 12 de febrero de 2021 9:33 Para: user@guacamole.apache.org Asunto: RE: Error FreeRDP docker Hi, Don't apology, it was my fault for not providing enough information. This are my connection details: * Windows 10 Pro 20H2 * Ignore certificate * NLA Security * Spanish Keyboard * Admin Mode * Resize method update 8.1 * Shared unit activated * Disable glyph caching activated * The rest are the default options. I have checked the power saving and screen saber and they are all deactivated, same settings as other machines. It happens with all the Windows 10 Pro machines from a specific customer, the rest f customers machines works perfectly with Windows 10, Windows 7 and Windows Server 2008/2013/2016. It happens when the sesión is already logged in. So, if I logg in, disconnect from the machine (without closing session) and reconnect I only see the black screen. Thanks in advance, Pablo De: Ivanmarcus <ivanmar...@yahoo.com.INVALID<mailto:ivanmar...@yahoo.com.INVALID>> Enviado el: jueves, 11 de febrero de 2021 20:28 Para: user@guacamole.apache.org<mailto:user@guacamole.apache.org> Asunto: Re: Error FreeRDP docker Pablo, My apologies for not being more specific, but other detail such as Windows version, connection configuration and so on would have been useful too. Also, is it just one machine that is a problem and/or do you have others that work ok? That said, if I understand you correctly, you are initially able to connect to a Windows machine via Guacamole, and use the connection normally. If you then try connecting to the same machine some time later it will connect, but won't actually do anything? That does sound at this point more like a problem on the client machine. I have occasionally had issues with power saving and/or screen savers on the client machine and wonder if this could be what you're experiencing? Perhaps you could firstly ensure all power saving and screensavers are turned off and see if that has any effect?
