Fusion 13 - Windows 11 ARM installation hangs indicating no network access

[Mijrob]

I built multiple levels of Windows 11 ARM ISO's using VMWARE docs and ALL fail during installation indicating no network access when network is available.  I tried NAT, AutoDetect and Shared options.  None seem to work.  Ideas?

[Technogeezer]

The reason you are getting no networking is that Fusion provides a vmxnet3 virtual NIC for its Windows 11 VM and Windows 11 ARM does not have a driver for this NIC out of the box.  Fusion Help has a topic "Manually Install VMware Tools on Windows" that describes how to install VMware Tools on Windows 11 ARM, but it's incomplete IMO.

Here's a procedure that I've used for the Tech Preview that should work for initial setup of Windows 11 ARM It avoids what you're seeing.

After initial installation of Windows 11 ARM from ISO, you'll see the first screen for the Windows setup process:

Don't click in this window. Instead, press Shift-Fn-F10 that will open a Windows command prompt running as an admin.

At the command line prompt, execute PowerShell:

powershell

Go back to the Fusion menu bar and select Virtual Machine -> Install VMware Tools. Click "Install" on the next dialog when prompted. The VMware Tools ISO will be mounted to the VM as the D drive.

Wait a few moments while the D drive is mounted. Then go back to the Powershell window and type the following commands:

d:
Set-ExecutionPolicy RemoteSigned
.\setup.ps1

Drivers for both vmxnet3 and VMware SVGA 2D graphics will be installed. The screen will blank out briefly while the graphics driver is installed. If you feel like poking around, there is a readme file on the D drive that provides more complete documentation on the setup.ps1 script that installs the drivers.

When the drivers finish installing,  reboot the VM with the following PowerShell command:

shutdown /r /t 0

After reboot, the setup process will restart at the first screen. Continue the process and the network will be discovered.

Edit 2025-04-27: Please note that this procedure is obsolete and no longer required. See other posts in this thread. 

[Mijrob]

Thank you. I found the section I. The help guide. My current issue is sharing files between Mac and arm systems. I have file sharing turned on and selected the sharing directory and rebooted. Windows is not able to see Mac files. Also I added printer sharing and when I try to add printers in windows the add process fails. Ideas?

[ColoradoMarmot]

There are no tools for windows yet, so no sharing (file, print or clipboard), and no copy/paste.

[Mijrob]

Thank you!  After waiting more than a year for Fusion 13 and not having file sharing is VERY disappointing.  I have been using CrossOver, which works OK, pending full function Fusion.

[Technogeezer]

---

 wrote:

After waiting more than a year for Fusion 13 and not having file sharing is VERY disappointing.  

---

You can get file sharing in a Windows 11 ARM VM by using Windows file sharing in the VM and configuring Windows file sharing on macOS works.. It's just that Fusion's folder sharing doesn't. That's definitely inconvenient not having folder sharing.

Personally given the warts and issues with VMware folder sharing over the years that they still haven't fixed, I'd seriously consider Windows file sharing.

[-MATTO-]

 - you rock, this worked - thank you!

[SpiderTrumpet]

Super helpful.  Thanks

 

VMWare you truly are a bag of skid marked pants for charging £100 for a product that needs its community to make it work.  Last time!  My work comp uses Parallel's and it just works out the box.

[kwarts]

Thank you!!

[Blendax74]

Hi kwarts,

today I tried exactly this on my new MBP 2023 M3 Max... but I still can't get Win 11 ARM to work.

Three devices remain driver-less (even after installing VMWare Tools with the provided procedure) - and I also had to install Windows with the "I have no internet" trick (Open cmd with Shift + F10 and type OOBE\BYPASSNRO. Your computer will restart and now you will have the "I don't have Internet" option.).

But now I still cannot get the drivers to work (SVGA-Adapter installed correctly):

- Basissystemgerät (Das Gerät "PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD&REV_10\3&11583659&0&07" erfordert weitere Installationen.)
- Ethernet-Controller (Das Gerät "PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00\000C29FFFFA9881D00" erfordert weitere Installationen)
- USB (Universal Serial Bus Controller) (Das Gerät "PCI\VEN_15AD&DEV_0774&SUBSYS_197615AD&REV_00\3&11583659&0&80" erfordert weitere Installationen.)

Is there maybe a compatilibility issue with the new MacBook Pros with M3 (Max) chipset?
Thanks for your assistance

Klaus

 

[Technogeezer]

There's not a compatibility problem. It's more likely the ISO that you used or the procedures you followed to install the ISO.

Can you tell us:

• Version of Fusion. If you're not using 13.5, stop right now and install Fusion 13.5. Follow procedures in the Fusion 13.5 in-product documentation and the latest version of the Unofficial Fusion for Apple Silicon Companion Guide https://communities.vmware.com/t5/VMware-Fusion-Documents/The-Unofficial-Fusion-for-Apple-Silicon-Companion-Guide/ta-p/2939907
• What is the file name of the Windows 11 ISO that you are using and how did you get it. You should have downloaded it using the Fusion 13.5 download tool - but beware that there's a bug in it for non-English macOS system languages. A workaround is found in the Companion Guide. 
• What "procedure" did you use to install VMware tools? Any procedure that told you to use Powershell is obsolete. 

