Fusion 13.6.4 issues with macOS Tahoe

5. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

Technogeezer

Posted Sep 17, 2025 04:02 PM

You may want to hold off upgrading to Tahoe - especially if you have a Mac Studio M3 Ultra. Howard Oakley over at the Eclectic Light Company blog is reporting an incompatibility with Tahoe and these Macs. See https://eclecticlight.co/2025/09/17/macos-26-0-tahoe-build-25a354-is-incompatible-with-mac-studio-m3-ultra/ for more info.

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

Original Message

6. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

Bigdave1357

Posted Sep 17, 2025 04:31 PM

I’ve seen similar complaints in MacRumors. My MBP M4 Max is working fine with Tahoe. Just Fusion that’s struggling.

Original Message

7. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

Bigdave1357

Posted Sep 17, 2025 05:01 PM

Seems this is only an issue for M3 Ultras that have first been updated to macOs 15.7 prior to attempting the Tahoe install. If you skip 15.7 you're good.

-------------------------------------------

Original Message

8. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

External Moderator

Technogeezer

Posted Sep 17, 2025 05:57 PM

Sorry for the delay in my response to this.

I've been able to reproduce this when the VM is running in full screen mode. I've not been able to reproduce it when running the VM in single window mode.

It's a curious bug from what I see. When the VM is running in full screen mode and the Mac sleeps, the VMware Fusion GUI app has quit. But as @Bigdave1357 says, the virtual machine is still running.

See if the following helps get the VM back without having to reboot or kill the vmx process:

Verify that the VM is running by using the following command vmrun -T fusion list You should see the command report that the VM is still running and shows the path to the .vmx file. Example: :
```
% vmrun -T fusion list
Total running VMs: 1
/Volumes/Virtual Machines/Windows 11 ARM 25H2 preview.vmwarevm/Win 11 ARM.vmx
```
Issue the following command to suspend the running VM: vmrun -T fusion suspend "path-to-vmx-file"
The path-to-vmx-file argument is the one that was returned by the vmrun list command, and should be enclosed in double-quotes as it likely has spaces in the path name. You will need to provide the VM's encryption password when prompted.
Here's an example:
```
vmrun -T fusion suspend  "/Volumes/Virtual Machines/Windows 11 ARM 25H2 preview.vmwarevm/Win 11 ARM.vmx" 
Encrypted virtual machine password: 
%
```
Note that you don't get a prompt that anything happened. Re-run the command in step 1 to verify that the VM has indeed suspended.
Now start VMware Fusion. You may be prompted for the password of your Windows VM. Provide it if asked.
You should now see the VM's full screen window appear. You should be able to resume the VM from this point by clicking in the window.

I wonder if the issue appears because the Fusion GUI is terminated by something during the sleep process, and that termination may be related to managing the VM in full screen mode.

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

Original Message

9. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

Bigdave1357

Posted Sep 18, 2025 05:30 PM

I can confirm that this works on my setup.

The bug can be replicated very easily: fire up a VM and then use the Apple Menu-> Sleep command to immediately sleep your machine.

Give it a few seconds to ensure the sleep has really taken effect and everything has shutdown.

Then move the mouse to wake up and you’ll find that the bug has bitten: the Fusion app has either quietly crashed or just shutdown, orphaning the running vm. Starting Fusion won’t rediscover the vm.

Follow Paul’s steps and the VM will suspend. Restart Fusion and then it will find the vm and you can resume work.

My vm’s are all encrypted, so the password is needed to do this. My passwords are long and complex so I keep them in the keychain.

It’s a PITA to dig them out and go through the steps to recover the VM. Quicker to simply kill the vm and go again, although that is certainly not recommended.

So you have three workarounds:

1. Kill the orphaned vm. Quick, but NOT recommended.
2. Use Paul’s method. You could put together a script or automation to make this more easy. You could even include the password if necessary, but that would mean disclosing it in plain text, which isn’t ideal.
3. Reboot your machine.

There’s another way: just don’t walk away from your machine with VM’s running, or configure your host machine not to sleep. Neither are particularly good options either, but something you can consider.

Hopefully Broadcom will class this as a high priority problem and issue a hot fix. It makes the whole Fusion app very difficult to use.

My thoughts are that either this only showed up in the release version of the app (highly unlikely in my opinion) or Broadcom did not properly test or test at all using the many betas released by Apple. If it’s the former, then I guess we’re all just really unlucky. If it’s the latter, I for one am really disappointed in Broadcom.

