Latest update causing launch problems on Mac

[bentwookie]

Fusion 2701.1.18 arm64 [Native]
Active Plan: Subscription
macOS 13.7.8 (22H730) on MacBookPro18,1

After the latest update, I'm finding that loading Fusion on my Mac takes forever and then pops a dialog with these logs: 

Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAMUI10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/CAMXLayer10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAMUI10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilderUI10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/local/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib

It eventually launches. I tried using the service tool to repair, but it didn't fix the problem. I guess I'll try reinstalling. 

[f360CHFH6]

If you didn't update yet, don't do it.
It's really bug with

Fusion 2701.1.18 x86_64 [Native] for Mac, but Autodesk team try to say - it's not.

[f360CHFH6]

It's look like that you close the ticket... it's not closed. Check updates on the topic, please

It's really can't work that way, as developers just not say before use about restrictions at lowest OS version, that could be updated.

And by the way, Tahoe version of Mac OS is the latest.
But in this topic the problem is also happened with newest versions of MacOS in comparison with your software.

You keep think, that solved problem.... but just keep skip it

[janT7C52]

---

@f360CHFH6 wrote:

If you didn't update yet, don't do it.
It's really bug with

Fusion 2701.1.18 x86_64 [Native] for Mac, but Autodesk team try to say - it's not.

---

Just out of curiosity (I’m no Fusion expert—more of a beginner who’s gradually getting the hang of it)... is it even possible to skip the update and keep using the older version? As far as I remember, a message always popped up telling me there is a new version - and I didn’t have to update right away, but that it HAD to be done within a few days. So I’m not sure if it’s even possible to say... "OK, this older version is fine for me... I don’t want the new one". (Maybe I just misunderstood the message meaning??)

Thanks in advance for the clarification...

[2364455]

What if I cannot update to Sonoma?

[jeroenK4BJ7]

Same problem here. Pleas fix this!  

[ninjadub]

hi i have the same problem on my mac im running ventura and can not update my mac to the sonoma as my mac is to old this is the log i get

thanks

Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAMUI10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/CAMXLayer10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAMUI10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilderUI10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaMachineBuilder10.dylib
Error: Could not load the addin in /Users/mark/Library/Application Support/Autodesk/webdeploy/production/d33deb94f63c0f9e07daa3f1ea6a07e40d838e5e/Autodesk Fusion.app/Contents/Libraries/Applications/CAM360/NaNeuCAM10.dylib

[g_grieble]

same issue guess we are all screwed and time to move to a different cad program

[cjcorney]

I have the same issue. (And more) 

The issue is definitely not due to macOS version, it appears to be a hobbyist issue for me. (Obviously no support available to hobbyists) because I have set up a new autodesk account with a different email, and started a free trial of the paid version - everything works perfectly on this login on my macOS Monterey on 2016 macbook pro

I also can't start a new design or open a previous design without fusion crashing.

Before the update everything was still working perfectly, so we know that fusion can work great on old machines - why bother forcing updates? Just let users on old machines use outdated software that don't want new features and only use the simplest of tools... 

So far I have tried the service utility to reset, repair, then I tried uninstalling and reinstalling from a fresh downloader. Then I tried manually uninstalling and reinstalling fresh again. Still the same issues.

Every time I get a fusion error report I send it to them so I hope they fix the bug or whatever it is. 

[f360CHFH6]

I can't check it after update without extra efforts. Maybe someone, who didn't update it yet can confirm or deny it.

The only way for me, try to restore from Time Machine backup. At least I think about it. But I don't want to do full restore for just the Fusion. So only can try to restore by files in all paths of the Fusion installation.

[cjcorney]

That's a good suggestion about time machine backups -  but like you say - I have done so much more with my macbook since then that I don't fancy rewinding to a previous day with risk of losing my new files etc

I checked the filepaths in the errors above, and the files were all there in my most recent update - but I think Fusion is not able to read/process the files to load the CAM360 properly... 

But I was still able to use fusion while these errors happened - however now - it has stopped working entirely for me - crashing instantly when I try load a file or start a new file... (Nothing to do with CAM360 errors) 

I have surrendered  - and bought a mac mini M4 ... hopefully it will work on that once I get it! ( I will be sad to see my trusty/reliable and still very capable macbook go to waste now though because of one software issue with Fusion)

[lordikipe]

Apparently there is no solution to the problem?

[cjcorney]

The solution for me was to buy a new computer

[vjcubas]

I'm running Autodesk Fusion on a MacBook Pro 16-inch, Nov 2024, Apple M4 Max, 64 GB RAM, macOS Tahoe 26.3.1, and Fusion continues to fail during startup with repeated initialization/loading errors.