If you got the VM installed using the "I don't have internet" option, you should be able to use Fusion menus Virtual Machine > Install VMware Tools to install Fusion 13.5's VMware tools (which will install the video and network drivers). It's installed just like the Tools on Intel Macs - the Tools ISO will automount and Autoplay will start the VMware Tools Setup program. Any procedures that are telling you to use Powershell are obsolete. 

Ignore the base system device and USB serial bus controller messages. They are normal and not the source of your problem.

 

 

 

[Blendax74]

I just helped myself --> as you've said, my (self-generated) ISO was the problem.
After downloading the ISO-Image with the feature of your software (and reinstalling Windows 11 ARM), the issue is solved.

=> everything works now (2 devices remain "unknown", but as you've said - these are not important).

Thanks Paul for you quick support! - I've just downloaded your Guideline, which told me the right trick - WELL DONE(!!!) . VMWare owes you money...

THANK YOU - very much appreciated!

[Technogeezer]

---

 wrote:

Thanks Paul for you quick support! - I've just downloaded your Guideline, which told me the right trick - WELL DONE(!!!) . VMWare owes you money...

THANK YOU - very much appreciated!

---

You're welcome. It's a good thing that this ls a free give-back to the community - they wouldn't want to pay me what it's really worth to them and the community. 

[Meloserj]

I read this post and I have same issue on my M3 MBA, the 2 devices don't have any driver from VMWARE drivers on fusion player.

The devices are:

PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD&REV_10\3&11583659&0&07

PCI\VEN_15AD&DEV_0774&SUBSYS_197615AD&REV_00\3&11583659&0&80

I believe vmware should add these 2 drivers in soonest time.

Still keep searching for them but I doubt I could find it through google :(

[Technogeezer]

Those two missing devices are normal and will not impact you running your VM. See the Unofficial Companion Guide for a more in-depth explanation of what these devices are and why the missing devices don't matter.

------------------------------
- Paul (technogeezer)
------------------------------

[gen843620]

This was helpful but I used a slightly easier way after Powershell gave me an error.

Instead of Powershell, I just used your recommendation, "Go back to the Fusion menu bar and select Virtual Machine -> Install VMware Tools. Click "Install" on the next dialog when prompted. The VMware Tools ISO will be mounted to the VM as the D drive."

THEN instead of powershell, I clicked the Windows 11 installation wizard's "Install drive" button and clicked "Select" on the D: drive.

That's it. 

Don't "select" a sub folder on the D: drive. Just "Select" the entire D: drive.

I just did it and worked. 

Thanks, though. I didn't know I could mount VMWare Tools during the installation. That was the magic trick. 

[Technogeezer]

Yes, you can select the D: drive and the network driver installation will work. However what I'm finding is if you select the D: drive  you will get a "something went wrong" message in the "Let's get you connected to the network" dialog after the driver is installed and the network is connected. This can be confusing for some users. You'll think that something is wrong when it really isn't.

Drilling into the D: drive and selecting the vmxnet3 sub-folder doesn't display that "something went wrong" message. It's a safer method in my eyes, but either way works. 

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

[gen843620]

I just know what actually worked for me. The powershell command just showed an error.

Drilling into a each subfolder on D: appeared empty.

Selecting the D: drive overall actually worked. It's not theoretical. I did it. Then my VM worked and I set up Windows 11.

Note, though, it's a moot point, because the ARM version of Fusion doesn't include sharing with the Mac desktop ("Sharing" is completely missing from Fusion menus and I looked it and confirmed it's not part of ARM Fusion. That's a deal breaker for me. 

I run a Windows program I need to backup to the Mac-side so its data is automatically backed up by two backup services.

Sharing a network folder from the Mac side worked but I don't want to have a perpetual share broadcasting as I move my laptop to numerous networks while working remotely.

So after getting it all working, I deleted VMWare Fusion ARM and the Win11 VM file and went with Parallels, which has sharing with the Mac side just as VMWare Fusion for Intel still does (I use that, too). Once I replace that Intel Mac, I'll have to switch its VMWare Fusion to Parallels, too.

[welldrake]

Unfortunately @Technogeezer's solution didn't work for me in Dec 2024.  Here's what did work.

• Start installing Windows 11 ARM
• Get to this screen:

• Go back to the Fusion menu bar and select Virtual Machine -> Install VMware Tools
• Click "Install" on the next dialog when prompted. The VMware Tools ISO will be mounted to the VM as the D drive.
• Wait a few moments while the D drive is mounted.
• Click 'Install driver' button (in screenshot above)

• Single click on (d:) VMware Tools
• Click 'Select Folder'
• It should find the driver and allow you to continue

[Technogeezer]

Not sure what solution of mine you tried - it may have been for an older version of Windows and Fusion.

This is the same solution I posted in the forum three weeks ago in  https://community.broadcom.com/vmware-cloud-foundation/discussion/windows-11-arm-iso-now-available-for-download-from-microsoft when Windows 11 24H2 ARM ISOs became available from Microsoft. This solution works for any Windows 11 ARM 24H2 ISO that's not created with Fusion's "Get Windows from Microsoft" feature (that includes downloads from Microsoft's web site and built from UUPdump.) . ISOs downloaded with Fusion's feature automatically add the VMware network driver to the ISO so that this procedure is not needed.

------------------------------
- Paul (technogeezer)
------------------------------

[Mr Pee]

This, you just select the folder from the drive, it will install the driver.

[Juan Garcia]

Hi WellDrake,

Your answer perfectly works! Thanks for smart solution for this issue!

Have a good day!