Redeem yourself by issuing a hot fix, and quickly.

Thanks for the workaround, Paul. No doubt it will help many people.

Original Message

10. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

External Moderator

Technogeezer

Posted Sep 18, 2025 05:40 PM
Edited by Technogeezer Sep 18, 2025 05:43 PM

Yes, killing the process will work, but my concerns are that unclean termination of the vmware-vmx process could result in other bad behavior. I'd rather err on the side of caution to not introduce a possibility of a corrupted VM.

Remember that technically macOS Tahoe hasn't been listed as qualified as a supported host operating system or Fusion. This isn't the first time a macOS upgrade has broken something with Fusion that required VMware/Broadcom to update Fusion to handle. Broadcom, like VMware before it, is very tight lipped on future product releases. It's difficult to say when they will release something that will address this bug.

This being said, I have started to ask about this through some moderator back-channels. I'm trying to make sure that the product team knows about this and maybe -- just maybe -- get some kind of response. At least I hope we can get "we know about it and have notified the product developers". I'll let everyone know how that turns out...

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

Original Message

Original Message:
Sent: Sep 18, 2025 05:08 PM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe

I can confirm that this works on my setup.

The bug can be replicated very easily: fire up a VM and then use the Apple Menu-> Sleep command to immediately sleep your machine.

Give it a few seconds to ensure the sleep has really taken effect and everything has shutdown.

Then move the mouse to wake up and you'll find that the bug has bitten: the Fusion app has either quietly crashed or just shutdown, orphaning the running vm. Starting Fusion won't rediscover the vm.

Follow Paul's steps and the VM will suspend. Restart Fusion and then it will find the vm and you can resume work.

My vm's are all encrypted, so the password is needed to do this. My passwords are long and complex so I keep them in the keychain.

It's a PITA to dig them out and go through the steps to recover the VM. Quicker to simply kill the vm and go again, although that is certainly not recommended.

So you have three workarounds:

1. Kill the orphaned vm. Quick, but NOT recommended.
2. Use Paul's method. You could put together a script or automation to make this more easy. You could even include the password if necessary, but that would mean disclosing it in plain text, which isn't ideal.
3. Reboot your machine.

There's another way: just don't walk away from your machine with VM's running, or configure your host machine not to sleep. Neither are particularly good options either, but something you can consider.

Hopefully Broadcom will class this as a high priority problem and issue a hot fix. It makes the whole Fusion app very difficult to use.

My thoughts are that either this only showed up in the release version of the app (highly unlikely in my opinion) or Broadcom did not properly test or test at all using the many betas released by Apple. If it's the former, then I guess we're all just really unlucky. If it's the latter, I for one am really disappointed in Broadcom.

Redeem yourself by issuing a hot fix, and quickly.

Thanks for the workaround, Paul. No doubt it will help many people.

Original Message:
Sent: 9/17/2025 5:36:00 PM
From: Technogeezer
Subject: RE: Fusion 13.6.4 issues with macOS Tahoe

Sorry for the delay in my response to this.

I've been able to reproduce this when the VM is running in full screen mode. I've not been able to reproduce it when running the VM in single window mode.

It's a curious bug from what I see. When the VM is running in full screen mode and the Mac sleeps, the VMware Fusion GUI app has quit. But as @Bigdave1357 says, the virtual machine is still running.

See if the following helps get the VM back without having to reboot or kill the vmx process:

Verify that the VM is running by using the following command vmrun -T fusion list You should see the command report that the VM is still running and shows the path to the .vmx file. Example: :
```
% vmrun -T fusion listTotal running VMs: 1/Volumes/Virtual Machines/Windows 11 ARM 25H2 preview.vmwarevm/Win 11 ARM.vmx
```
Issue the following command to suspend the running VM: vmrun -T fusion suspend "path-to-vmx-file"
The path-to-vmx-file argument is the one that was returned by the vmrun list command, and should be enclosed in double-quotes as it likely has spaces in the path name. You will need to provide the VM's encryption password when prompted.
Here's an example:
```
vmrun -T fusion suspend  "/Volumes/Virtual Machines/Windows 11 ARM 25H2 preview.vmwarevm/Win 11 ARM.vmx" Encrypted virtual machine password: %
```
Note that you don't get a prompt that anything happened. Re-run the command in step 1 to verify that the VM has indeed suspended.
Now start VMware Fusion. You may be prompted for the password of your Windows VM. Provide it if asked.
You should now see the VM's full screen window appear. You should be able to resume the VM from this point by clicking in the window.

