Revit 2020.2.9 Hotfix

49 views
Skip to first unread message

Ailene Goldhirsh

unread,
Jul 27, 2024, 4:43:19 PM7/27/24
to passfinklallnas

On a laptop the installation gets to 33%, and then looks for the original installation file Rvt.msi to complete the install. I don't seem to have the file. I might have removed temp files because this is a bit leaner laptop for travel, but I can't recall doing that, so it could just have to do with how it was installed.

I considered reinstalling Revit 2022, or starting it so I would have the rvt.msi file but the Autodesk Desktop App won't let me do that either since it is installed. I would rather not have to completely uninstall Revit and any add-in's, and reinstall all of it just for a hotfix.

revit 2020.2.9 hotfix


DOWNLOAD ————— https://bltlly.com/2zRJ7S



I have tried two different methods to install Revit 2022.0.1 hotfix (Desktop app and direct download) using two different level of user rights (Power User and Admin) on two different Computers (my everyday workstation and my Dell Precision mobile workstation running an 8 core Zeon and otherwise fully loaded) = 8 different attempts. All have failed. It gets to a point where it's trying to unpack different sub components from a temp directory and can't find them... I have manually dug in and found the components that it can't find and pointed it to them, but the installs still fail...

On one computer those files didn't even seem to have gotten downloaded (I searched all of the packages in the temp folder for the missing components), I ran the installer again under a different user and it reached the same point but the temp folder that it was looking for was in a folder under the other user account... and on the other computer it created temp folder "x" but was looking for temp folder "y"... even after pointing the dialog to the correct folder and contained file it failed.

I was finally able to get a successful install on one machine under one configuration and that one is the only one that has any of the applicable log files (I don't currently have one of the computers available to me so I can't confirm that this is true in all of the test case scenarios that I started this post with.). The error that has been occurring is that it can't seem to find the place that it unpacks everything to so it doesn't have anywhere to place a log file (or so it seems to believe) on top of not being able to run any of the separate packages.

The one that did finally succeed was the result of me catching the install right after it unpacked everything and storing the contents of the patch elsewhere, then running the exe directly. unfortunately this is not a working solution for the other 70 installs that will need to be performed.

However, just to be as thorough as possible, here are the log files from the one that did install (or enough to update the Revit About page). Probably won't help much because they were run from a different scenario than applying the hotfix as it's presented to us from Autodesk...

Gary - I took your case on Directly, but have already escalated it to Autodesk, so look for a call from their agent. But since we're getting ready to build our 2022 deployments, I wanted to stay in touch with you here on this one.

Are you using SCCM for deploying the updates, or just the Desktop app? We've had some issues where there is more than one uninstall thread that causes this failure. I'm not sure if this is specific to updates only, but we caught it with Desktop Connector 14.10.0.1456 update recently. We've been looking into ways to manually uninstall the REX Framework position before running the update.

We're a user base of about 70 across two offices, mixed bag of Architects, building Engineers (MEP), Civil Engineers, and Surveyors. The deployments would get messy as all getout and we would have about as many as we have employees using design software. So we create individual deployments and stick them on a server where everyone can get the pieces they want. We also do the same for "critical" patches and notify users when there is one they need to install. Everything else is installed directly from the Desktop App by the users as they want/need them.

In my testing I have tried multiple installation methods (Desktop app, downloading the installer, etc) using several different user rights (power user with Admin auth for the installer, local machine admin user, and network admin user).

The only success that I have had is as noted previously: making a copy of the unpacked package and installing the individual components manually. the successes and failures noted previously are common regardless of computer or user rights.

After running into a problem with another, very simple, installer that simply overwrote a couple of files with newer ones, I believe we have tracked this issue down. We now have several successful installations of the service pack without failures.

The failures were happening (or so I now believe) on a small set of computers in which we had installed Revit 2022 prior to a policy change within our environment. IE: they were installed while the users had local Admin rights to their computers (or were installed under a different user that had local Admin rights). The service packs were being installed after those rights had been reduced to Power Users on the local machines. The installers for the service pack were being granted admin rights from the desktop at run time, but that was causing conflict within the system and somehow preventing access to the uninstaller that the new installer needed to run (even when the SP was being run under a different user with local Admin rights strangely enough).

Awesome - we were having a similar issue with Desktop Connector, where a newer version was installed than the one were supporting. We've been incorporating uninstall scripts where we can but as you said it can get messy - in some cases, the uninstall leaves files and keys behind that stop another installation. I'll check back in later to see if you have any more details - thanks for the update!

Has anyone had issues starting up Revit after downloading the latest hotfix for 2020?? A number of users in my company have not been able to start Revit after downloading the hotfix, it gets stuck on the start-up window.

I recommend conducting a clean uninstall, then downloading the full installer using the Browser Download from your Autodesk account, (not the Autodesk Desktop app) pointing to the folder location where the RVT.msi is located.

Helpful Links:
AutoCAD Videos AutoCAD Crashes or Freezes AutoCAD Customer Council AutoCAD System Requirements Prepare your computer for download Autodesk Virtual Agent Clean Uninstall Steps for Setting-Up Student Software

The issue is when I download the hotfix, after clean uninstall/ install, Revit no longer opens. I have installed Revit through the browser, and downloaded the hotfix via Autodesk Desktop app updates.

With a week's time, I had to remove FOUR installations of Revit 2020 that were upgraded to 2020.2.7, all by way of the Autodesk Update App, because the application failed to open after the update was applied. After the first incident, I had to make sure that it wasn't a mistake, so after I cleaned it up--using Autodesk's own manual removal documentation--I reinstalled Revit 2020 and then systematically updated it, patch at a time, still using the Update app; with each major patch (2.2, 2.3, etc.), I would stop updating and open the application. However, as soon as I applied 2.7, Revit 2020 wouldn't even open, not even after 20 minutes.

Once again, I manually removed Revit 2020, reinstalled it, then applied all patches up to 2.6, but NOT 2.7. Shortly after that first incident, three other users applied the 2.7 update, each of which resulted in Revit 2020 failing to open. At that point, I issued a company-wide directive to users of Revit 2020 to NOT install the 2.7 patch until Autodesk comes up with a solution.

Autodesk documentation indicates that patches cannot be removed individually; the entire application must be removed. However, I note that starting with Revit 2022, it appears that individual patches CAN be removed.

I have had another user in my office re-install Revit 2020 through the browser and subsequently install the hotfix 2020.2.7 through the browser also and he had no issues (yet) starting up Revit afterwards. Access to browser download via the desktop app - see attached steps to do this and please share if it works. Note you can also uninstall a hotfix through the browser. If you have it already downloaded you will have option to uninstall at step 3.

Several users in this office have installed both 2019 & 2020 hotfixes with no issues.

I tried uninstalling - No go. Reinstalling - No go. I finally had to slam a recent disk image back to my OS drive and all is well now. Macrium Reflect image saved me a re-install of 2019 & 2020 and took about an hour to do.

In order to troubleshoot this issue, a journal file from an impacted system would be extremely helpful. It may help to identify which component is failing to load and causing Revit to become non-responsive.

Lastly, a previous commenter noted that they were installing each of the Revit updates/hotfixes individually. This should not create a problem but it is unnecessary because Revit updates and hotfixes are cumulative and include all changes from previously released updates/hotfixes.

The install codes for Revit 2021/22/23/24 work and install the default version. But if you want to install updates and hotfixes where they are more than 1 and have a pre-req of a specific version, it seems to be an issue.

Could that be because the install took more than 40 minutes and the timeout was set to default at 30 minutes?
I will try to see after incresing that timeout window.
Also, any idea on the custom detetion script and dynamic script for Autodesk Revit installers ?

Can we make a copy of Revit Installer. I dont see the option to download the installer. Does someone has the Revit 2021 default installer with version 21.0.0.383 ?
I need to run that as a pre-req with install directory as Program Files and not %Program Files%. I am running it as a pre-req for 2021.1.9 update.
It is installing in the wildcard and need to build a custom 2021 so sot use with the install directory as Program Files.

64591212e2
Reply all
Reply to author
Forward
0 new messages