Remote desktop error

[Eric Maxon]

Hi there I have been trying to remote desktop to my vmware machine and recieve this error message.  does anyone know how to fix this? 

The graphics display components in the remote session failed to start up.

Error code: 0x11

[Technogeezer]

There's a recent thread in  this forum that describes the same issue. The last update to the thread suggests that the issue may have started with the 2025-02 Microsoft updates. I've not been able to reproduce this on Windows 11 ARM Professional running the latest 12.5.0 VMware Tools, but the poster in the other thread could reproduce at-will. 

What Fusion version, Intel or M-series, and Windows 11 Pro build are you running?

Perhaps someone from Broadcom can pass this issue to the VMware Tools team to see if this is a Microsoft problem or a VMware problem due to some Microsoft change? 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Eric Maxon]

Thanks for the questions.  I'm running a new mac mini m4 pro and have windows 11 pro

[Technogeezer]

What kind of monitor are you using with that Mac mini, and what resolution do you have it set for?

In the Windows App, how do you have the display for the connection configured? Do you have "Optimize for Retina displays" and "Start session in full screen" set?

I also assume that when you installed VMware Tools in the VM that you chose the "Complete" option, and not "Typical" or "Custom". 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Eric Maxon]

Thanks for asking. I have a LG TV that I use as a monitor 55" 3200 x 1800

On VM machine - display is accelerate 3d graphics on supports directx 11 use full resolution for retina dispaly

scale high resolution all view modes

auto adjust user interface size in the virtual machine

virtual machine resolution - use fusion display preferences

as for the tools I would think i did full, but i don't know for sure

[Technogeezer]

Try the following:

In the Windows App setting for the connection, uncheck "Optimize for Retina displays" and "Update the session resolution on resize". Now choose the resolution from "Default for this display" to "1900 x 1200". See if the problem still occurs.  

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Eric Maxon]

Thanks for the ideas - I did that, but still receive the same error

[Technogeezer]

Is this a brand new VM installation or one that has been around a while and upgraded?

This is quite puzzling - there appears that there's may be something awry with high resolution / retina displays that's not working quite well.

One thing that I saw from some similar issues in the Intel PC world is this - it might be worth a try:

Log into the VM from the Fusion console window. Don't have the VM in full screen mode, let it open in a window. Set the resolution of the screen in the VM (using Settings in the VM) to something like 1920x1200 - the window should resize to match the new resolution. .

Now go the Windows app and see if the problem still exists. 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Technogeezer]

@Rajeswara Reddy Kotla is there someone on the VMware Tools team that could take a look at this?

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Eric Maxon]

it's a new install and still no luck

[Eric Maxon]

I'm running fusion 13.6.2 on a mac mini pro m4 mac os 15.3.1 windows 11, 64 bit ARM Im not sure how to tell what version of VM tools is running

[Husheng Zhou]

You can find out your vmtools version by clicking Control Panel -> Programs and Features -> VMware Tools. The VMtools version will show at the bottom of the panel. Can you also check which version of display driver are you using? Device Manager -> Display Adapters -> VMware SVGA 3D -> Properties -> Driver -> Driver Version

[Eric Maxon]

thanks im running vmtools 12.4.5.23787635

I hope that helps, Im really at a loss as to why this does not work

[Husheng Zhou]

Did you try to sign out the current user on VM to release all sessions?

Try this on your VM: Sign out -> login -> Sign out again. Then use RDP from another machine (physical or VM) to connect to the VM.

[Eric Maxon]

Thank you for the suggestion. I have shut down the VM machine exited out of VMware rebooted the computer and started over again still without change. I have tried to connect via rcd from two different computer computers with no luck.

[Husheng Zhou]

