Autodesk 2026 Crashes Trying to open an AutoDesk 2023 file

I did a system upgrade of a Autodesk Revit Machine where the upgrade was a significant one  The system was 10 years old an Intel i7 2600K to an AMD Ryzen 5 9600X.  The CPU boost alone is significant but everything was just better.  Going from 32GB DDR3 to 64GB DDR4 and upgrading from an ATI FirePro 4800 to a Nvida RTX 5060.  The Storage also got a huge boost moving from a 1TB SATA SSD to a Gen4 M.2 2tb WD Black.

CPU Comparision

The system came together great, it loaded autocad, revit extremely quickly and rending files that would normally take hours took just a few minutes.  Then the SNAG happened.

A particular file that they were working with did not work on the new system.  It opened fine on the old system but it took a while to make changes and they wanted to migrate the job file to the new system and the new version of REVIT.  Given the generational changes in processing not to mention it being completely different CPU architectures, upgraded software, windows 11 pretty much anything could be causing the issue.  There was no other file that had an issue like this file.

With no other files seemingly being affected, and the old system did not have the problem with opening or rendering the file so I started looking into differences in the software and the system.  We even got autodesk involved, and they didn't have any trouble opening the file; however no one tried to render it.

We did as they asked and tried the following:

Please try this
1. Install all the updates for windows, and video card driver, restart computer
2. Close all Autodesk programs.
3. Run "Autodesk Access", sign in as your email
4. Install all the updates listed from bottom towards up
5. Restart computer.

If still not working, try the following 3 things:

1. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Clear-a-corrupt-damaged-C4R-model-from-the-system.html

2. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-Disable-Add-Ins-for-Revit-Products.html

3. https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-reset-Revit-to-the-installation-defaults.html

Hope this helps, let me know.

When none of that worked; did some more research but came up empty.  Below are some of the things I tried to get the system to open the file.  Really the file opened but no changes could be made and the file would not render it was quite the issue.

Troubleshooting:

For Revit 2026, you can disable add-ins by using the built-in Add-Ins Manager, its standalone application, or by manually moving the add-in files from their installation directory. These methods allow you to manage add-ins individually, as a group, or disable them entirely. 

How to use the Add-Ins Manager

• Inside Revit: Click on the Manage tab, then find the Extensions panel and click Add-Ins Manager. From here, you can enable or disable individual add-ins, all add-ins, or macros. The changes will take effect after restarting Revit.
• Standalone Application: Search for "Revit Add-Ins Manager" in the Windows Start menu or navigate to the installation folder at <Revit installation folder>AddInsManager\RevitAddInsManager.exe. This is useful if a faulty add-in prevents Revit from launching.
• Cloud Models: If you are working with cloud models, you may need to deselect all items in the Add-Ins Manager and then recheck only the Autodesk Collaborate add-in before restarting Revit. 

How to disable all add-ins at once

For users who need to disable all third-party add-ins at once, you can modify the Revit.ini file. 

• Add a section called [API].
• Add the line DisableUserAddinsAndMacros=1.
• To re-enable the add-ins, change the value to 0.
• Restart Revit for the changes to take effect.

3. General System and Software Troubleshooting

• Disable Add-ins: Temporarily disable all third-party add-ins in Revit 2026 to see if a conflict is causing the crash.
• Update Graphics Drivers: Ensure your graphics card drivers are updated to the latest certified version from the manufacturer's website.
• Check System Resources: Verify your system meets the Revit 2026 System Requirements (16 GB RAM minimum, 100 GB free disk space for temp files recommended).
• Clean Reinstallation: If all else fails, a clean uninstall and reinstall of Revit 2026 may be necessary to resolve a corrupted installation.
• Check Windows Event Viewer: This can provide clues about the crash details. 

If the problem persists, gather your Revit journal files and submit a support ticket to Autodesk with the crash report number for further investigation. 

The default location for Revit journal files is: C:\Users\%USERNAME%\AppData\Local\Autodesk\Revit\<Autodesk Revit version>\Journals. This folder can be accessed by typing %LOCALAPPDATA%\Autodesk\Revit\<Autodesk Revit version>\Journals into the File Explorer address bar. If you cannot find the folder, it may be hidden, so you will need to enable "Show hidden files, folders, and drives" in Windows' folder options.  

