Any chance that the original install for Revit is no longer available or has moved? Maybe the deployment on the server got moved, or you installed direct from the download and then deleted the folder in C:\Autodesk? Some updates expect to see the original install, and will stall with no meaningful info if they don't find it. And, R2/.X updates seem to do this more often than SP updates.

Gordon

enhanced Dynamo features?

Where's that documented?
Or are you talking about the Dynamo Player that came with 2017.1?

I am also having trouble installing 2017.2 ... maybe I'm missing something in the process.

I downloaded BDSP shortly after it was available, but did not install anything until this weekend. I downloaded 2017.2 via the subscription account. I was hoping I only needed to install the latest update, rather than having to go find all the earlier updates and installing them in order (particularly as they are not in the subscription updates to download), but 2017.2 will not install. Do I need to install these in order of issuance? Per the "Revit Builds/Updates & Product Support" thread, I don't, but it's not working. The error report refers to a "Beta" being installed, but I haven't ever installed a Beta version on this computer. I've included the error report for your reference.

Per the "About" information, I currently have Build 20160225_1515(x64) installed.

Any input would be appreciated.

Thank you!

Every year seems to be different, and I haven't tested every combination, but I have noticed a few things
1: Cumulative often means cumulative up to the subscription threshold. So, I would not be surprised if 2017.1 and later actually needs SP2 to install. And, often post R2/.1 updates need R2/.1 first. Or in this case .1.1 since .1 was a bag of hurt.
2 Even when ADSK specifically claims that an update is cumulative, I have seen situations where they are just wrong, and the update does have a prerequisite.

Because every update is a crap shoot, I long ago gave up. I install every update, every time, in order. 2017.1 being an exception, because it was so bug ridden I waited for 2017.1.1 and for new builds I just skip 2017.1. But usually I install everything. Or at very least everything that hasn't been deprecated. So yeah, for 2015 I install 16 updates. Every time I build a new 2015 machine.

As for the beta, I wonder if there is some extraneous stuff in the registry that is confusing the issue? In those cases Microsoft's FixIt tool is the first line of defense. Full uninstall and reinstall is the sad trombone second option. But that said, I would try installing SP1 & SP2 at least, before trying 2017.2.

Gordon

We had an issue where 2017.03 security fix got installed on some machines (it appeared in the Autodesk Desktop App) even though it wasn't intended for subscription customers) and 2017.1.1 wouldn't install over it (I had to uninstall 2017 entirely and manually remove the personal accelerator. Later on a different machine I was able to install 2017.2 without a problem (without 2017.1.1), so it might not be the cause of your problem

we encountered the same issue with 2017.03 security fix. It is no longer part of our SCCM task sequence.

Reason 297 why ADA is a steaming pile of **** and should be removed. It causes more harm than good. If it was just useless that's one thing, but actually screwing up like that? No thanks.

Yeah, I'm opting to leave 2017.03 out since we're on subscription. But I had to chase down Luke Johnson's links to get the rest. SP1 installed ok, SP2 is cranking now ... so far so good, other than my (lack of) patience. :laugh:

Ok, I downloaded the Microsoft FixIt tool. That fixed something and SP1 & SP2 appear to have installed fine (i.e. I could open Revit & the build numbers matched). But 2017.1.1 came up with what appeared to be the same errors. So on to sad trombone option (can anyone else hear the music when they read that?) ... uninstalling & reinstalling.

I have a suspicion that the server drive mapping is contributing to the issue. I'm not sure how that's set up here, but sometimes if I've browsed to a file via the mapped drive, programs can't find the same file later through "recent" files. My suspicion is coming from several can't find/invalid drive "G" errors. So on the reinstall, I decided to browse to and run Setup via the network path instead of the mapped drive. Reinstall ok so far. Tomorrow morning to retry the updates.