Similar issue is observed in another thread, https://community.broadcom.com/vmware-cloud-foundation/question/cant-connect-windows-11-arm-vm-using-remote-desktop-on-host-machine-macos-m1
Can you try the latest VMtools-12.5.0 (https://packages.vmware.com/tools/releases/12.5.0/windows/arm/) and follow the method suggested by me in this thread?

[Technogeezer]

I would suggest uninstalling the current version of VMware Tools that you have installed in that VM and not just upgrading the Tools over the version currently installed. Restart the VM after uninstalling the Tools, then install the 12.5.0 Tools from the ISO file that you've downloaded on the Mac (attach it to the virtual CD/DVD drive). 

Also, when installing Tools 12.5.0, choose the "Complete" option, not "Typical" or "Custom". 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[stainless steelrat]

Hey Technogeezer,

I had a working vm on the 4th.... yesterday and today exhibits the symptoms. 

I had upgraded yesterday to fusion 13.6.3, and the new vmware tools package 12.5.0, and it still mostly wasn't happy. Last night before bed it worked once.... but today, same symptoms if either black screen, or 0x11. (depends on if the guest is signed in or not). I just downloaded your iso file. Uninstalled, reboot, install, reboot. Same behaviour. 

Mac sonoma 14.7.3
Fusion 13.6.3 
Windows 11 arm, version 24h2 26100.3194
ms rdp mac app 10.9.10 (2327)

This is the only thing that I find weird are these few "unknown/flagged devices in device manager. I'm not sure whether they were an issue before or not.....

[Eric Maxon]

That was a great idea - I removed the video driver and restarted windows and then tried to RDC, unfortunately, it didn't work. Thanks for the creative idea. Hopefully, somebody has another one.

Eric

[Husheng Zhou]

One workaround of this issue is to use VM's build-in VNC. To enable VNC, shut down your VM, and then go to VM's settings -> Advanced -> Check "Remote display over VNC" -> Change port or password as needed. Boot your VM and then use any VNC client to connect to the VM using VM's IP:PORT (5900 by default). Make sure your VNC client and the VM are within the same subnet (using bridged network for VM makes things easier).

[Eric Maxon]

I don't know if it's good or bad but connecting with VNC does work.  Odd that I can't make RDC work.... thanks for the work around

[Technogeezer]

Interesting. The Base System Device and USB controller are expected. The other two unknown devices are indeed interesting. I do not see them on my VMs. Does Device Manager have anything interesting to say about what they are?

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[stainless steelrat]

The one searches out to be either an acpi device for a lenovo laptop, or an old serial card device.

Which is weird considering I'm not doing any pass through, and they don't go away after removing and restarting. Connected to the mac, is a caldigit thunderbolt dock, and a razor external cam.... 

Anyways, no hardware has been added and/or removed when it was working or now when it does not. 

I think it must be tied to a windows change somewhere for it to be working one day, than not the next. 

The add remove programs only shows the vmware tools, and a fresh copy of the onedrive client 25.020.0202.0001.... but I don't see how that would do anythings. Especially when I can login to the guest directly..... 

If there's anything that you guys want me to try.... just let me know.

[Technogeezer]

@stainless steelrat I've never seen those two "Unknown device" devices on a Windows 11 ARM VM. Can you delete them, reboot the VM, and then see if the devices have been re-discovered?

By any chance would this be a multiple monitor setup? 

Can you also post a copy of the .vmx file for this VM so I can compare it to a known good working example. 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[stainless steelrat]

It is a multiple monitor setup. I have the laptop screen + 2 x Dell 24" monitors connected to the caldigit thunderbolt dock. I have been using multi-monitor setups for over 20 years.

Here's your vmx.....

.encoding = "UTF-8"
displayName = "win11arm-22h2"
encryptedVM.guid = ""
guestInfo.detailed.data = "architecture='Arm' bitness='32' buildNumber='26100' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='26100.3194' prettyName='Windows 11 Pro, 32-bit (Build 26100.3194)'"
encryption.keySafe = "vmware:key/list/(pair/(phrase/2ueKMS%2fwubw%3d/pass2key (redacted)

I had to confirm. (OS is set to win11 arm)

But I've been running this guest for a long time. It would have started with the fusion 13 tech preview or just after. The encryption settings are set to "all files", vs only needed. 

[Technogeezer]

Is it possible that you turned on Windows kernel debugging (that was required for very early Windows 11 ARM running with the first tech previews of Fusion on Apple Silicon)? 

The vmx file isn't very helpful since you have full encryption enabled for the VM, unfortunately.

Have you tried disconnecting one of the monitors and seeing if that changes anything?

One other question since you have multiple monitors. From the Fusion menu bar, do you have :Use All Displays in Full Screen selected.

The VMX does indicate that you are still running the 26100.3194 build. Can you verify that by running the winver application from within the VM?

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[stainless steelrat]

OK, so a few answers. 

1. The multi monitor has never been an issue before. I think the extra entries in the device manager might be related to the fact I'm forcing fusion to leverage the nic on the caldigit dock. Because I'm on a wired connection when I'd be running the vm in my office. And up until the 5th of march, it was working just fine. 

To answer your question about the multiple monitor mode, no it's not optioned. I run it on only one of the external displays so I can multitask with other windows.

From a winver perspective. I most recently "downgraded" to the version to a build before the preview patch was installed, by reverting the snapshot. 



I have a time machine vm guest file that I restored the other day. But I haven't tried to actually use it yet, because I'm worried about name duplication and other guest issues when you restore things. I might have some time to try that this weekend as just a generic troubleshooting process. I'll try to see if it will let me change the encryption options through that process.... or by removing the tpm, etc.

Thanks for the help..... considering that it's a "not just me" issue with the rdp error 0x11, I'm sure there will be more "commonalities" out there.

[stainless steelrat]

Hey @Technogeezer

So I took my time-machine restored copy of my vm. (unfortunately it was from back in dec). Rdp works without issue. Which implies it's definitely a windows patch or modification which seems to do it. 

I am trying now to not upgrade to 24h2 yet, just in case. Running windows update it only "found" these files to update instead:

I'm going to see how that does. The vmware tools is likely the older version (12.4.5.23787635) So process of elimination lets see what breaks it. Retrying this process is technically just the "time machine" restore away from going back to this point. 

[stainless steelrat]

So this afternoon, my recovered vm upgraded to 24h2.... on initial boot it let me rdp. Disconnect, and attempt to reconnect, and I get the error. On that vm I'm now trying to go back to 23h2..... Because up to when it upgraded rdp worked just fine. I find it very interesting that it lets you rdp the one time..... and one time only.

Its now reverted: 

rdp is working again. I'll try again with it tomorrow to confirm. I have added a few registry keys which should force the current 23h2 build.... 

[Technogeezer]

Which 24H2 build did it upgrade to?

This is Patch Tuesday, so I'm expecting another 24H2 update to be offered by Microsoft tomorrow. It'll be interesting to see if the symptoms change with that new update.

- Paul (Technogeezer)

[stainless steelrat]

@Technogeezer

I have "re" upgraded to the 24h2 on my restored vm. I was able to login through rdp on the first attempt. But I need to see if it will let me login after a few reboots and things. 

patch tuesday build:

installed today (march 12)

Also the current ms remote display adapter info: 

If it gets broken that will be the first thing I'm gonna try. Also, I think the kernel debug stuff seems to be turned on (still in this guest maybe) so I'll run the commands to remove it just to be safe.

Thanks for all the help on this....

[jrocks44]

Thanks for doing the leg work on this.  I've been having the same issue.  I can RDP once and then not again.  I found that if I uninstall Microsoft Remote Display Adapter under Display adapters in Device Manager, that I'm able to RDP in again.  You have to Show hidden devices to see it.

[jrocks44]

I came across a solution here that worked for me on the 24H2 build on my VM.  

From that post:

Setup local or AD-enrolled group policy on/for the RDP destination machine (see also screenshot attached):
Local Computer Policy> Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Select network detection on the server - set to Enabled, Turn off Connect Time Detect and Continuous Network Detect

Just for those who are not familiar with GPOs, you can run group policy editor for the local machine by:
Hitting Windows-Key + R, then typing "gpedit.msc" in the field and then click "OK".

[Eric Maxon]

fixed deleting the hidden driver did it

thank you everyone

Eric

[Technogeezer]

@Eric Maxon - was the hidden driver re-discovered after reboot?

Some research is finding addtiional blog posts that indicate this may be an issue with Remote Desktop on Windows in general - not just a VMware problem. 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Eric Maxon]

Great questions, yes the file re-created, but is working....

[stainless steelrat]

@Technogeezer

So for my main vm guest, which was originally upgraded to 24h2 and the source of the problem. I "restored" it from time machine to be back to 24h2 with feb patches. (vs the downgraded, working 23h2).... Then I installed the newest patch tuesday patches. Which puts me to this build:

So now I'm matching my 23h2 -> 24h2 (march build) test guest vm which has been working fine since yesterday.... And you think it would work, but no I'm still still getting the 0x11 error. 

As a result, I tried to remove the rdp graphics device from device manager.... as recommended by @Eric Maxon. Once that was removed, and a reboot, rdp now works works just fine. (the same as my "test guest"). 

Which means, if you are are on 23h2 and never had any issue, upgrading to the march patches, you'll likely be fine. If you upgraded to another 24h2 and/or experienced the problem, patching with march patches won't fix it alone you'll need to remove the hidden rdp graphics device, and then it will work. You'll then be able to patch to march patches, just to be current.