• Default location: 

  C:\Users\%USERNAME%\AppData\Local\Autodesk\Revit\<Autodesk Revit version>\Journals. 
• To find it quickly: 

  Type %LOCALAPPDATA%\Autodesk\Revit\<Autodesk Revit version>\Journals into the File Explorer address bar. 
Replace the placeholder: 
Replace <Autodesk Revit version> with your specific version, such as Autodesk Revit 2024 or Autodesk Revit 2023. 

Crashes when opening of a Revit model

• Cloud Model: If the model being opened is stored on a BIM 360 or Autodesk Docs cloud project, see the following article: Crash with or without CER occurs when trying to open any model in Revit.

• Install Revit Updates: See the following article: How to keep Revit updated.

• Install clean Revit: How to Complete a Clean Uninstall of Revit products 

• Disable Add-ons: See the following article: Check if add-ons are causing unexpected behavior in Revit.

• Try opening the file with Audit.

• Open with worksets closed

  1. Open the model with the worksets containing linked models closed: Open Worksets.

  2. If the model opens, reload each link individually until the problematic link is identified.

• Crash on Windows 11 environment:

  • Crash when using steel connections: SQLDUMPER.EXE window opening and closing when launching or working in Revit or Advance Steel

  • Crash with update Windows 11 24H2: Crashes in Revit after updating to Windows 11 24H2

• Crash in Revit 2024 at conflicting/ corruption schemas when using mixed Revit updates: Schema Conflicts in Revit 2024

Note: See the following for Revit and AutoCAD links: 

• • "Data in file (file name).rvt is corrupt and needs to be manually recovered" when opening a file or syncing a file to central in Revit.

  • How to repair corrupt AutoCAD files.

More Troubleshooting

See the following link for more troubleshooting: Crash AND open.

For Revit 2019 and older

1. Rename or Delete the Flexnet files:

Close all Autodesk software, then rename or delete the following three files from this location: C:\ProgramData\FLEXnet

• • adskflex_<number>_tsf.data

  • adskflex_<number>_event.log

  • adskflex_<number>_tsf.data_backup.00

Note: Check if the files are not hidden using these steps: How to turn on hidden files and folders on Windows.

2. Locate and rename the ADUT folder:

   1. Go to C:\User\username\AppData\Roaming\Autodesk\ADUT.

   2. Rename the folder (for example, to "ADUT2").

3. Delete the contents of the folder: C:\ProgramData\Autodesk\CLM\LGS.

The Fix

The fix ended up being an issue with SteelConnections.  I paid careful attention to what the system was doing when it was trying to render and noticed it was crashing bringing up steelconnections.  So what I had to do was manually remove steelconnections from the addins folder.

Close Revit.

Browse to the folder C:\ProgramData\Autodesk\Revit\Addins\[Version].
eg  %PROGRAMDATA%\Autodesk\Revit\Addins\2026

Move the add-in files to another location to temporarily disable them. Renaming the files will not work. (eg moving steelconnections2026.addin to the desktop)

Restart Revit to confirm the add-ins are no longer available. 

That fixed the issue with the file.  The file rendered very fast taking only a few minutes on settings that use to take the older system hours.

*Note to re-enable the addin move it back to the addins directory

A powershell script to update rustdesk in action 1

For maintaining remote access for our IT systems we use a mix of action1 and rustdesk.  Though action1 has a very good remote web interface it can be slow at times.  I've setup a rustdesk server for additional security.  Below is a powershell script that I created.  

The script creates a folder for downloading rustdesk from github; and if it isn't there create it, download and install.  There is a else where if it is installed, uninstall rustdesk then create the install directory and install the latest version.

$Folder = 'c:\#NAMEOFFOLDER'

"Test to see if folder [$Folder]  exists"

