Cannot get Fusion to start

[mbostonsprint]

I have been trying to get Fusion to start on my office computer several times today, without success. The small title screen (about 5" x 7") appears, but the software never starts. I was using Fusion yesterday, and noticed it seemed to have more lag time than usual, but there was not an issue starting it up.

The computer system is a W7 PC with 16GB memory. I have been using this machine for Fusion work for several years without any difficulty.

Suggestions welcome --

[davebYYPCU]

W7.  There have been earlier threads mention - run in compatibility mode.  

There is an update phasing this week, correlation? Maybe.

Might help....

[Phil.E]

I'm assuming you've taken the usual first step and restarted the computer. 

If you could please gather the application log files, zip them together, and post back here it might show the problem. 

[mbostonsprint]

Thanks for the responses. Yes, I rebooted the computer to see if it was "just a glitch". No luck. I tried again this morning, same thing. Attached find the log file package, including new log file from today.

I was able to run Fusion from my home system, so the problem appears confined to this PC and whatever interaction is involved with this physical location, Autodesk, and whatever update may have occurred in the last 2-3 days. My home machine showed that there was a pending update, which will take effect on next startup. Remains to be seen what might happen there.

[Phil.E]

Hi,

It's hard to say from the log files, but they do eliminate most known cases.

It would be helpful to check the process while it is hung. There are instructions here:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/simplecontent/content/how-to-use...

For Fusion 360, the Process Monitor ‘filter’ should be :
 Process Name     is     Fusion360.exe

[mbostonsprint]

Thanks for the response. Just to clarify for me, do the log files indicate that communication IS occurring with Fusion servers(s), or does the boot-up cycle not get that far? I am trying to make sure that we don't have some modem/firewall issue on our end as a cause.

I will try the Process Monitor route and send more info. Thanks --

[Phil.E]

The log files (you can see it in the applog files from Sept 16-17), do connect to the servers. There is no indication of proxy, firewall, or av that we can see.

It might be related to file permissions. The process monitor should show that. 

Thanks for your patience.

[mbostonsprint]

OK, now it's working. No idea why, but I booted up the ProcMon app to see what it looked like, tried putting in a few parameters (apparently unsuccessfully for the purpose, haven't yet gone through the tutorial screencast), and re-booted Fusion, and Fusion started successfully. I guess that it thought it was being watched and should behave correctly.

After I get a handle on what the ProcMon software needs for setup, I'll see what it shows for what will apparently be "normal" operation. Will additional log files be useful for possible comparison, or is the possibility of file permissions not visible in any case in the logs?

[mbostonsprint]

Addendum:  I also rebooted Fusion without ProcMon running, and that also worked. I suspect something on the Autodesk end, but that's just the cynic in me.

[Phil.E]

Yes we were trying to see whether it was local or server related. No worries, if it happens again please let me know.

[mbostonsprint]

Hello, Phil --

You asked me to report additional instances of this behavior, so log file package is attached. The logs were downloaded using the Fusion tool, after I left the system trying to start up for some couple of hours. When I got back to my desk, it had started. I closed it, and it restarted normally as far as I could tell. I had tried a couple of times previously today to get it started without success, but it looks like it works if I have an hour and a half to spare for bootup.;-)

In any case, please see what can be gleaned and let me know if there is something I can do. I am going to do a detailed ProcMon process, assuming the software will continue to start, but I do not have any additional info from that right now. Thanks --

[Phil.E]

Sorry it took so long to get back.

The day you refer to is September 28. All the application logs from that day show Fusion was running normally, and the longest startup time recorded was about 80 seconds.

Are you continuing to see this behavior?

[mbostonsprint]

Hi --

I can't comment on the "max 80 second startup time", but as I noted, I did try a couple of times without success to start the software. One thing I will note is that Windows 7 Task Manager does not show that Fusion 360 is a running  (or non-responding) application while the title screen is displayed, prior to the actual functionality booting up. I don't have a clue how Fusion's diagnostics may (or may not) be riding on Windows' coattails, but I am certain about the lack of bootup in the earlier couple of trials.

[Phil.E]

I'm just going by what I can see. In the very last application log from September 28, Fusion begins to do normal things at 14:46:19 and finishes normally at 14:47:16.

If this is continuing to happen on every launch of Fusion please let me know.

[mbostonsprint]

Phil,

Thanks for the response. I have been seeing more consistent startup in the last few days, so The Issue (whatever it is) looks to be mitigated to an unknown extent. I have not yet had time to do a real Process Monitor analysis, so that remains as a possibility to find additional nuggets. Generally, if it is working, I need to use it; if not, I move to something else that fell off the plate....

I'll let you know if/when I have ProcMon results to share. Thanks again --

[Phil.E]

Thanks.

If the problem comes and goes, that actually eliminates a bunch of stuff this could be. The things that vary: design size, what hub you are logged into, your internet provider, or some temporary condition on the machine*.

*years ago now, met a customer once with a habit of having 100+ chrome tabs open, Intel graphics, and very little RAM on the machine. I only finally noticed it in one of their videos, and it was crushing performance on that machine for Fusion. (only pointing out how these variables play out in strange ways)

[Phil.E]

I sent you a PM.