Skip to content
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

Closed
AmitMY opened this issue Jun 27, 2017 · 7 comments
Closed

Shadow error: Access is denied #267

AmitMY opened this issue Jun 27, 2017 · 7 comments

Comments

@AmitMY
Copy link

AmitMY commented Jun 27, 2017

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:

Shadow Error
Access is denied

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!

@fidergo-stephane-gourichon

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:

Only server administrator can connect to other sessions. These rights can not be delegated to regular  users
RDS Shadow won’t work in the networks based on workgroups

@binarymaster does this apply here? What reason can cause access denied on shadowing? (For example, on Win10 1703 15063.674.)

Thanks.

@binarymaster
Copy link
Member

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)

@binarymaster
Copy link
Member

Only server administrator can connect to other sessions. These rights can not be delegated to regular users

Well, this actually makes sense, the user must have some privileges to shadow other sessions.

@fidergo-stephane-gourichon
Copy link

fidergo-stephane-gourichon commented Nov 27, 2017

@binarymaster thanks for linking to #247 (comment).

There, discussion reports that upgrading to 1709 solved the problem.
So, we upgraded. Now winver says 1709 16299.64 .
termsrv.dll has become 10.0.16299.15 which README.md says is supported (from build 160101.0800). Just in case: everything is in French here, and that didn't seem to cause any issue so far.

Result: RDPwrap basic functionality works again (after update). Yet no progress regarding shadow: we still get "access denied" on mstsc /shadow:2

Have walked through README.md again, no more hint. What now?

Thanks.

@svargh
Copy link

svargh commented Feb 17, 2021

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 ....'
After rebooting, shadowing works.

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.

@sebaxakerhtc
Copy link

Closed as solved. If not - reopen it.

@Beej126
Copy link

Beej126 commented Jun 4, 2023

re: shadow access denied see: #1512 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants