Revit 2022.1 Patch Unsuccessful

[ajuelich]

Hello,

I'm battling some issues on Revit 2022 and would like to patch it completely to rule out that as a potential fix.  When I go to install it says it is successful but I do not see it in Programs/Features, nor does the Build Version change.  Reading their release note, it says it may require access to the install content but this was deployed from the Network so that install location is no longer valid.  Any other way to get around this?

Thanks!

[natasha.l]

Hello @ajuelich, 

If you no longer have access to the original Content path, you can conduct a Clean Uninstall, then reinstall locally. So that the original Content path location is on the computer. 

1. I recommend downloading and reinstalling Revit 2022 from the Autodesk account portal
2. Install Revit on a local drive
3. Try reinstalling the update Revit 2022.1 Patch 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[ajuelich]

You want me to do this on 300+ machines? These are network installs. This
type of prerequisite does not work in these environments. Autodesk used to
realize this years ago but seemingly forgot these environments exist
completely. Even if I did this, it would only solve the problem for a
period of time before that content cache is cleared out.

[MarkMoorhead]

I agree, this is NOT a solution.  All files required to install the patch should be included in the patch.  Virtually no one will have the original install files still on their computer. 

[m_latz]

When you install Revit (or any other msi) the path of the installation source is saved in the registry.

If you later apply a patch which require the original installation source you should/can copy the original installation source again to the local pc. Then modify the registry to define the new install source  location as "LastUsedSource" and now you can apply the Revit patch without any problem.

You do not need the installation source of the whole Revit deployment, only the files from the rvt.msi.

regards

Markus

[ajuelich]

And how do you suppose I do that on close to 300 machines over several different locations?  We never had to do this in the past.  Autodesk changed Deployments and Patching completely, and didn't even update any of their documentation.  Their Support doesn't even know anything about the changes.  It's a big ol' mess over there.

These responses show a clear lack of understanding on the environments in which most Autodesk products are installed and supported.  We're not talking about Mom and Pop shops where someone installed AutoCAD via a DVD.

[MarkMoorhead]

I understand that, but there are also different install source versions and you have to have the correct one to put back on your hard drive, especially if you installed at different times using a different install version. Those old install versions are hard to find to download again.

This solution is unacceptable.

[ajuelich]

This was never a requirement of Hotfixes in the past.  This isn't a me problem, this is a Autodesk problem that they need to resolve and document properly.  And they need to start understanding their actual customer base before they go to reinvent stuff every few years for the heck of it.

[MarkMoorhead]

I 100% agree, especially for the amount of money they charge for these subscriptions.

[m_latz]

Different install source versions of the rvt.msi for Revit 2022  ?

I know this was a problem with Revit 2021, but in Revit 2022 I did not notice that.

I've build deployments between 4th july 2021 and now and always have the same rvt.msi signed at:

If you have different rvt.msi version for Revit 2022 can you please tell me, at what date they are signed, then I can try to get that sources and check the difference between the files.

For the case of different installation sources, I use the oldest installation source version and make patches to the other version(s). These patches have only a few MB compared to the whole rvt installation sources.

Then my installer/updater make a check on the local pc for the correct version, copies temporarily the installation sources to the local pc, modifies the "LastUsedSource" entry in the registry, patches the sources if necessary and applies the msp file.

You can use powershell to script this or any other programing language you work with. Then you can use your deployment software (SCCM or whatever) to distribute.

regards

Markus

[MarkMoorhead]

I could be mistaken about 2022 having different install sources. Just assumed it was similar to 2020 and 2021. However, here should have to be no scripting or any other hoop to jump through just to install a vendor provided patch.

[ajuelich]

For a decade or more you could easily deploy the hotfix and the switches to do so were documented.  Now, all of the sudden, I need to somehow get 12+ GB of data down to each of my 300 machines, magically change a bunch of undocumented registry settings, and then process the hotfix, and then clean all of that up.  It's utterly insane and major steps backwards.  And none of this is documented.

I shouldn't have to do some crazy powershell scripts.  That is the job of Autodesk Support and their developers.