Replies: 2 comments 1 reply
-
|
Heya, I see you closed this again. Did you figure out the issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes...I was hoping to close it out before anyone saw! 😆
I'm sorry for the trouble!
It turns out it was a system property setting, that Windows 11 automatically enables for some reason, that stops remote desktop from happening.
Thank you for reaching out regardless!
Sent from [Proton Mail](https://proton.me/mail/home) for Android.
…-------- Original Message --------
On Monday, 11/03/25 at 12:10 Jeffrey ***@***.***> wrote:
Heya, I see you closed this again. Did you figure out the issue?
—
Reply to this email directly, [view it on GitHub](#369 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BZUT7A2UTI7GDDN3QEEVVCT326LBNAVCNFSM6AAAAACK7W4F7OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBWGE2DQMA).
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I can't seem to use Remote Desktop after using the Debloat tool. I have Network Sharing enabled and all those settings. I also have the Services running as well. Is there a way to get Remote Desktop to work while keeping the benefits of the debloating script?
Beta Was this translation helpful? Give feedback.
All reactions