Two issues with Device Manager in VMware Fusion not recognizing some devices: Base System Device, USB Controller, and two ICDIs for my microcontroller unrecognized

[MCUStu3]

Hello,

I am running Windows 11 on a MacBook M1 with VMware Fusion.
It installs nicely and does everything else I need it to except for the two issues below.
The VMware Tools are installed.
I usually update everything in my computers.

First Issue:

When opening Device Manager, under the Other Devices category, I have the following two items with a yellow triangle next to it as shown in the attached picture (named Unrecognized USB Controller): Base System Device and Universal Serial Bus (USB) Controller.

What do I do about this? I think, because of this I have the second issue below.

Second Issue:

On top of the First Issue...

I have a TM4C123GXL microcontroller (MCU) and a program (Keil, which installs fine) that I need to use on a Windows (and known to work in VMware for Macs as stated by the instructor's directions) to connect to my MacBook laptop for my class so that I can study while I'm at school instead of home at my Windows 11 desktop computer.

When opening Device Manager, under the Other Devices category, I have two items of the same name with a yellow triangle next to it as shown in the attached picture (named Two Unrecognized ICDI): In-Circuit Debug Interface and In-Circuit Debug Interface. This is supposed to be normal as pointed out by the instructions for my class. We're supposed to download some drivers from the manufacturer's website at TI.com. Then, when going to Device Manager and updating the two In-Circuit Debug Interface (ICDI) drivers that have the yellow triangles next to it, we're supposed to point the folder with the downloaded drivers in the Browse My Computer for Drivers option. This would install the Stellaris drivers for my MCU so the Keil program could run it with JTAG or something. In my Windows 11 desktop computer, this works fine and dandy with the same device and cable and everything. However, in my MacBook M1 laptop, it does not work. It shows that it was not able to install, as shown in the attached picture (named Unable to Install). I am using a data cable that came with the microcontroller and it is the same one I used for both computers

Things I have done to try and fix this as pointed out by the internet but to no avail:

1) Reinstalling and repairing VMware Tools.
2) Uninstalling VMware Tools, restarting, installing VMware Tools again, and restarting. I've tried typical and complete install and used the latest download from Broadcom's portal as well.
3) Editing the ".vmx" file's "ehci.present = "TRUE"" to FALSE as well as other lines. However, when I get to my login screen, the screen is frozen and I can't use any inputs. The only way to get out of there would be to shutdown the VM using the VM menu and reverting the file.
4) I went to the Virtual Machine menu to go to Settings. In the Removable Devices category for USB, there is an item called "Luminary Micro In_Circuit Debug Interface" which is supposed to be my Stellaris ICDI for my MCU. I go down to the Advanced USB options to try USB Compatibility for USB 1.1 and USB 2.0, but the VM freezes at the login screen like in step 3 above until I put the USB 3.1 option back up.
5) In the Virtual Machine menu to go to Settings, under the Other category for Compatibility, I looked under the Advanced options drop down for Use Hardware Version to make sure that it is version 21. Some people said that this needed to be 21, and it already was.

Researching, trying all of this out, and more took dozens of hours... 
I would appreciate some help so I can make my life easier and study on-the-go like at school.

6) Setting the Virtual Machine > Settings > USB > ICDI Plug In Action to Connect to Windows. However, this always revers back to the "Use default action".
7) In the Mac's System Settings > Privacy & Security > Files & Folders, VMware Fusion does have permission to access Removable Volumes I suppose noted by the "Full Disk Access".

[Technogeezer]

When opening Device Manager, under the Other Devices category, I have the following two items with a yellow triangle next to it as shown in the attached picture (named Unrecognized USB Controller): Base System Device and Universal Serial Bus (USB) Controller.

Those two specific drivers are harmless and expected for a Fusion Windows 11 ARM VM. The lack of a driver for those two devices do not impact the operation of a Fusion VM on an M-series Mac.

To your second issue.

It looks like the device is being passed to the Windows VM by Fusion properly. What's happening is that Windows is not finding an appropriate driver for it.

A common issue for devices that require the installation of a driver on Windows 11 ARM is that the vendor has not provided a compatible driver for the device. Windows drivers need to be specifically compiled for the ARM CPU architecture to run under Windows 11 ARM - drivers that work on Intel versions of Windows will not work on WIndows 11 ARM. The first thing that I would do is to check with the device's manufacturer and verify that they have an ARM version of the drivers. Otherwise the device will not work - either on a Windows 11 ARM VM running on M-series Macs or a physical Copilot+ CPU with a Qualcomm CPU chip. 

The reason your device works with your Windows 11 desktop computer is that it is almost certainly running Windows 11 x86_64 (Intel/AMD CPU) - which a driver is available for.

[Technogeezer]

I don't know i this is possible or not, but would you be able to run that development environment in a Linux VM (for example, using Ubuntu or Debian)? Many times the open source community has ported device drivers for Linux running on an ARM CPU that the device manufacturers haven't taken the time to port. 

[MCUStu3]

Okay, this website/forum won't let me respond to people on my own posting. I'm concluding this for myself and everyone else out there that people are just too lazy to write new stuff for the ever changing world of technology and make people's lives easier by being flexible with technology. Therefore, in order for this to work, the hardware MUST NOT be only from a Mac computer. So, if you have the older Macs with the Intel chips in it, then it would be possible. Not possible for the new ones of this time, even though these are some of the biggest tech companies making stuff that thousands to dozens of thousands of people are buying or using or could be using.

[Technogeezer]

I understand your frustration. And your posts are getting through - which means that the moderators have released the "first time user" hold on you.

I don't think it's a "too lazy" argument. It's a return on investment argument. Windows 11 ARM didn't get a lot of consideration from the hardware community because it wasn't making a major dent in the markeplace. The operating system was limited to a tiny number of Microsoft Surface devices and the occasional Mac user that wanted to run Windows. Because the return may not have warranted an investment, vendors dragged their feet recompiling and testing drivers. Sometimes "build it and they will come" isn't enough of a business argument. It also was easier to continue with the status quo that "all computers have Intel CPUs.

One can hope that the more widespread availability of ARM-based Windows PCs will may change the minds of the hardware vendors to invest in the re-compile. 

There are exceptions, though. Arduino microprocessor boards and their IDE work fine on a Windows 11 ARM VM. Sometimes the open source community can be a bit more nimble.