This is not a hardware limitation. This is a current-generation, high-end Apple Silicon machine with more than enough resources to run Fusion. The problem has been ongoing for a while, and the usual generic troubleshooting guidance is no longer sufficient.

We need Autodesk to provide a real solution, not another round of basic steps such as reinstalling, rebooting, clearing cache, or checking system requirements. Please escalate this to the appropriate Fusion engineering/support team and provide a clear path to resolution.

Specifically, I need Autodesk to help with:

1. Identifying the root cause of the startup/initialization failures shown in the attached screenshots.
2. Confirming whether Fusion is fully supported and validated on macOS Tahoe 26.3.1 with Apple M4 Max hardware.
3. Providing any required hotfix, workaround, configuration change, or known issue reference.
4. Reviewing the relevant Fusion logs and advising exactly what needs to be corrected.
5. Confirming whether this is a compatibility issue, corrupted local Fusion state, cloud/service dependency issue, licensing/session issue, or application defect.

This is impacting my ability to use Fusion reliably. Given the hardware and software environment, this should not be happening, and I need a concrete technical response from Autodesk rather than generic support recycling.

Please escalate this case and provide the next actionable steps, including any logs or diagnostics you need from me.

FYI:

- MacBook Pro 16-inch, Nov 2024
- Apple M4 Max
- 64 GB RAM
- macOS Tahoe 26.3.1
- Fusion webdeploy production build: 2448aa8b3276a952725a8bb01f628b797da18a2a

...and still getting...

Thanks

[vjcubas]

After installing the latest upgrade, here is what I ended up with:

I am seeing repeated Autodesk Fusion startup failures on a current-generation MacBook Pro:

- MacBook Pro 16-inch, Nov 2024
- Apple M4 Max
- 64 GB RAM
- macOS Tahoe 26.3.1
- Fusion webdeploy production build: 2448aa8b3276a952725a8bb01f628b797da18a2a

Fusion repeatedly reports that it cannot load multiple internal Simulation add-ins from the installed app bundle, including:

- SimVTKExt10.dylib
- SimPostProcessing10.dylib
- SimFEACSObjects10.dylib
- SimLinearAnalysisController10.dylib
- SimPostProcessingUI10.dylib
- SimDesignVariations10.dylib
- SimLinearStaticStress10.dylib
- SimThermalTransient10.dylib
- SimThermalSteady10.dylib
- SimThermalStress10.dylib
- SimFluidDynamics10.dylib

This appears to be a systemic Simulation subsystem load failure, not a single user add-in issue.

I performed additional diagnostics on:

Autodesk Fusion.app/Contents/Libraries/Applications/Simulation/SimVTKExt10.dylib

Findings:

1. SimVTKExt10.dylib exists.
2. File permissions appear normal.
3. It is a universal Mach-O binary with both x86_64 and arm64 slices.
4. It passes code-signing validation.
5. It does not appear to be blocked by a quarantine attribute.
6. The main Fusion executable includes the expected runtime paths:
- @executable_path/../Frameworks
- @executable_path/../Libraries

However, otool -L shows that SimVTKExt10.dylib references VTK dependencies using names such as:

- @rpath/VTK/libvtkCommonCore-7.1.dylib
- @rpath/VTK/libvtkIOXMLParser-7.1.dylib

The installed Fusion bundle does not contain those exact filenames anywhere. Instead, the bundle contains the corresponding 7.1.1 files under:

Autodesk Fusion.app/Contents/Frameworks/VTK/

including:

- libvtkCommonCore-7.1.1.dylib
- libvtkIOXMLParser-7.1.1.dylib
- libvtkCommonDataModel-7.1.1.dylib

I searched the full app bundle and confirmed that the requested 7.1 filenames do not exist anywhere in the installed Fusion package. There are no apparent compatibility symlinks for the requested 7.1 names.

The 7.1.1 VTK libraries that I checked are valid on disk and satisfy their code-signing requirements.

Based on this evidence, the installed Fusion webdeploy package appears internally inconsistent: at least one Simulation binary is linked against VTK dependency names ending in 7.1, while the packaged VTK libraries available in the app bundle use 7.1.1 filenames/install names.

Because the startup log shows repeated failures across many Simulation add-ins, this appears to be a shared Simulation dependency/package issue rather than an isolated SimVTKExt10.dylib problem.

Please escalate this to Fusion engineering. I need Autodesk to confirm whether this is:

1. a known defect in webdeploy production build 2448aa8b3276a952725a8bb01f628b797da18a2a,
2. a corrupted or partial webdeploy update,
3. a macOS Tahoe 26.3.1 compatibility issue,
4. or an unsupported packaging/linkage mismatch between the Simulation add-ins and bundled VTK libraries.

Please provide the supported remediation procedure. I do not want to manually symlink, rename, or modify bundled .dylib files because that could alter the signed application bundle and create further supportability or signing issues.

