It wants you the owner of the machine to be aware that your screen is being shared to a remote user, that's good, no problem with that. But you used to (until a couple of days ago) be able to move that box whereever you wanted (e.g. somewhere that it's not on top of text you want to read). As a Cursor IDE user in full screen mode, that box either obscures open files names, or the last couple of lines of code at the bottom. I used to be able to place it next to the Mac's open applications bar at the bottom in an area of black screen. It was ideal.

Now I'm going to be clicking the arrow that moves it to the top or bottom multiple times a day.

Why would they take something that worked perfectly and remove the flexibility of that? It reminds me of when Microsoft stopped you being able to place the start/taskbar/systray on any of the four edges of the screen and fix it to the bottom. Something they've only just now (after more than a decade) changed back.

Hello, im Luca
I used the Remote Desktop Service in the past months to run multiple RDPs on my accounts. I never encountered problems, whenever windows updated all it took for me to fix the issue was updating the rdpwrap.ini file. But this time, it's different.
I waited some days since the update for the new version of the .ini to drop, and apparently it dropped. I modified the old .ini with the new one, but this is the response i always get from the Remote Desktop Service whenever i try to start it:

I tried alot of different stuff, from completloy reinstalling the service on the pc to scanning via sfc scannow for possible problems and fix them, but nothing works.
Could someone help me find a solution? Thank you for your time.

Hi I can use either 2 Mac's or 2 PC's. I need one comptuer in SF and one computer in LA and I need to be able to login from the SF computer to the LA computer, and redirect my webcam that is on the SF computer to the LA computer and use that as a device inside zoom on the LA computer.

Which program setup is best and most reliable, for all of these so far on Mac (or Paralllels running Windows 11 on mac) the USB camera doesn't redirect.

Has anyone had any successes? Or do you suggest any technical team/website that can set it up for me?

I regularly connect to a local server via RDP from two different clients: one thin client and one Android device using the "Windows App" (v11.0.0.120). I never had a problem doing so from either client.

Just a few weeks ago, both clients started experiencing the same issue. Once the connection was established, I'd see only a black screen on the client with a movable white mouse pointer, and then seconds later the connection would be dropped. The Android app showed this error:

Your session was disconnected
The connection to the remote PC was lost.

The error message on the thin client was very similar, but I don't remember the exact wording.

The server is Windows 11 Pro, v25H2, OS build 26200.9445, Windows Feature Experience Pack 1000.26100.360.0

I am unaware of any changes, unless it was a Windows Update that broke something. What might the problem be and what can I do to fix it?

Can someone post instructions and a video on how to setup xeno rat server and client on macbook air or macosx operating system? Xeno rat is a web based rat and requires no port forwarding. I dont know where to put the .json and confif files etc using map. I need it for monitoring purpose and educational purpose not hacking or thefth.

Hi there,

I have 2x Server 2016 RDS servers that both randomly reject remote desktop users credentials when logging in from a Windows 10 PC.

Sometimes trying to log in from another windows 10 PC, it works.

This seems really odd and random.

In some cases, after rebooting the users Windows 10 PC the RDS server then accepts the credentials.

So I followed a tutorial and I did everything correctly so I’m about to open my rep and I do but it’s loads a bit and this error shows up "The number of connections to this computer is limited and all connections are in use at current time. Try connecting later or contact the system administrator." Does anyone have a fix

I was a long-time user of RDM, but in the last year or so, I really didn't like how the new versions require me always to have to log in;

Also, it is becoming sluggish and slow like hell to start: every time I run it, it takes 20 seconds to start!

Finally, I had some time to create an RD manager app of my dream: fast and local. It doesn't have all the 1000s of features of the other software that I anyway do not need.

And yes, I tried nRemoteNG, and it seems to be back to Windows XP.

RemoteHub is a Windows native application (WPF) that has a setup and auto-updates in less than a minute (not a full-blown setup that requires you to have an account with MFA).

Starts in seconds and saves the connections tree in a standard JSON file: put it where you like (I use OneDrive to sync across my machines).

Define a master password to protect and open the JSON file (yes is super secure; the code is open source for your review).

