-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shadow error: Access is denied #267
Comments
No feedback from maintainer? README.md links to http://woshub.com/rds-shadow-how-to-connect-to-a-user-session-in-windows-server-2012-r2/ which claims:
@binarymaster does this apply here? What reason can cause access denied on shadowing? (For example, on Win10 1703 15063.674.) Thanks. |
For me this just looks like a Windows bug, and almost entire Windows NT 10 looks unstable for me (that's why I still use Windows 7). Also take look at this: #247 (comment) |
Well, this actually makes sense, the user must have some privileges to shadow other sessions. |
@binarymaster thanks for linking to #247 (comment). There, discussion reports that upgrading to 1709 solved the problem. Result: RDPwrap basic functionality works again (after update). Yet no progress regarding shadow: we still get "access denied" on Have walked through README.md again, no more hint. What now? Thanks. |
Would like to tell, that shadowing is working for Windows 10 20H2 Version 10.0.19042.804. I had to activate shadowing in gpedit.msc -> Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Connections -> Set rules for remote control ....' For my computer Windows 10 20H2 Version 10.0.19042.804 seems to be very stable (No problems performing hibernation/standy and resume cycles during heavy GPU RTX 3090 Cuda Load , Memory load with multiple running VMWare instances) PS: And huge thanks for providing rdpwrap. |
Closed as solved. If not - reopen it. |
re: shadow access denied see: #1512 (comment) |
First, gotta say thanks for this awesome tool! Saved me from downgrading to win 7.
I followed the readme, and can now remotely login to the PC running Windows 10 (latest update up to 27/06/2017).
However, when trying to shadow the session (
mstsc /shadow:2
) I get a prompt straight up:In the configuration, all is green, so it is not like: #215
It might be similar to #247, because I am on the latest update, but again, all green, and a different error message
I would appreciate any help!
The text was updated successfully, but these errors were encountered: