Tag Archives: Continuous updates

Automated .NET 4.7 update kills AutoCAD pre 2017

Thanks to Robert Green for pointing this out:

Microsoft is installing .NET 4.7 as part of their auto updates and it is causing many legacy Autodesk applications to crash on any ribbon interaction. Touch the ribbon, away goes your software.

If you can keep from installing the 4.7 framework do so. If the damage is already done then uninstall .NET 4.7 and install .NET 4.6.2 using this download link. Note that the uninstall of the offending version must be done first!

AutoCAD 2013 to 2016 and Inventor are affected, and possibly other products. BricsCAD users are unaffected.

It is also reported that you can work around the problem by hacking the registry to identify an earlier .NET version as being installed (the usual caveats apply). That’s described in this Autodesk Knowledgebase article that works around a related but slightly different issue.

Don’t you just love the way continuous automated updates enhance and enrich the user experience?

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.

AutoCAD 2018 – there’s already an update

If you downloaded and installed AutoCAD 2018 yesterday and don’t/won’t/can’t have Autodesk desktop app running on your systems, you may already have another download to do, because AutoCAD 2018.0.1 is out.

At the time of writing there is no sign of this update on Autodesk’s main site, but you can get at it using Autodesk Account. Go to Management > AutoCAD > Downloads > Updates & Add-ons.

All that’s downloaded is an executable. No readme, nothing. There is currently no official information about the reasons behind this update, what it includes, what it might affect, how to include it in a deployment, etc. You’ll need to make up your own mind whether to install this update now or wait for information about it. I suggest the latter.

Of course, if you’re using desktop app and allowing automatic updates, you don’t need to worry about any of that that. Just trust Autodesk to not break anything and hope for the best.

What’s the worst that could happen?

Edit: see this post for further information.

Battle of the Bullshit part 2 – Autodesk’s sophistry

In my last post, I gave Bentley a well-deserved slap for, er, saying things that perhaps weren’t entirely factual. Now it’s Autodesk’s turn.

What’s this about? Carl White, Senior Director of Business Models at Autodesk, wrote a blog post Not so fast Bentley: Separating fact from fiction responding to statements made by Bentley in its press release Bentley Announces Autodesk License Upgrade Program. Some of Carl’s observations on Bentley’s claims were perfectly valid, but unfortunately he went beyond that and wrote a few more things – “facts” – where he’s on shakier ground. Let’s examine Carl’s interpretation of reality, shall we?

Fact #1 – No Autodesk customer ever  loses the right to use the perpetual software license you’ve purchased, it is “evergreen”.

This is generally true. There are exceptions (read the EULA), but let’s not split hairs. In the vast majority of cases, we don’t lose the right  to use the software. We can, however, lose the ability  to use the software. That loss is practically inevitable long-term because of the progress of technology. I have several old AutoCAD releases I can’t run for environmental reasons, not licensing ones. This means that if we want to use our licenses long-term, we rely on Autodesk’s ongoing cooperation. That’s where customers have legitimate concerns, because there are no guarantees that Autodesk will continue to provide that cooperation. If it does, there are no guarantees that cooperation will remain free or even affordable.

And if you’re on a software maintenance plan, you can continue to receive all of the benefits of software updates and technical support for as long as you’d like.

This has been officially promised, and let’s give Autodesk the benefit of the doubt and assume that this promise will be fulfilled to the letter. There’s still an elephant in the room. What will the benefits of updates and support cost us? Based on what Autodesk has done in recent years, it is a pretty safe bet that the cost of maintenance (formerly called Subscription) is going to rise, and rise sharply. Give it a few years and I expect maintenance customers will be paying the same as rental customers. I expect other strong-arm methods will be used to “encourage” people onto rental. When this happens, our perpetual licenses will be near worthless and Bentley’s claim about a “…write-off of the future value of their investment…” will become uncomfortably close to the truth.

We’ve shared key dates well ahead of time to give customers time needed to adjust, but that does not mean we’re taking away options.

The latter part of this statement goes beyond disingenuous; it’s arrant nonsense. Of course Autodesk is taking away options. Autodesk has been taking away options for years, and this has only accelerated. As of right now, I can no longer buy an Autodesk software perpetual license. I no longer have that option, which I had before. How is that not taking away options?

Fact #2 – Our customers have a choice. When you subscribe to Autodesk software, you have flexible terms (monthly, quarterly, annually), and multiple access points (single user, multi-user and shared). Now Autodesk customers can get the software they need for a year or a month, in ways that are more convenient and better for their business.

Well, I guess the first sentence is kind of true in a sense. Long-term customers (that’s most of us) do have the choice between paying merely a lot  more per annum for an Autodesk license via annual or multi-year rental, or paying vastly  more by doing it monthly. Suggesting this is better for our business is, of course, laughable.

Customers can buy and use it for as long as they want and can match their subscription type with the demands of their workforce. When the workforce expands, they can ramp up, or in quieter periods, they can scale it back. In short, subscribing gives you flexibility and predictability.

This is true; rental is  the best option for some customers under some circumstances. It is good that Autodesk has made that option available for the small minority of customers in that situation. However, it is the opposite of flexibility to make it the only  option.

When it comes to value, lower upfront costs make our software more accessible and allow you to try more tools without the risk of a large upfront expenditure. Plus, you only pay when you need it. This is a big deal. Some of our customers prefer this cost is considered an operating expense, allowing you to bill the cost of the software back to the client or project. And if you subscribe for a longer, multi-year term, you lock-in your rate. Combine that with flexibility in the length of contracts and you may find that you’re actually paying less.

Nice attempt at spin here, but ultimately it’s nonsense. Except for the minority of customers who need that level of flexibility, rental is not about paying less. If it was, Autodesk wouldn’t be doing this. Pushing Autodesk customers on to rental is all about trying to extract more  funds from us for the same thing, not less. Suggesting otherwise is disingenuous.

If rental really was  better value, Autodesk would give its customers the choice between perpetual and rental and let the market decide. But wait! Autodesk did exactly that a few years ago, and the market decided; the rental experiment failed miserably. Autodesk knows  it has to make rental compulsory because otherwise most customers wouldn’t go for it. Yet in a painful piece of patent paralogy, it paints this compulsion as a selfless act of customer service.

Fact #3 – Software as a service is essential for technological evolution. It allows for continual and consistent innovation and support. The software will get better, faster and more seamless in the way you use it. The experience is customized to you or your organization, and provides a simplified way to access and deploy software, manage your users and collaborate on projects. With this new way of delivering software, everyone will always have the latest, most up-to-date Autodesk tools available.

Even ignoring the conflation of software as a service (SaaS) and rental, the first sentence is breathtaking in its audacity. It goes beyond spin, beyond disingenuity, into the realms of the surreal. No, SaaS is not essential for technological evolution. The whole history of computing screams that loud and clear. Autodesk wouldn’t exist if the first sentence were true. It isn’t remotely close to true. To be generous, it’s a terminological inexactitude.

Reading beyond the first sentence, there’s a lot of wonderfully utopian wishful thinking that nobody familiar with Autodesk would believe for a second. It’s shown up for the other-worldly spin that it is by Autodesk’s years-long ongoing decline in maintenance value-for-money and its woeful attempts at trying to make continual updates work (which you probably don’t want anyway).

It’s not just Autodesk saying this; the entire software industry is moving in this direction. Frankly, design and engineering software has been a bit slow to make this change. But the benefits for end-users are clear, and it’s just a matter of time before all vendors have similar ways of buying.

While it’s true that various software companies are moving at least partly towards SaaS and rental of conventional software (some more successfully than others), it’s not at all a uniform industry-wide position. It’s disingenuous to imply that going all-rental is already almost universal and Autodesk is just catching up. As for the “benefits for end users” being clear, I guess all those customers who like paying lots more per year for their software will agree.

