Windows 10 - 1703 update - Crashes C3D

[rkmcswain]

Anyone else running Win 10, get the 1703 update and then Civil 3D fails to launch?

Got a few of these, but it's very inconsistent. Some machines seem unaffected, others won't launch Civil 3D 2017 (or 2014) after this update -- UNTIL we launch it 3, 4, or maybe 5 times - then all of a sudden it starts working fine. A couple of users have reported that after a cold boot (i.e.: Monday, after being off all weekend) - that the same process repeats. They have to launch and crash it 3-5 times before it will launch and remain fairly stable.

I found this, but not sure it's exactly this problem. Not to mention the "solutions" sound like they are basically guessing. Those are 4 pretty broad, major things to "try one or more of the following". And.... if you do "solution" 3 or 4, then what is the point in doing 1 or 2?

[chriscowgill7373]

There are some random issues being caused by the .net framework 4.7 that comes with 1703, but it is very sporadic.

[CADmgrMike]

Rk,

I have a user with 1703 and the C3D dialog boxes are very laggy in displaying information.

For example, if you bring up the alignment properties box, it will be mostly blank until you move the dialog box. Then it will populate.

Best I can tell, his pc is exactly the same as mine except for this update.

Are you seeing anything like this too?

I have another user with Windows version 1607 and it isn't quite as bad, but does happen occasionally.

I'm running version 1511 and don't experience these issues.

[rkmcswain]

@CADmgrMike - I'm not saying that we are not experiencing those issues, but those have nothing to do with the main issue, which is --> about 30% of the time when you launch C3D it crashes - even before the graphics screen starts to load. We never get the Autodesk CER dialog. Windows catches the fault and kills the app.  

Like this:

We may have isolated a contributing factor to this, but I'm not ready to say what it is yet, without more testing.

Thanks.

[CADmgrMike]

Gotcha.

I should have mentioned this user is experiencing that particular issue also.

Trying to figure out if they are related.

[jmayo-EE]

I had a similar issue with win7 on 3 of 30 machines a few months ago. I was able to fix these 2 of these machines with the 'Reset Settings to Default' shortcut. The other I had to uninstall and reinstall .Net.