This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 76%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGF%3C/text%3E%3C/svg%3E)
Hi experts
New deployment, all windows server 2022 Datacenter Edition.
BROKER2022 as the session broker for the entire deployment.
PROFILE2022 as file server for user´s profile shared folder. (Fslogix profile management -had a funny number of hours dealing with outlook search strange results-)
TS012022, TS022022, TS032022 and TS042022 as RDSH-Remote desktop collection servers (only one collection)
REMAPPS012022 and REMAPPS022022 as RDSH-remoteapps collection servers (only one collection)
All RDSH are under same GPOs.
Remote desktop collection session shadowing is working fine as espected.
Remoteapp collection session shadowing shows a black screen, I can only see the mouse. If I publish VNC viewer as a remoteapp then session shadowing works ok, but word, excel, cmd, notepad, server manager, and many more, just shows a black screen.
I have tried:
In event viewer I can only see events reporting the user permission granted for the session sharing and the session sharing start, and zero errors :(
"Snapshot view permission granted
User domain\user (session id: 2) granted permission to user domain\admin"
"Snapshot view session started
User domain\admin on computer BROKER2022 is viewing user domain\USER (session id: 2)"
This is happening in a Vsphere production environment , and in my hyperv homelab, so It´s not hardware/virtualization related.
If I add all RDS farm servers to a non-member in server manager and try to shadow a remoteapp session there, the result is the same.
If I try to shadow a remoteapp this way same result.
"mstsc /v:[IP address or host name of remote connection destination] /prompt /shadow: [session ID] /control"
If anyone could help I would be very grateful.
Thanks in advance (and apologies for my english)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 84%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hello experts,
Has anyone found a solution for this issue?
I'm experiencing the same problem on Windows Server 2022. When shadowing RemoteApp sessions, whether in interactive mode or not, the screen turns black with only the mouse cursor visible and moving.
I remember that this functionality worked well on Windows Server 2012, but now, in a new environment with Windows Server 2022, I have encountered this bug. It appears that many others are facing the same issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 9%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
I found the reason.
I had a similar problem on the terminal server 2022, on 2016 everything is ok.
The solution is to disable the policy (Disabling RemoteFX graphics for RemoteApp)
Use advanced RemoteFX graphics for RemoteApp
After disabling the policy, the user to which they connect needs to completely re-logon in terminating the session.
Sorry screenshot from the Russian version of the system.
Hey, Nikolay Savin!
Just wanted to drop by and give you a huge thanks for your help. Disabling the "Use advanced RemoteFX graphics for RemoteApp" policy totally fixed the black screen issue when shadowing RemoteApp sessions on Windows Server 2022. Big props for sharing this solution and helping everyone out!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 87%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETT%3C/text%3E%3C/svg%3E)
I'm glad this resolved your issue. However, we've had an ongoing 2+ year support case with Microsoft regarding similar issues with RemoteApp, including black screens and screen artefact issues on Windows Server 2019 and newer. While Microsoft suggested this GPO as a solution, our testing showed it didn't resolve the screen artefact drawer issue. Microsoft confirmed this is a known issue without a resolution. While you can now see the screen, you may still encounter issues, particularly when moving the RemoteApp window.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hi. Thank you for your question and reaching out.
Your firewall may block the connection.
If the Remote Desktop Service uses port 3389 by default, the session host must be reachable from the end-user devices for internal connections or from the Remote Desktop Gateway for external connections.
Verify that no firewall, including Windows Defender Firewall if it is turned on on the session host, is blocking the port that your RDS environment utilizes between the client and the session host.
Another possibility is a certificate issue. Because it employs SSL encryption, Remote Desktop Gateway needs a certificate to be installed. In order to ensure a successful connection with the session hosts, clients must have confidence in the certificate authority that issued the certificate.
Verify that a copy of the root certificate for the certificate authority has been imported into the Trusted Root Certification Authorities store by opening the Certificates Microsoft Management Console (MMC) on the client device.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.
Hi, thank you for your answer.
The problem is not in the user connections, they connect fine to full session and remoteapp collections, the problem is that I cannot shadow their remoteapps sessions, but I can shadow their full sessions. (As they are connecting, there is no issue with the 3389 port or the certificate, that is issued and signed by our domain Certification Authority, and I previously deployed its trustness with a gpo). Look at the picture, at the top there is a remoteapp shadowing session, where you can only see a black screen and the user mouse, and you should see the wordpad in the bottom of the picture, wich is the remoteapp beeing shadowed.
No firewall in the RDSH, clients and servers on the same subnet. No certificate issue, and no communications issue. All RDSH (full session collection and remoteapp collection) are under same gpos. From my point of view, is a bug, but nowadays there is no way to report this issue to microsoft. I had to use the windows 10 feedback center to report the issue... but I think it was a waste of time.
This has always been working in ws2016, and ws2019.
Still dealing with this :(
I´ve found that the microsoft remote desktop app isnt affected by this, and you can shadow remoteapps sessions that are using this app as remote desktop client. Unfortunately I dont know why this wont work with the native remote desktop client and you only see a black screen and the mouse.
https://apps.microsoft.com/store/detail/microsoft-remote-desktop/9WZDNCRFJ3PS?hl=en-us&gl=us
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 73%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECR%3C/text%3E%3C/svg%3E)
We have the same issue with Server 2019 across both our Azure infrastructure and a customer's own hyper-v infrastructure that we do not manage so we know it isn't related to our environment. We find that when the black screen comes up if we click around on it then the windows start to paint, however you don't know what you are clicking on until it is too late which makes it rather dangerous. On 2012 R2, shadowing of a remoteapp worked perfectly. We used this extensively to provide support to our SaaS customers where our app is distributed from Azure servers via RemoteApp.
We haven't gone anywhere near ws2022 due to the remoteapp focus issues detailed here https://www.reddit.com/r/sysadmin/comments/11pzji9/server_2022_remote_app_issues/
Really hoping M$ get their act together with RDS technology in the next version of Windows Server. It isn't economically viable for us to use AVDs for our deployments.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 31%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Configure the shadow connection mode. You can configure whether you need to request the user confirmation to connect and whether view or control is allowed in the shadow session. You can configure shadow connection mode through the GPO option Set rules for remote control of Remote Desktop Services user sessions (Computer Configuration -> Administrative Templates -> Windows components -> Remote Desktop Services -> Remote Session Host -> Connections).
The following 5 modes are available:0 – disable shadow remote control; 1 — full control with user’s permission; 2 — full control without user’s permission; 3 — view session with user’s permission; 4 — view session without user’s permission.
Everything after this simple action all works.
Attach this policy to RDSH. Update all group policies.I also had the same situation as you after that everything worked as it should.