Fusion hangs on start-up, tried all published recommendations

[robert.manna]

Windows 11 computer. Fusion previously worked fine, last used it in December. Went to use it again yesterday and I get the splash screen, then the actual UI loads (mostly, but not fully) then I get the spinning wheel of death that goes nowhere. Finally, just have to force quite the app. Have tried the majority of Autodesk's published recommendations. The only thing I'm not 100% certain is if the graphics drivers are 100% up to date, but I'm not getting prompted by Windows. I've tried deleting various settings files, reset via the Fusion utility and un-install and re-install (several times). I have not attempted a 'deep clean' manual uninstall as I'd like to not delete some of the 'shared' settings/files that are used by other Autodesk Apps.

I have another computer (my laptop) which opens Fusion and my design files just fine, however for I think obvious reasons I'd prefer to work on the desktop that has more horsepower.

Any suggestions would be greatly appreciated.

[RajkumarIlanchelian · Accepted solution]

@robert.manna Can you confirm if you have multiple monitors and if so does disconnecting it help?

[robert.manna]

@RajkumarIlanchelian I do have multiple displays and will note that Fusion was not attempting to start on the 'primary' display from an OS perspective.

I did as you suggested and disconnected my two other monitors and Fusion started up completely on the single (primary) monitor.

I did a quick test, and with Fusion 'reset' to the primary screen and the two additional displays connected, Fusion did properly start. Where does this leave me; clearly the issue was that Fusion was attempting to start on a 'secondary' display and not the primary, but are there any steps I should take, or something else I should address to avoid the issue in the future? 

[RajkumarIlanchelian]

@robert.manna @It seems like either a screen resolution or some variable is playing a role when Fusion is closed on another monitor. 

I have posted a link below where I have asked in another thread for some detail. Would you be able to provide this for us? 

https://forums.autodesk.com/t5/fusion-360-support/fusion-won-t-run-even-after-fresh-install/m-p/1248...

[robert.manna]

@RajkumarIlanchelian yes, I should be able to generate the DMP file per the other thread. Will get to it sometime in the next couple of days. I will note that all of my monitors are running at 2560x1440 with 100% scale. They are effectively identical in terms of the screen, slight variation on models in terms of extra USB ports and such.

Running a Nvidia GeForce RTX 2070.

[RajkumarIlanchelian]

@robert.manna Thank you for the information about the monitors. Having your process explorer files would certainly help us get more information on what could be a potential problem here. 

[RajkumarIlanchelian · Accepted solution]

@robert.manna Thank you for providing the dump files. Our engineering team was able to quickly look into this and found out where the hang is happening. It is the Nahimic Audio dlls that are causing these issues. Can you let us know if any of these solutions works for you? 

this is in fact causing a problem here are some potential ways to solve it:

1. Run services.msc and stop the Nahimic service, and set it to manual start.
2. Disable the onboard audio through the BIOS settings.
3. Update or uninstall the Manufacturer's audio drivers, not sure if this will say Nahimic.

Here is a web article that seems to describe a similar issue:

https://chieftalk.chiefarchitect.com/topic/28384-multi-monitor-issue-fix-for-computers-with-nahimic-...

[robert.manna]

@RajkumarIlanchelian thanks! Those tips helped, adding Fusion to the blacklist.dat file mentioned in the forum post you highlighted resolved the issue. This also explains a warning I was getting with BambuStudio, that warned about using it on a secondary monitor, so I had explicitly avoided using it on another monitor.

[RajkumarIlanchelian]

@robert.manna Thank you once again for confirming the suggestion worked and more importantly thank you again for providing the process explorer dump files. This helped us get to the root of the problem.