if (Test-Path -Path $Folder) {

Remove-Item -Recurse -Force c:\#NAMEOFFOLDER\*.*

Remove-Item 'c:\#NAMEOFFOLDER'

Get-CimInstance -ClassName win32_product | Where-Object Name -Match "RustDesk" | 

    ForEach-Object -Process { 

        Invoke-CimMethod -InputObject $_ -Name Uninstall 

                            }

New-Item -Path "c:\" -Name "#NAMEOFFOLDER" -ItemType "directory"

Invoke-WebRequest https://github.com/rustdesk/rustdesk/releases/download/1.4.6/rustdesk-1.4.6-x86_64.msi -OutFile c:\saplit\rustdesk-1.4.0-x86_64.msi

$pkg = "c:\#NAMEOFFOLDER\rustdesk-1.4.0-x86_64.msi";

Start-Process msiexec "/i $pkg /norestart /qn" -Wait;

##Start-Process msiexec "/i $pkg /qn" -Wait;

##Start-Process msiexec "/i $pkg /norestart /qn" -Wait;

Start-Sleep -Seconds 30

Remove-Item -Recurse -Force c:\#NAMEOFFOLDER\*.*

Remove-Item 'c:\#NAMEOFFOLDER'

} else {

#uninstall rustdesk

Get-CimInstance -ClassName win32_product | Where-Object Name -Match "RustDesk" | 

    ForEach-Object -Process { 

        Invoke-CimMethod -InputObject $_ -Name Uninstall 

                            }

New-Item -Path "c:\" -Name "#NAMEOFFOLDER" -ItemType "directory"

Invoke-WebRequest https://github.com/rustdesk/rustdesk/releases/download/1.4.6/rustdesk-1.4.6-x86_64.msi -OutFile c:\saplit\rustdesk-1.4.0-x86_64.msi

$pkg = "c:\#NAMEOFFOLDER\rustdesk-1.4.0-x86_64.msi";

Start-Process msiexec "/i $pkg /norestart /qn" -Wait;

##Start-Process msiexec "/i $pkg /qn" -Wait;

##Start-Process msiexec "/i $pkg /norestart /qn" -Wait;

Start-Sleep -Seconds 30

Remove-Item -Recurse -Force c:\#NAMEOFFOLDER\*.*

Remove-Item 'c:\#NAMEOFFOLDER'

}

Removing a VM from Hyper-V High Availability cluster

 To remove a virtual machine from a Hyper-V High Availability cluster is really relatively trivial, so long as you don't have any system on the cluster in failover, you right click on the role and click remove

You will then be prompted; asking if you want to remove the role and you select YES.

Then the system is removed from the cluster and is operating on the host the VM was assigned to run to.

Automating SQL Data Dump and SFTP File Transfer with Powershell and WinSCP on Windows

We work with a third party that takes care of a few systems for us that we automated and to make that work we had to script an automated process to export data from our SQL server and automatically upload it to an SFTP Server.

For this setup we are using WINSCP for doing the file transfer and a combination of a bat file and powershell for exporting the data out of SQL and automating the process.  I am using windows for automating this process.

What will be required:

WINSCP

Powershell

So install powershell and WINSCP on to the system.  

Open powershell as and administrator and install the Clobber the WINSCP Module and the SQLServer module

Install-Module -Name PowershellGet

Install-Module -Name SQLServer

Install-Module -Name WinSCP

Once done we will make two files, they will be running from the same directory.

SQLDataExport.ps1 and gen_sql_data.bat

The powershell file is fairly straight forward. It essentially gets and runs the sql query and saves it to a directory as a txt or csv.

SQLDataExport.ps1

$serverInstance = "$address, $port" 

$databaseName = "$databaseName" 

$Username = "$databaseUser" 

 $Password = "$databasePassword" 

$filePath = "$PATH\$FILENAME" + (Get-Date).ToString("yyyyMMddTHHmmss") + ".txt" 

Import-Module SqlServer 

$sqlQuery = "$YOURSQLQUERY" 

Invoke-Sqlcmd -ServerInstance $serverInstance -Username $Username -Password $Password -Database $databaseName -TrustServerCertificate -Query $sqlQuery | Out-File $filePath -Encoding UTF8

BatFile (This is where all the FTP Magic happens)

@ECHO OFF

powershell.exe -executionpolicy remotesigned -File $PATHTOPOWERSHELLSCRIPT.ps1

timeout /t 120

echo "FTP Started" >> seed_exReport.rpt

date /t >> exReport.rpt

time /t >> exReport.rpt

echo option batch abort > ftpPutCmds.txt

echo option confirm off >> ftpPutCmds.txt

