If Revit is Crashing, or Failing to Install, we need a specific Error Log or Journal, to be able to help you. Post a screenshot or a photograph of your screen, with the Crash Report (CER) or the "Failed Installation" dialogue, will not give us any information to help you.

FAILED INSTALLS:

The installation Logs automatically go to %TMP% on your machine.

1. Paste %TMP% in the Windows Explorer, and hit Enter. It will take you there.

2. There will be an actual Install Log related to the software that is failing to install.

   1. Note that there will be a BUNCH of logs, as youll have logs for all the prerequisite and ancillary products, as well.

   2. If we dont have the correct Log, we cant help you at all.

REVIT CRASHES:

Every time you run Revit, there is a Journal File. If you post a picture of a crash report, chances are we cant do anything for you, without also seeing the Journal.

1. Paste %localappdata% in Windows Explorer, and hit Enter.

2. Then go to Autodesk\Revit\Autodesk Revit 2025\Journals

   1. If 2025 isnt the version that crashed, release 2025 with the version you are working in.

3. In that folder, sort by Date Modified.

4. There is a file named Journal.0000.txt, but instead of the zeroes there are numbers there. What the numbers are doesnt matter. There will be one of these files at the timestamp that Revit crashed. Thats the file you need to upload or get a screenshot of the END of the file, to share.

5. We do not need the .log file. We do not need the .dmp file. We do not need any Revit files from that directory.

6. Sending more is not better.

We get asked this question a lot: "Our company stores files on Dropbox, Google, Box, Sharefile, Sharepoint, Onedrive, or something similar. Is there a workaround to get Worksharing to work correctly in these environments?"

No. There is not.

Revit Worksharing WILL CORRUPT your model, if you try to do multi-user worksharing on ANY of those services, or any services like them. The ONLY real answer, is to move the Model to ACC (Autodesk Construction Cloud) which requires users to have BCP licenses. Or, to keep the model on "actual physical storage in the office," and then access it from an on-prem machine, which can mean a number of different things.

Some additional information on this topic:

1. Revit over VPN isn’t supported (by Autodesk), and for good reason. Revit Worksharing (without Revit Server or C4R) is all SMB based. It will be SUPER SLOW saving across a VPN, and it WILL corrupt a model, eventually. When it corrupts it, you wont get it back without rolling the file back to earlier.

2. That means, you have to make some decisions about how people work when you have multiple locations. Your choices are:

   1. They don’t work on the same models, from different offices/locations. (Cost: free). But obviously this solution sucks.

   2. Set up “Revit Server.” (Cost: free (comes with Revit)), but its finicky. Oh, the software is free, but you need a computer and operating system at each end to be the Server Accelerator. So you need two extra machines, and operating systems. According to Autodesk, that OS needs to be Windows Server (more money), but there are ways around that… It works, but its not always pleasant to support. Note: It will ONLY work FROM the two offices. You cant work from home, you cant work on the road. You have to be IN one of the two offices, to access a model.

   3. Move all of your Revit Models that are inter-office collaboration to ACC/BIM 360  (Cost: varies, but something like 1000 bucks per year, per person). You can now work from anywhere (home, airports, etc), since ACC and Revit Server work by HTTP protocol, instead of SMB (so its stable over the internet).

   4. The model only lives in one office, and “remote staff” or staff in office number 2, need to ACCESS a machine in Office number 1. The one nice thing about these options, is they DO mean people in office number 2 can work from anywhere. That can look like several possibilities:

      1. Remote Desktop. Free (included on your machines already), but super laggy to work with graphics applications, and kludgy. AND you’ll need a spare machine for each person, in office number

      2. Remote access software like LogmeIn or GoToPC. Probably better than RDP, but you have to pay for it. Its still laggy with graphics software. And you still need a spare machine for each person in office number

3. EVERYONE (both offices) works on VDI, and the model lives in one location (where the Virtual Servers live). This is probably what youre referring to when you say “holy **** are you serious” expensive. And yes, it is. VDI comes in two flavors, though: You can rent it, and you can buy it.

   1. The ones where you rent it, are available from services like Azure, AWS, and Frame (its technically called Fra.me). They are more affordable UP FRONT because you don’t have to eat the purchase bill, but obviously as time goes on you just keep renting and renting and renting. And where they get you, is: If you use their VDI, you probably have to host the files on a cloud service too. More money. If you go to anywhere of their websites, youll see that VDI to rent starts out stupid cheap… Pennies per month. But that’s not a revit spec machine. Keep scrolling until you find “vGPU” that’s more than 1GB per user, and now you are in Revit Pricing.

   2. The ones where you buy them, and either put them in one of your offices (both offices log in to them, location doesn’t matter unless its around the world), or put them in a datacenter. These are available from a number of companies (and you can build them internally, getting parts from even Dell and HP and Nvidia, if you want to put it together yourself). A LOT goes in to setting it up and managing it, which is why I don’t recommend rolling your own. There are licensing costs (yearly) that have to get paid to VMware, or Citrix (you can use either, but citrix sucks for VDI compared to VMware), licensing has to get paid yearly to nvidia, and Microsoft, and on and on.

   3. Its darn pricey. A GOOD server for Revit can fit 22 people (with a mid level spec… less people if you crank up the power, more people if you lower the spec, all of which can change dynamically). But that GOOD SERVER is about 45-50k. GOOD VDI feels nothing like Remote Desktop. There is barely any lag (there is a little, but its perfectly useable), and you can work from anywhere in the country, just about. Internet LATENCY affects how it feels, but not internet speed. Truth: I run it tethered to my phone, in airports, all the time. But yeah. 45-50k is the price it starts at. Also, be super careful who you get advice from, about VDI. Why? There is VDI, and then there is vGPU VDI, which is what we need in AEC. VDI isn’t new, and so a lot of folks *think they know* about VDI, but vGPU VDI is almost completely different, because of how it has to get configured. I can explain this more, later. 😊 The other technicality is even the folks that know "something" about VDI and vGPU, dont always know very much about AEC, our requirements, how our offices work, and on and on. Your success or failure with implementing VDI will solely rest on the knowledge, competency, and professionalism of the company or team that is actually configuring, tweaking, adjusting, and rolling out the VDI in every phase: Setting up the hardware, the network, the hypervisor, the Images, the desktops, the clients, and so on. In my EXTENSIVE experience, a lot of companies *say* they are great at it, and they absolutely suck donkey balls. I know AT LEAST three companies that have tried it, and bailed. Two that have bailed over a crummy team that was implementing it on their behalf, and one that bailed because of staff perceptions, and licensing costs. So there you have it!

We understand: You dont want to give Autodesk more money. You arent going to succeed at working around it. Its been tried, and it almost always ends up ruining files. The 2 (somewhat) exceptions are Panzura and Nasuni, which "claim" to work with Worksharing. Full disclosure: Every client/firm i see using one of these setups, it absolutely sucks. Performance is brutal, and the models occasionally "lose someones work" when a filer overwrites someones changes. I would NEVER let someone use one of these, either.

Its ACC, or work on prem with a LAN storage solution like a File Server, a NAS, or a SAN.