Tag Archives: Patch

Autodesk has released an update to fix the following AutoCAD 2018 problem:

Product users of version 2018 Autodesk single-user subscriptions may experience an intermittent crash. The crash occurs when it has been more than 24 hours since the last successful authorization check and there is intermittent or no internet connection, or the licensing authorization server is unavailable. The licensing authorization check occurs in the background and is completely unrelated to activities the user is performing at the time of the crash.
A fatal error message may be shown by the product. For example:

FATAL ERROR: Unhandled e06d7363h Exception at ee563c58h

 
Links:

Note that this crash only afflicts subscription (rental) single-user (standalone) customers. People with perpetual licenses don’t have to put up with the multiple additional points of failure caused by the subscription licensing system insisting on phoning home every 30 days. Yes, even if you pay for three years’ subscription up front, you’ll still need a working Internet connection every 30 days if you want to keep using the product.

At least, Autodesk has been saying it’s only once every 30 days (as if that wasn’t bad enough). The information provided with this hotfix tells a different story. What is the license server doing phoning home 24 hours after the last successful authorization check? Enquiring minds want to know.

No criticism of Autodesk is implied for providing this hotfix. As always, I commend Autodesk for fixing up problems as they arise. The basis of my criticism is the hotfix being necessary in the first place. It’s caused by Autodesk inflicting unnecessary complication on its customers for its own internal reasons. This one fails the “how does this benefit the customer?” test big-time.

The single-user subscription licensing mechanism has been a crock from day one, especially for CAD Managers of multiple users who have to deal with its onerous requirements. It’s an astonishingly poor design, very badly implemented. Even with this particular crash fixed, it’s still a crock.

AutoCAD 2018.0.2 arrives

AutoCAD 2018.0.1 is dead, long live 2018.0.2!

Here’s the readme.
Here’s the 64-bit direct link.
Here’s the 32-bit direct link.

This supposedly fixes stuff that 2018.0.1 broke, such as the signed VLX thing. Will this one break other stuff? I guess we’ll find out.

AutoCAD 2018.0.1 mystery deepens with silent withdrawal

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information was later made available, but questions remained.

Now the update has been silently withdrawn. Go to Autodesk Account > Management > AutoCAD > Downloads > Updates & Add-ons and you will no longer see this:

The infamous Autodesk desktop app also shows no sign of this update. So why has it been withdrawn? Autodesk isn’t saying, but thanks to Jimmy Bergmark, we know that installing the 2018.0.1 update re-introduces a bug from AutoCAD 2016 (pre SP1) where signed VLX files don’t load. This means various 3rd party applications won’t load if the developers have done the Autodesk-recommended right thing by digitally signing their code.

If you’re a developer and want to test your code under the different versions, these direct links still work at the time of writing:

If you’re not sure whether or not you have 2018.0.1 installed, the About command will show you.

You can also check for this under program control by inspecting the system variable _VERNUM. In AutoCAD, it’s “O.49.0.0” before the patch and “O.61.0.0” after. I don’t know about LT, and I don’t know about the situation with verticals. Do they incorporate the 2018.0.1 fixes? How about the VLX bug? Should users who have applied this update uninstall it? Is this going to be done automatically or by Autodesk desktop app? How should users manually revert to the pre-2018.0.1 state if they need to load applications that use signed VLX files?

I think it’s fair to say that Autodesk’s management of this update has been a disaster. This is just one in a long line of AutoCAD update screw-ups going back decades. It proves comprehensively that continuous updates from Autodesk are a non-starter.

Autodesk can’t be trusted avoid breaking things with its updates. It can’t be trusted to effectively communicate about the updates. It can’t be trusted to provide fixes for its broken fixes. It can’t be trusted to provide an automated update mechanism that doesn’t hog your resources or one that works properly.

The AutoCAD 2018 install inflicts the execrable Autodesk desktop app on your systems without asking, which in itself is a betrayal of trust. I recommend you uninstall it immediately after all Autodesk installs. You will need to right-click the app tray icon and use the Exit option before you can uninstall it using Add or Remove Programs.

Autodesk needs your trust to make its continuous update idea work. Autodesk doesn’t have that trust. Autodesk doesn’t come close to deserving it.

AutoCAD 2018.0.1 mystery partially resolved but questions remain

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information is now available, but more questions have arisen.

If, like me, you don’t/won’t/can’t have Autodesk desktop app running on your systems, the only current official way to get at the download is using Autodesk Account (but read the whole of this post before you go there). That’s also how you get at information about the update. Go to Management > AutoCAD > Downloads > Updates & Add-ons. From there, it’s not obvious how to get the information, but it’s under More options.

From there, pick View Details. This will show you the following information (after you pick More):

As you can see, the severity is considered high. If you pick View release notes, you can see the readme, or you can go straight to it if you have this direct link. Here are the fixes described in the readme:

  • Occasional crashes when ending an AutoCAD session using specific API code no longer occur.
  • Publishing annotative multiline attributes no longer results in incorrect annotative scaling.
  • PFB fonts can now be compiled successfully as SHX files.
  • The border of a mask is no longer plotted in PDFs when “Lines Merge” is turned on.

Although it would be easy to have a go at Autodesk for shipping a product that needs fixing within hours of release, that wouldn’t be entirely fair. No software is flawless. Stuff happens, and the sooner fixes are provided to resolve that stuff, the better. So I commend Autodesk for getting this fix out quickly.

That doesn’t mean Autodesk is blameless, though. Read on.

First, the way the information about this update was (or wasn’t) disseminated was sub-optimal. It has required too much prodding and guesswork to get to the point we are now, and we’re still not where we should be.

Next, there’s scant information in the readme. I don’t see any documented way of including this fix in a deployment, for example. That means it’s not possible to create a one-step automated install without resorting to trickery.

Further, this update isn’t available on the main Autodesk site. It needs to be. Even if you know the version number to look for, a search at autodesk.com will come up blank:

Using the Autodesk Knowledge Network Download Finder won’t help, either:

Fortunately, these direct links appear to work:

This brings me to my fourth point of criticism. See that the 64-bit executable has “r2” on it? The one I downloaded on 23 March doesn’t. The 64-bit executables are similar in size to each other but the binary content is different. The 32-bit 2018.0.1 has a date of 22 March and the 64-bit 2018.0.1 r2 has a date of 24 March. So it looks like the patch has been patched, at least for 64-bit users.

Information on this patch-patch is non-existent. Should somebody who downloaded and applied the 64-bit 2018.0.1, download and apply 2018.0.1 r2? Will that work? Do they need to uninstall 2018.0.1 first? How should they do that? Will the 32-bit 2018.0.1 also be updated to r2? Should those users hang off a few days to avoid wasting time or go ahead with what’s there now?

Over to you, Autodesk.