This has now occurred during the last two Fusion upgrades I performed. The first time, the only way I was able to recover was to completely remove Fusion from my MacBook Pro and reinstall it from scratch.

That is not a reasonable long-term workaround for a paying customer. A full uninstall/reinstall after an upgrade is disruptive, time-consuming, and creates avoidable downtime. Fusion needs a reliable upgrade and repair path that preserves the local installation state without requiring customers to repeatedly remove and rebuild the application.

Please treat this as more than a one-time local installation issue. The repeated failure pattern across consecutive upgrades suggests there may be a persistent problem with the webdeploy upgrade process, package integrity validation, or dependency handling on macOS.

Thanks

[vjcubas]

## Fusion upgrades on macOS should not require uninstalling and reinstalling the entire application

I am posting this because this has now happened to me across multiple Autodesk Fusion upgrades, and the pattern is becoming hard to excuse.

After installing the latest Fusion upgrade on a current-generation MacBook Pro, Fusion started reporting repeated internal Simulation add-in load failures during startup.

My system:

- MacBook Pro 16-inch, Nov 2024
- Apple M4 Max
- 64 GB RAM
- macOS Tahoe 26.3.1
- Fusion webdeploy production build: 2448aa8b3276a952725a8bb01f628b797da18a2a

The startup failures involved multiple internal Fusion Simulation components, including:

- SimVTKExt10.dylib
- SimPostProcessing10.dylib
- SimFEACSObjects10.dylib
- SimLinearAnalysisController10.dylib
- SimPostProcessingUI10.dylib
- SimDesignVariations10.dylib
- SimLinearStaticStress10.dylib
- SimThermalTransient10.dylib
- SimThermalSteady10.dylib
- SimThermalStress10.dylib
- SimFluidDynamics10.dylib

This was not a third-party add-in problem. These are internal Fusion components inside the Autodesk application bundle.

I did some basic diagnostics before reinstalling. The affected .dylib files existed, had normal permissions, passed code-signing checks, were not quarantined, and appeared to contain the expected Apple Silicon and Intel slices.

However, at least one of the Simulation libraries referenced VTK dependencies using names ending in 7.1, such as:

- @rpath/VTK/libvtkCommonCore-7.1.dylib
- @rpath/VTK/libvtkIOXMLParser-7.1.dylib

But the installed Fusion bundle only contained the corresponding 7.1.1 libraries under:

Autodesk Fusion.app/Contents/Frameworks/VTK/

For example:

- libvtkCommonCore-7.1.1.dylib
- libvtkIOXMLParser-7.1.1.dylib
- libvtkCommonDataModel-7.1.1.dylib

I could not find the requested 7.1 filenames anywhere in the installed application bundle.

That strongly suggests that the installed webdeploy package was internally inconsistent, corrupted, partially updated, or missing compatibility links/install-name handling. Whatever the root cause is, the result is the same: Fusion upgraded itself into a broken state.

And here is the bigger problem: this is not the first time.

This has happened during the last two Fusion upgrades I performed. The first time, the only recovery path that worked was to completely remove Fusion from my Mac and reinstall it from scratch. This time, once again, I had to remove and reinstall the application to get back to a clean working state.

That is not a reliable upgrade process. That is uninstall/reinstall roulette with a CAD subscription attached.

For a paid professional tool, this is not acceptable. Fusion needs a dependable upgrade and repair mechanism on macOS. Users should not have to manually inspect dynamic libraries, hunt through app bundles, diagnose missing dependencies, or completely remove and reinstall the product after routine upgrades.

A clean reinstall may be an emergency workaround, but it should not be the practical upgrade strategy.

Autodesk should provide:

1. A proper repair option for Fusion installations on macOS.
2. Package integrity validation after webdeploy updates.
3. Clear detection and recovery for partial or inconsistent upgrades.
4. Better logging that identifies missing runtime dependencies directly.
5. A supported remediation path that does not require users to manually modify signed application bundles.
6. A public acknowledgement if specific webdeploy builds are known to have packaging or dependency issues.

I understand software is complicated. macOS signing, universal binaries, runtime paths, and bundled dependencies are not trivial. But that is exactly why the upgrade system needs to be rock-solid. This is core product infrastructure, not an optional nicety.

Shame on Autodesk for allowing Fusion upgrades to repeatedly put paying customers in a broken state where the only dependable fix is to remove and reinstall the whole application.

Please fix the upgrade process. Fusion users deserve better than this.

[maximeliron]

Telling people to uninstall reinstall, or update to a slightly more recent version of Mac is simply lazy engineering.

I'll do it, but too often I'm confronted with the lackluster user experience standards of Autodesk. I guess that's what you get when competition is hard to come by.