Yes, it’s likely that many vendors, maybe even most of them, will have similar ways of buying in the next few years. No, it won’t be all of them. No, not all vendors will make rental compulsory for new licenses as Autodesk has done. Some of Autodesk’s competitors (e.g. Bentley, Bricsys) will continue to provide their customers with the ability to purchase perpetual licenses. The law of give-the-customer-what-they-want-or-die tells me that those competitors are much more likely to thrive than Autodesk.

What does this mean? It means that millions of you are already seeing the benefits of shifting to subscription and are making that choice voluntarily.

Voluntarily? Really? I can’t imagine anyone typing that statement in that context without either wincing (if they have any self-respect) or laughing (if they don’t). Strewth!

So who won the Battle of the Bullshit? Nobody. First, Bentley lost. Then Autodesk put in a supreme effort, summoned up a steaming stack of sophistry, and lost more.

Raise your game, people; we’re not all stupid out here. If you can’t support your argument with the truth, then your argument isn’t a good one and you need to rethink it.

Hotfix for AutoCAD 2017 SP1 Autoloader bug

As reported earlier, AutoCAD 2017 SP1 breaks third-party add-ins that use the officially approved Autoloader mechanism. Autodesk is to be commended for acting quickly to produce a hotfix for this. In order to make this hotfix available quickly, Autodesk has taken the very unusual step of allowing a third party to distribute it. See this post from Jimmy Bergmark, who pointed out the bug in the first place. Kudos to whoever at Autodesk made the call to think outside the box to do this. It’s a very un-Autodesk Corporate thing to do, and particularly commendable for that very reason.

It’s important to note that because of the way Service Packs are now handled in AutoCAD and the vertical products based on it, this SP1 bug affects all of those products, not just base AutoCAD. Here is the list of affected products*:

  • AutoCAD 2017
  • AutoCAD Map 3D 2017
  • AutoCAD Civil 3D 2017
  • AutoCAD Mechanical 2017
  • AutoCAD Electrical 2017
  • AutoCAD Architecture 2017
  • AutoCAD MEP 2017
  • AutoCAD P&ID 2017
  • AutoCAD Plant 3D 2017
  • AutoCAD Utility Design 2017

*See links in comments below for further information about this.

Having heaped praise upon Autodesk for acting so quickly, it still needs to be said that Autodesk has done the wrong thing very quickly. Customers who go along with Autodesk’s continuous update push will see third party applications failing. The third party developers will be getting support requests from those customers and will have to persuade them a) that it’s Autodesk’s fault, and b) to go and deal with a manual hotfix that requires admin rights and requires copying/renaming things in Program Files. For customers without sufficient confidence to do that, or for whom just getting permission from IT to perform admin-rights operations is onerous, that’s pretty inconvenient.

It is wrong for Autodesk to offload the consequences of its incompetence onto its victims. Those customers and developers who have simply followed Autodesk’s direction and done nothing wrong deserve better than this.

What should have happened? SP1’s immediate withdrawal. It should be pulled now and reintroduced later (perhaps as SP1a) with this bug fixed. Given we’re only talking about one file, a week or two should do it. The hotfix should remain available for those customers who have already installed SP1, wish to keep it in place, and are happy to do the manual hotfix steps.

The lesson for customers and developers is not to blindly follow Autodesk’s direction. Make your own informed decisions about how you use, manage and develop for Autodesk products.

There are lessons here for Autodesk, too.

  1. Test stuff properly before releasing it. If serious bugs like this are discovered, delay the release until they’re fixed and retested.
  2. When you do screw up, fix it not only quickly but correctly. Don’t offload your problems onto your customers and developers; clean up your own mess.
  3. You’re not competent enough to do the automated continuous update thing. Your customers won’t trust you to do it, and they will be right. Give it up.

If item 2 above involves extra inconvenience and expense, so be it. It’s part of the cost of doing business; people pay a lot of money for Autodesk software, particularly if they’re forced to rent it. But doing item 1 right is actually cheaper and it means item 2 is much less likely to be relevant.