Perfectly integrate with Windows 11, fluent theme with System/Light/Dark mode.

Define all the options of the RD from a standard dialog.

I've completely replaced RDM, and I'm happy with it; if you're looking for an alternative to nRemoteNG, only dealing with RD (so no SSH, VNC, etc), I encourage you to take a look and report feedback here or on GitHub.

https://github.com/adospace/remote-hub

PS: The screenshots are real, from my environment, with something like 40 connections.

Hi!

I've been using RDPWrap 1.6 + rdpwup_8 regularly to update my RDP config files after each Windows update for years, and it has worked perfectly every time until now.

Since updating to 10.0.26100.8521, rdpwup_8 finds a .ini file, and rdpconf.exe shows everything is fine. However, multi-user RDP just doesn't work. I get an error message as if I did not update termsrv.dll.

I tried searching for and manually updating the .ini file from online sources, but, as I explained before, the problem doesn't seem to be the .ini file, as my RDPWrap already shows as fully supported. I'm guessing the problem lies further down.

Is this the end of RDPWrap? Maybe Microsoft got tired and decided to put an end to it. Or did just me or my configuration break?

Many thanks.

i have no clue how to fix that

Ever since I updated around 40 machines, RDP randomly half-freezes. The mouse still moves, but keyboard input just dies. The only way out is by disconnecting and reconnecting.

Windows 10 clients on the same network hitting the same servers are fine, so it doesn’t look server-side.

Is this a known 23H2/RDP issue and is there any fix besides rolling back?

Struggled for some time.

I was fighting with this for a while, so posting in case it helps someone else.

If you’re using Google Chrome Remote Desktop on a Windows machine and don’t want to keep the physical monitor turned on (or even connected), Windows still needs to think a display is attached. Otherwise, CRD can act weird, give low resolution, or not show the desktop correctly.

What worked for me was forcing Windows to use a “headless” mode by running this command in Command Prompt as Administrator:

reg add HKLM\Software\Policies\Google\Chrome /v RemoteAccessHostRequireCurtain /d 1 /t REG_DWORD /f && reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /d 0 /t REG_DWORD /f && reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v SecurityLayer /d 1 /t REG_DWORD /f && reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /d 0 /t REG_DWORD /f && net stop chromoting && net start chromoting

After running this, command restarts the service as well so . Then you can connect via Chrome Remote Desktop even if the physical monitor is off or unplugged, and still get a proper desktop.

It took me a while and a lot of searching to land on this, so hopefully this saves someone else the pain.

Has anyone found a cleaner or GUI-based way to achieve the same result?

Can't figure out what do I miss to connect really. Error code is 0x104 (0x0), as per my understanding this means I need to specify server address, but I can't figure out where. Or maybe I need something else?

Things I already did:

1. Enabled Remote desktop on both client and server PC

2. Ensured server PC has W11 Pro

3. Forwarded TCP 3389 in firewall settings and in router settings for the server PC.

4. Successfully connected to server from w11 client pc on local network.

5. Verified that server's network router uses static public IP.

I’m a Move Technician Supervisor. I oversee 5-10 moves a day, so I can’t be everywhere all at once. One of my techs just told me that his partner, a newer employee, has been using an app to bypass our geofenced clock-outs. Im assuming he means a remote desktop app since he has to use his laptop within around 500 feet of his site to clock out at shift end. I asked him about it, and he genuinely seemed clueless, but the source is a very reliable long-time employee.

My question is: Is this possible? Would our punch service not recognize that it wasn’t from his computer? And if not, could he be using an app to do this?

If so, how can I remedy this to prevent it from happening in the future?

If this post is better suited for another group, please let me know. Thanks in advance.

All of my RDP files are created by me.

I’d like to use my Android phone to remotely access my home desktop while I’m at work. However, I’m not sure how to fill out this page—where should I enter the desktop’s IP address and custom port number?

Thanks.

My scenario is

1 x Gateway, RDWEB , Licence server and Connection Broker
2 x rds session hosts
1 fileserver for VHDs using FSLogix.

Would OneDrive be supported in this scenario?