I wonder if the issue appears because the Fusion GUI is terminated by something during the sleep process, and that termination may be related to managing the VM in full screen mode.

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

Original Message:
Sent: Sep 17, 2025 12:08 PM
From: Technogeezer
Subject: Fusion 13.6.4 issues with macOS Tahoe

I've been able to reproduce this. I think I have a workaround that doesn't depend on manually killing the vmx process or rebooting. It involves using the vmrun command to identify and suspend the VM. Then you should be able to fire up the Fusion GUI and resume the VM.

I was able to get around this. I'll post more details when I'm able.

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

Original Message:
Sent: Sep 17, 2025 10:10 AM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe

Hi Paul,

Interesting and in the very far past I have seen sleep related issues too, but nothing like this, and I believe the symptom to be different.

I'll keep monitoring my setup. I am running with the MBP plugged into an external display - an Apple Studio Display - and it may be that this is in some way part of the mix. I say that because I have had issues in the past with sleeping which only occur when an external display is present and the MBP running in clamshell mode. That configuration seems to be a bit of an achilles heel for Fusion.

It seems to be very repeatable. I've had this problem occur three times today before posting.

Original Message:
Sent: 9/17/2025 9:57:00 AM
From: Technogeezer
Subject: RE: Fusion 13.6.4 issues with macOS Tahoe

I wonder if this is new behavior with Tahoe or some old behavior that may or may not be getting worse.

There have been reports of Fusion having issues with the host sleeping while VMs are running. See https://community.broadcom.com/vmware-cloud-foundation/communities/community-home/digestviewer/viewthread?MessageKey=e0e689a0-d2bf-4a6f-9d7e-ddd348e527e0&CommunityKey=0c3a2021-5113-4ad1-af9e-018f5da40bc0

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

Original Message:
Sent: Sep 17, 2025 09:39 AM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe

Fusion seems to be impacted be a serious bug in relation to Tahoe and sleep.

When my host MBP goes to sleep with Fusion running a Windows 11 ARM guest, on waking from sleep the whole Fusion app seems to be degraded. I am unable to view any Fusion window, including the VM Library or the guest. The guest is still running, as far as I can tell, but its window is not visible any more within macOS.

Quitting the Fusion app and restarting it doesn't solve the problem. On restart, Fusion will then display its VM Library window but doesn't seem to be able to reconnect with the still running guest, nor control it.

Shutting down the host clears the issue, obviously. Another less inconvenient workaround is to quite the Fusion app and then search for 'vm' in the Activity Monitor to find the guest virtual machine, and then quit that. After this Fusion can be restarted, the guest rebooted, and operation resumes.

Obviously killing the guest vm like this is far from ideal.

This bug makes working in Fusion almost impossible. If I walk away from my machine for any time, I need to suspect/shutdown the guest before walking away, in case my MBP goes to sleep.

-------------------------------------------

16. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

External Moderator

Technogeezer

Posted Sep 19, 2025 09:22 AM

From what I remember as a long time Fusion user, VMware rarely had "day-one" support for a new macOS major version.

It's a fair point, though, that many software vendors work with beta versions in order to announce that day one support. But that does not guarantee that the shipping product is free of bugs on the new macOS version. The industry is littered with software that worked fine in beta versions that suddenly stoped working in the released version due to last minute changes.

broadcom's shift to making the desktop hypervisor products free of charge is a both good and bad for us Yes, we no longer have to pay for Fusion.. But with no revenue for Fusion, it brings into question how much resource they're going to allocate to provide timely attention to the product. I for one would like the option to purchase support (open source vendors seem to have figured this out - free license, paid support) for the product to fund development and more timely bug fixes

An audio proceinng utility I use just released their Tahoe-compatible update. It's not bug free though - they list 2 known annoying bugs (with workarounds) impacting their product that they've reported to Apple and are awaiting fixes.

My guess is that you won't see any update in "a few more days". It's also entirely possible that this is an Apple problem introduced in Tahoe as this did not happen in Sequoia. In which case, we could be looking at an Apple fix

if one depends on any computer system for a living, it may be a good idea to wait until the software you use announces support for Tahoe. Early adopters always risk having problems.

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

Original Message

Original Message:
Sent: Sep 19, 2025 02:01 AM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe

Thanks Paul, for your efforts on this. Hopefully your back-channel will prove fruitful.

i think this might be the final straw for me if Broadcom don't recognise the severity of this situation and produce a quick fix. I've been with vmware products for years and I will be sad to go but as a business user I need tools that i can depend on. So far I have stuck with Fusion despite all the recent corporate changes but I really can now feel that I am using unsupported software.

We should not expect Broadcom to test Fusion in advance of new OS releases nor produce rapid bug fixes, or even fixes at all, if the product is unsupported, which seems to effectively be the case. But I do have that need so I guess I'm using the wrong product. A well known competitor product has full compatibility with Tahoe and full support. It's a paid product but then I was always a paying customer of Fusion.

I'll give it a few more days and see what transpires, but it might be time to pull the trigger.

Original Message:
Sent: Sep 18, 2025 09:37 PM
From: Technogeezer
Subject: Fusion 13.6.4 issues with macOS Tahoe

There is no other place to report Fusion bugs other than this forum. We can only hope that Broadcom will take note of bugs reported here and fix them in future versions of the product

Again, remember that Fusion running on Tahoe is an unqualified/untested configuration (I hate to use the term "unsupported" because Broadcom no longer provides technical support for Fusion). Since it hasn't been subjected to any official testing, it's likely that problems exist on Tahoe that weren't seen on Sequoia.

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

Original Message:
Sent: Sep 18, 2025 08:48 PM
From: kazuyoshi tomita
Subject: Fusion 13.6.4 issues with macOS Tahoe

I'm having the same issue too.

My environment:

- Mac Studio 2023 (M2 Max)

- Tahoe 26.0

- VMware Fusion: 13.6.4

According to the vmware-vmfusion.log, a segmentation fault appears to occur when resuming macOS.

==============

2025-09-19T00:02:41.602Z In(05) VMware Fusion IsTopologySupported: Topology: 1729x921 @ 0,0.

2025-09-19T00:02:41.602Z In(05) VMware Fusion IsTopologySupported: Guest screen size limit: 8192x8192, 10 displays max, bounding box memory limit: 268435456 bytes.

2025-09-19T00:02:41Z[+0.000] Wa(03) VMware Fusion Caught signal 11 -- tid 351631 (addr 500003640)

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SIGNAL: pc 0x183266394 sp 0x16dc729b0

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SIGNAL: x0 0x14ddd0000 x1 0x500003640 x2 0x1865848 x3 0x14ddd0020

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x4 0x3b2233640 x5 0x0 x6 0x0 x7 0x0

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x8 0x3640 x9 0x731 x10 0x3608 x11 0x4

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x12 0x4 x13 0x0 x14 0xffffffffffffffff x15 0x3

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x16 0x183266360 x17 0x1f123cd70 x18 0x0 x19 0x8806a21e0

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x20 0x4 x21 0xd82 x22 0x732 x23 0x8829e05d0

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x24 0x1e9841000 x25 0x180 x26 0x16dc72dd0 x27 0x180

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion x28 0x0 x29 0x16dc72a80 x30 0x1885ffa88

<snip>

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[0] rip=000000010514c260 in function Util_BacktraceWithFunc in object /Applications/VMware Fusion.app/Contents/Frameworks/libvmwarebase.dylib loaded at 0000000104e68000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[1] rip=0000000104fdb530 in function Sig_Init in object /Applications/VMware Fusion.app/Contents/Frameworks/libvmwarebase.dylib loaded at 0000000104e68000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[2] rip=0000000183266744 in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 0000000183263000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[3] rip=00000001885ffa88 in function -[NSSoftwareSurface frontBuffer] in object /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit loaded at 00000001876c9000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[4] rip=00000001885fe510 in function -[NSCGLSurface flushRect:] in object /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit loaded at 00000001876c9000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[5] rip=00000001885fe260 in function NSCGLSurfaceFlush in object /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit loaded at 00000001876c9000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[6] rip=00000001e816ce40 in function glSwap_Exec in object /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine loaded at 00000001e8153000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[7] rip=00000001e7f766f8 in function CGLFlushDrawable in object /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL loaded at 00000001e7f69000

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion SymBacktrace[8] rip=000000018781ce68 in function -[NSOpenGLContext flushBuffer] in object /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit loaded at 00000001876c9000

<snip>

2025-09-19T00:02:41Z[+0.000] Wa(03)+ VMware Fusion The core dump limit is set to ZERO; no core dump should be expected

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion Msg_Post: Error

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (VMware Fusion)

2025-09-19T00:02:41Z[+0.000] In(05)+ VMware Fusion Unexpected signal: 11.

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion [msg.panic.haveLog] A log file is available in "/Users/tomita/Library/Logs/VMware Fusion/vmware-vmfusion.log".

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion [msg.panic.requestSupport.withoutLog] You can request support.

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion [msg.panic.requestSupport.vmSupport.apple.menu]

2025-09-19T00:02:41Z[+0.000] In(05)+ VMware Fusion To collect data to submit to VMware support, choose "Collect Support Information" from the "Help" menu.

2025-09-19T00:02:41Z[+0.000] In(05)+ VMware Fusion You can also run "VMware Fusion Problem Reporter.tool" inside the VMware Fusion application bundle directly.

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion [msg.panic.response] We will respond on the basis of your support entitlement.

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion ----------------------------------------

2025-09-19T00:02:41Z[+0.000] In(05) VMware Fusion Exiting

==============

Is there a place where I can report this?

Original Message:
Sent: Sep 17, 2025 09:39 AM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe

Fusion seems to be impacted be a serious bug in relation to Tahoe and sleep.

When my host MBP goes to sleep with Fusion running a Windows 11 ARM guest, on waking from sleep the whole Fusion app seems to be degraded. I am unable to view any Fusion window, including the VM Library or the guest. The guest is still running, as far as I can tell, but its window is not visible any more within macOS.

Quitting the Fusion app and restarting it doesn't solve the problem. On restart, Fusion will then display its VM Library window but doesn't seem to be able to reconnect with the still running guest, nor control it.

Shutting down the host clears the issue, obviously. Another less inconvenient workaround is to quite the Fusion app and then search for 'vm' in the Activity Monitor to find the guest virtual machine, and then quit that. After this Fusion can be restarted, the guest rebooted, and operation resumes.

Obviously killing the guest vm like this is far from ideal.

This bug makes working in Fusion almost impossible. If I walk away from my machine for any time, I need to suspect/shutdown the guest before walking away, in case my MBP goes to sleep.

-------------------------------------------

17. RE: Fusion 13.6.4 issues with macOS Tahoe

Recommend

Bigdave1357

Posted Sep 19, 2025 09:32 AM

Good points, as always.

However, business pressures, particularly in development, don’t always allow for developers to hold off using new versions of software. I for one work an in an environment where complex toolchain dependencies mean that I’m more or less forced to update to newer versions of code within a few days of them being publish. The knock-on effect of not doing this can lead to other issues with other toolchains.

I think the main issue here is that the Fusion products is not receiving anything like the support, if any, that it should for it to be considered “business class”. Like you I would pay for a supported product, and did in the past. But that’s not on offer. So if nothing materialises in the short term from Broadcom, I think it will be goodnight from me, and hello to Parallels.

Original Message

Original Message:
Sent: 9/19/2025 9:22:00 AM
From: Technogeezer
Subject: RE: Fusion 13.6.4 issues with macOS Tahoe

From what I remember as a long time Fusion user, VMware rarely had "day-one" support for a new macOS major version.

It's a fair point, though, that many software vendors work with beta versions in order to announce that day one support. But that does not guarantee that the shipping product is free of bugs on the new macOS version. The industry is littered with software that worked fine in beta versions that suddenly stoped working in the released version due to last minute changes.

broadcom's shift to making the desktop hypervisor products free of charge is a both good and bad for us Yes, we no longer have to pay for Fusion.. But with no revenue for Fusion, it brings into question how much resource they're going to allocate to provide timely attention to the product. I for one would like the option to purchase support (open source vendors seem to have figured this out - free license, paid support) for the product to fund development and more timely bug fixes

An audio proceinng utility I use just released their Tahoe-compatible update. It's not bug free though - they list 2 known annoying bugs (with workarounds) impacting their product that they've reported to Apple and are awaiting fixes.

My guess is that you won't see any update in "a few more days". It's also entirely possible that this is an Apple problem introduced in Tahoe as this did not happen in Sequoia. In which case, we could be looking at an Apple fix

if one depends on any computer system for a living, it may be a good idea to wait until the software you use announces support for Tahoe. Early adopters always risk having problems.

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

Original Message:
Sent: Sep 19, 2025 02:01 AM
From: Bigdave1357
Subject: Fusion 13.6.4 issues with macOS Tahoe