Fusion360 won't start on latest Windows 10 Insider build (19030)

[Anonymous]

OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19030 N/A Build 19030

Attempt to start program, it will freeze and never get to the splash screen. I'm available to grab whatever info you need from the process, since it doesn't die. It's just hanging.

[jevans3XST6]

Same problem here. Just adding my name to the list.

Funny, other Autodesk software works just fine.

[jsroques_web]

Here is a reply from @karina.harper here. So devs at Autodesk are aware of this.

So two solutions I guess : wait for a fix or revert / reinstall windows (as one can't usually revert to an old enough version)

[Anonymous]

Hopefully they post here when it's fixed so we know when to reinstall it,
because it's obviously not at a point where it's able to self-update right
now 🙂

[paultcook]

+1 19033.1

[alexandr_russkih]

+1 same issue

[peter.svensson]

+1 Same issue for me 😭

[CAD-CNC69]

Same here.  Very curious what actually broke, hoping Autodesk will provide some details.  We have a test machine that runs most of the pre-production builds, so as not to disrupt our workflow.  

[Anonymous]

+1 (win Version 10.0.19033.1) don't start

[slickmilwaukee]

I just got this response from Ryan Bales at Autodesk Tech Support:

We have been tracking this issue all week and its really starting to effect a lot of folks. We are doing our best to get a fix pushed to the development team but we do not have a timetable yet. 

Our best solution at this point in time is to try to roll back or reinstall a NON IP(Insider preview) version OR go back to a working IP version.

Looks like we're on our own for now.

[Anonymous]

Same for 19035.1 :S 

[familien_enholm]

yeah, was just about to write that, lot of time has passed, strange that autodesk haven't fixed this yet 😕

[ryan.bales]

---

@slickmilwaukee wrote:

I just got this response from Ryan Bales at Autodesk Tech Support:

We have been tracking this issue all week and its really starting to effect a lot of folks. We are doing our best to get a fix pushed to the development team but we do not have a timetable yet. 

Our best solution at this point in time is to try to roll back or reinstall a NON IP(Insider preview) version OR go back to a working IP version.

Looks like we're on our own for now.

---

Probably should chime in since i'm being quoted. What i mean by this:

We are doing our best to get a fix pushed to the development team but we do not have a timetable yet. 

Was that we are doing our best to push them to make a fix.  Sorry for the confusing wording @slickmilwaukee 

[Anonymous]

Gleiches Problem bis zum Windows 10 Insider build (19035)

[slickmilwaukee]

NO worries Ryan- We appreciate your efforts! I posted this because it seems to be literally the only communication on this issue here. Thanks again, and please keep us updated!

[ryan.bales]

I'm i'm totally fine being quoted - only wish i'd not fumbled my words 😂

[slickmilwaukee]

You didn't really, and I appreciate your honesty.

[skipperB6LS2]

+1 Have the same problem as well.

[oonicooo]

same here

[jlmccuan]

updated to 19035.1 and still have the same issue

[alexandr_russkih]

19037.1 without changes