Not finding anything that's immediately pointing to a root cause, but here are some things to think about;
It looks like there are remnants of Tuxedo NTFS and another third party NTFS driver on this system. I tend to avoid these types of third party drivers because they have shown to de-stabilize the macOS kernel. It doesn't look like the kernel extension is loaded, but I'd try either running in safe mode as a test or remove the drivers entirely.
There are some instances in the Fusion vmware.log file of issues with the virtual NIC. I also see that you're running a utility for file transfer to Android. I would re-try this build by booting the Mac in safe mode, then run Fusion without using any additional applications (especially something that's playing around with networking) to see if the problem exists. If you're able to complete the build successfully, I'd suspect a conflict with something else that you're running on the Mac.
Original Message:
Sent: Sep 16, 2024 02:26 AM
From: changanmoon
Subject: An annoying bug of Fusion
Thanks for your reply! I am using Windows 11 23H2, and I was building a 24H2 (version 26100.1742) Windows ISO file.
I am attaching a quick problem report archive, along with some files (including log files in the VM bundle) that could be useful here.
Original Message:
Sent: Sep 13, 2024 02:19 PM
From: Technogeezer
Subject: An annoying bug of Fusion
Which build of Windows 11 ARM are you running in the VM, and which build of Windows are you trying to build from UUPdump?
You may also want to collect a quick support bundle and post that - the logs from both the VM and Fusion GUI it collects may be useful in helping to identify what's going on.
I've built ISOs from UUPdump using various Windows 11 builds. I'm trying to build the Windows 11 24H2 release preview iso (26100.xxx) on a VM that's running the Windows 11 23H2 beta channel release (22635.4145) right now -- so far no issues. I'm running on an M1 Mac Mini with the VM set to 4GB of memory, 2 vcpus, and a virtual hard disk size of 96GB (expanded from the default of 64GB, and the recovery partition moved so that I could expand the C drive).
------------------------------
- Paul (technogeezer)
Original Message:
Sent: Sep 13, 2024 06:38 AM
From: changanmoon
Subject: An annoying bug of Fusion
Hello there, I am a Fusion user.
Recently I wanted to create an Windows .iso with UUPDump on a Windows 11 arm64 virtual machine on Fusion, so I ran the script `uup_download_windows.cmd`.
At first, everything seems to be fine (fig. 1):
However, after a while, the VM accidentally stopped working, and its screen gone black like this (fig. 2):
I tried to start this VM, only to find that Fusion failed to power on VM (fig. 3):
I even checked out the virtual machine library as well, but it is weird to see that the VM's status is "running" (fig. 4):
I restarted my Mac and relaunched Fusion, then the virtual machine could be opened normally.
However, this issue persists when running UUPDump script on Fusion. I tried the same script on other VM products, but such issue won't appear.
It seems that there's a bug in Fusion, and it is quite annoying to me.
Could anybody look into this? Thanks!
-------------------
FYI, here are some information I could provide:
General Information:
- Fusion version: 13.6.0
- macOS version: Sonoma 14.6.1 (23G93)
- Mac chip: Apple Silicon (arm64), M1 Pro
Specifications and settings of this Windows VM:
- 8 GB RAM, 4 CPUs
- 64 GB or 256 GB hard disk
- Have activated "Synchronize time", "Pass power status to VM" and "Enable verbose USB debugging", but I've left other settings default in advanced settings (fig. 5)