echo open sftp://$USERNAME@$SFTPURL -privatekey=$SFTPPRIVATEKEY.ppk -passphrase=$PASSWORD -hostkey=acceptnew >> ftpPutCommands.txt

echo option transfer binary >> ftpPutCmds.txt

echo cd seed >> ftpPutCmds.txt

echo put $SQLDATA_*.txt >> ftpPutCmds.txt

echo close >> ftpPutCmds.txt

echo exit >> ftpPutCmds.txt

"C:\Program Files (x86)\WinSCP\WinSCP.exe" /console /script=ftpPutCmds.txt /log="$PATH2Error.log" /loglevel=1* /logsize=5*100M

echo "FTP Finished" >> seed_exReport.rpt

IF EXIST *.txt (move *SQLDATA_*.txt Old\) REM move old file to a folder called old

date /t >> exReport.rpt

time /t >> exReport.rpt

echo. >> exReport.rpt

Once done you can setup the task scheduler to run the batfile.  You will need the script to start in the directory that the bat file and powershell file are in.

Allowing Windows 11 Access to Unauthenticated Shares

Windows 11 prevents you from accessing open SMB shares because they are a security risk.  However sometimes you need to access these unauthenticated shares for a variety of reasons.  Here is how you do that.

Method 1: Use the Local Group Policy Editor 

1. Open the search menu and type gpedit.msc, then select "Edit group policy" to open the Local Group Policy Editor.
2. Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation.
3. Find and double-click the policy named "Enable insecure guest logons".
4. Select "Enabled," click "Apply," and then "OK".
5. Restart your computer for the changes to take effect. 
6. 
   
   

Method 2: Use the Registry Editor 

1. Open the search menu, type regedit, and press Enter to open the Registry Editor.
2. Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
3. In the right-hand pane, find the AllowInsecureGuestAuth value. If it doesn't exist, right-click in an empty space, select New > DWORD (32-bit) Value, and name it AllowInsecureGuestAuth.
4. Double-click AllowInsecureGuestAuth, set the "Value data" to 1, and click "OK".
5. Close the Registry Editor and restart your computer. 
6. 
   
   
   

Enabling Java Virtual Console on Windows 11 and Windows Server

I wrote a post about bypassing Java MD5 to run Java KVM viewer, well now to get it to run on the latest version of java and Windows you need to disable it completely or have an alternative to using the iKVM Viewer.

With the MD5 algorithm disabled with the new java, you get an application error attempting to launch the iKVM Viewer as shown below.

To resolve the issue you need to open a text editor program as administrator on windows and browse to your JAVA directory a typical default example is 

"C:\Program Files (x86)\Java\jre-1.8\lib\security\"

Open java.security

an go to line 694 and disable the jdk.jar.disabedAlgorithms by putting a # in front of the line as shown below.

You will then be able to run the iKVM viewer as shown below.

Replacing a drive and repairing a storage spaces volume

When you have a drive fail in a storage spaces, changing out the drive isn't straight forward, however well worth the effort when you consider the advantages storage spaces has over regular RAID.  Specifically the lack of a an expensive disk controller, and tiered spaces with the use of HDDs and SSDs.

So in my case it is a 2U server with a RAID Controller set to JOBD, and I had a failure of a Seagate drive as shown in the picture above.  On the server we removed the bad physical drive, if on a raid controller prepare the drive, should be set to JOBD.  Formatting may be required.  As shown in image below, I added a Toshiba drive; and to replace it we need to the the following.

PS C:\> $PDToRemove = Get-PhysicalDisk -FriendlyName "$DISKNAME" 

In this case the drive's friendly name is "SEAGATE ST600MP0006" then we need to remove the disk with the following Powershell statement.

PS C:\> Remove-PhysicalDisk -PhysicalDisks $PDToRemove -StoragePoolFriendlyName "$PoolName"

(in this case SEAGATE ST600MP0006)

Once the old disk is removed we can run a repair with the following powershell statement

PS C:\>Repair-VirtualDisk -FriendlyName "$VIRTALDISK"

This will take some time to run, but it is much faster then repairing a RAID setup, taking about 20 minutes to repair the storage spaces mirror setup.  While the dive is being repaired you will see it in a InService status.

When storage spaces finishes the drive will show as being in good health.