Fusion wont run on Microsoft Surface Pro 5 anymore after update

[Harold_Weistra]

So, I used to run Fusion on my Microsoft Surface Pro 5 whenever I was on the road without my Zbook. Until it updated yesterday and now even wont start anymore but once, stating the videocard was inadequate.

I know it isn't the recommended hardware (i5, 8gb ram internal HP video) but it ran smoothly until now. So do AutoCAD and Inventor for that matter. So what has happened?

Tried to uninstall, clean, reinstall. No joy at all.

Any tips on how to get things up and running again?

Cheers,

Harold

[slickmilwaukee]

Hi @Harold_Weistra,

Would you happen to be on the Windows Insider program? If so, there is/was a bug in there that will render your F360 useless. I went down so many rabbit holes to try and find the solution I just gave up. There are many threads on this issue, and I don't believe any of them has a working solution available.

If you can look in your Windows updates and then try and uninstall whatever happened, OR if you are lucky enough to have a system restore point set, now's the time to use that.

[Harold_Weistra]

Hi @slickmilwaukee,

Thanks for responding! Not sure if it's the Windows update. I'm not on the insider program. And it happened after the Fusion Update. Not the Windows update. I just get a blank screen with the viewcube. Thats it. Think it's the video driver somehow....

Cheers,

harold

[Harold_Weistra]

It seems that @tomas.fober has a workaround that seems to solve my issue as well:

Windows OS

1. (Close Fusion 360) In windows explorer browse to  %localappdata%\autodesk\web services

2. In the Web Services directory, right lick on the Login State.xml file and select delete

3. Restart Fusion 360

Windows

1. Browse to %appdata%\autodesk\neutron platform\options\{alphanumeric folder name}.
2. Delete NGlobalOptions.xml.
3. Browse to %appdata%\autodesk\neutron platform\options
4. Delete NMachineSpecificOptions.xml
5. Browse to %temp%\autodesk\
6. Delete the BrowserCache folder.

Seems to be working for now. Also after a reboot. Will try again tomorrow.