Will Autodesk learn from this? Unfortunately, I can’t be confident about that. I’ve seen too many such lessons unlearned or simply ignored over the years.

Microsoft demonstrates why automatic updates are a terrible idea. Listening, Autodesk?

I like Windows 10. After some investigation and with some trepidation, I have upgraded two Windows 7 computers and one Windows 8 (ugh) computer to Windows 10. In use, I’m generally very happy with it. It boots fast, works well and most of the more ridiculous aspects of the Windows 8 “let’s assume your computer is a phone” interface are gone. The fact that I can scroll windows using my mouse wheel without first clicking on those windows to obtain focus is a real productivity plus. I would be happy to recommend Windows 10 to all Windows 8 users and most Windows 7 users, dependant on individual needs. I would, but I’m not. Microsoft is entirely responsible for that reluctance; read on.

The one thing I really, really dislike about Windows is the way it pushes updates. With Windows 7 I was always selective about what updates I allowed through and when they were applied. Windows 10 doesn’t give you that choice. It downloads and applies its updates as it sees fit, regardless of the importance of those updates, my bandwidth and the level of inconvenience applying those updates might cause. Windows 10 Professional only allows you to defer updates until the next restart, and will nag you to restart until you give in.

This is bad enough, but the Home version just takes over your computer and updates and restarts whenever it feels like it. Yes, even if you are in the middle of doing something and have unsaved work, and the update process leaves your computer unusable for two hours. I wouldn’t have believed it if it hadn’t happened to a very computer-smart member of my own family. Quite astonishing levels of malicious arrogance from the utter wankers at Microsoft.

I know there can be some very important reasons for keeping your OS up to date, particularly as far as urgent security patches are concerned. But really, given the choice between a tiny chance of some unknown malicious action by some unknown party (that hasn’t yet happened to any computer I’ve been running in over 30 years) and a 100% chance of known multiple malicious actions by Microsoft, which would you pick? Problem is, I made my choice on those three computers a few months ago and now I’m stuck with it.

Microsoft’s arrogance has triggered a minor in-house rebellion; two of my other former Windows computers are now happily running Linux. Five years ago, 100% of the computers in my household were running Windows. Now the figure is 43%, and I’m not even counting handheld devices (that would make it 20%). I haven’t bought a new version of Office in many years. Yes, I know, Microsoft isn’t exactly quaking in its boots, but it makes me feel better to raise the digit in this way.

Various other people are holding back on Windows 10 for this and other reasons, despite the insistent placement of update icons and nag notices. Some of those nag notices have made the news for all the wrong reasons. Last month, many people found themselves updated to Windows 10 without their explicit consent and against their will because Microsoft changed the status of the Windows 10 update for Windows 7/8 users and employed other sneaky tricks.

To Microsoft: that’s a really, really abhorrent low-life scumbag way to behave. These are our computers, not yours. We’re the customers (the ones providing the money) and you’re just vendors (the ones who want our money). Get back in your box and stop behaving like dickheads. Your assholery has been a significant factor in your decline. Give it up, it’s bad for you.

If you’re a Windows 7 or 8 user who wants to stay that way, please don’t disable updates altogether, because that could leave you vulnerable. Instead, I suggest you check out the free utility GWX Control Panel. If it’s too late and you’ve been updated, here’s what you can do. You have a limited amount of time to roll back.

Autodesk wants your software to be updated like this, continually and automatically. This is a bad idea for a whole range of reasons that go beyond why it’s a bad idea for Microsoft to do it. I hope to expand on those reasons later, but this post is long enough already. Trust me, it’s a terrible idea.

Although right now Autodesk is doing a heart-warmingly poor job of implementing this concept, eventually it might get the technical details right and be in a position to force it on you. Fight it tooth and nail. Make your voice heard wherever you can, online and in person. Uninstall, disable or block any software that attempts to do this. Look for any utilities, tips, etc. that stand between your software and automatic updates, and spread that news far and wide. This is an important battle for control over our own property, so please don’t give up.

Navel gazing note: this is the 500th post published on this blog.