Checking Your AutoCAD Graphics

seen on Tom’s blog – Without a Net

Every year AutoCAD configurations get more complex.
For example, one large jump in complexity happened in AutoCAD 2007 when we introduced Hardware acceleration.
Prior to AutoCAD 2007 we only had a dependency on the operating system, but since then we have also become more dependent on graphics cards and drivers. Each new level of dependency brings new potential for interoperability issues.

AutoCAD Crashes Caused by Old Adobe Flash Player

seen on Tom’s blog – Without a Net

Autodesk has been receiving reports of crashes in a variety of Autodesk products ( and versions ) while using the help system or while viewing videos ( such as in the New Feature Workshop ). Audesk has traced the source of these crashes and found them to be caused by having an older version (or corrupted installation) of the Adobe Flash Player on user systems.

In these cases, uninstalling the older version of Flash and then reinstalling a current version from the Adobe website should address the problem.

AutoCAD Crash Caused by Odd Registry Value

seen on Tom’s blog – Without a Net

In the past, we’ve seen issues where you would launch AutoCAD and it would immediately close with a Customer Error Report ( CER ) dialog and possibly the message:
This version of AutoCAD was not installed properly and some features may not run correctly. You should reinstall AutoCAD immediately to make sure all features are working properly. Do you wish to continue anyway?
This often points to a corruption in the .NET Framework but we recently discovered a cause that was a bit more unusual.

It turns out that one source for this kind of crash stems from a bad registry entry in the HKEY_CLASSES_ROOT.png key. There have been user-reported cases where the value in the Content Type key contains a leading space:

In cases where someone had that leading space in the value, simply removing it resolved the crash.