Cannot install Revit Sever 2026

[michaelNB4NL]

Hello,

I have Revit Server 2025 installed and running already on our server and trying to install Revit Server 2026 alongside it.  However, I start the install and then just get a generic "Cannot Install.  This computer does not meet the minimum requirements for Autodesk Revit Server 2026".  

This is on a Windows Server 2019 server with a Xeon E-2224 processor with 16GB RAM and plenty of space on the SSD hard drive.  I've made sure to update .NET framework and made sure it was running 4.8.x.  Looking at the requirements for Server 2025 vs Server 2026, it seems the only difference is that Server 2026 dropped support for Windows Server 2016.  Otherwise, it appears that our server meets the minimum requirements.

I can't seem to find any errors of note in the install.log (I can upload logs if wanted).  Anyone else having an odd issue just getting it installed?  I saw the other posts about folder permissions, but I can't even get to that point.  Any suggestions?

Thank you in advance for any ideas.

[vmartinez5V3ZH]

Same issue here. Any suggestions? 

[michaelNB4NL]

I have submitted my logs to Autodesk support.  I'll post back here if I end up getting any helpful feedback.  Others can feel free to post if they have suggestions as well.

[vmartinez5V3ZH]

Thank you for sharing this. I appreciate you taking the time to contact Autodesk support and for your willingness to post any updates you receive.

I'm very interested in hearing what feedback they might provide. On my end, I plan to open a new support case with Autodesk tomorrow morning regarding the same issue. Hopefully, with more cases being reported, we can get clearer guidance or a resolution soon.

[michaelNB4NL]

The current thinking is that we are running into an issue on our end with trying to install Revit Server 2026 on a domain controller.  We are a small firm and run Windows Server 2019 Essentials.  Autodesk said they are working on a potential change to the installer that I can try to see if that fixes our issues.  Is your server running as a domain controller as well?

[vmartinez5V3ZH]

Thanks for the update, Michael.

Yes, our server is also running as a domain controller — we're using Windows Server 2019 Standard in our case. That might very well explain why we're seeing the same issue.

I appreciate you sharing that Autodesk is working on a potential installer update. Please do let us know if that helps resolve the problem on your end. I'll make sure to mention the domain controller aspect when I open our support case today.

[huotger]

Hello, 

Yes, the current iteration of the Revit Server 2026 installer is performing an OS check via a specific registry key and the expected value is not met when Windows Server is configured as a Domain Controller.  We are working on an adjustment to the Revit Server 2026 installer to improve the OS check to account for this use case. In the interim the following process can be utilized:

1. Download the Revit Server 2026 installer executable
2. Extract the contents of the executable (using 7Zip)
3. Within the extracted location, edit the Setup.xml
   • Remove the entire  <Signature> line
   • Edit line "<Property property="OS_PRODUCT_TYPE" defaultValue="ServerNT">" to   <Property property="OS_PRODUCT_TYPE" defaultValue="LanmanNT">
4. Save the setup.xml
5. Run setup.exe

I hope this helps.

[vmartinez5V3ZH]

Hi, Gerry, 

Thank you very much for your suggestion and for looking into this issue.

I followed the steps you provided — extracted the installer, modified the Setup.xml as indicated (removing the <Signature> line and changing the OS_PRODUCT_TYPE to LanmanNT) — but unfortunately, the installation still fails with the same error about not meeting minimum requirements.

I appreciate the workaround attempt. Could you let me know where exactly in the installation log files I might find more detailed information about this error? I’d like to review the logs to see if there are any additional clues.

Thanks again for your support.

[huotger]

Please utilize the Installation Log Collection Tool to obtain all the local log information for Autodesk based installations, includeing Revit Server 2026.

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-Use-the-Log...

[michaelNB4NL]

This worked for me.  I had to manually unzip using 7Zip.  I couldn't have the installer unzip to the Autodesk/WI folder and make the edits there (that failed with the same error as before).

[vmartinez5V3ZH]

Just wanted to share the workaround that finally allowed me to install Revit Server 2026 on our Windows Server 2019 Domain Controller, after repeatedly running into the "This computer does not meet the minimum requirements" error.

Important warning: This approach involves modifying the Windows registry. Proceed only if you fully understand the implications and have proper backups in place.

I initially followed Autodesk's suggestion to manually extract the installer with 7-Zip, remove the <Signature> line from the setup.xml file, and change the line:

<Property property="OS_PRODUCT_TYPE" defaultValue="ServerNT"> to: <Property property="OS_PRODUCT_TYPE" defaultValue="LanmanNT">

I made sure to run the installer from the extracted folder and not from the default Autodesk/WI directory. However, the installation still failed with the exact same message.

After reviewing the installation logs — especially the DDA.log — I confirmed that the installer is internally performing a system requirements check against the actual registry value of:

HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductType

The log explicitly shows the condition check failed because it expected "ServerNT".

Workaround that finally worked:

1. I created a full system backup and a snapshot of the Domain Controller beforehand (we're running on virtualized infrastructure).

2. I temporarily changed the registry key:

   HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductType from "LanmanNT" to "ServerNT"

3. I ran the Revit Server 2026 installer — it completed successfully without any issues.

4. I immediately reverted the registry key back to "LanmanNT" before restarting the server.

Everything is working correctly so far.

Note that this registry change must be strictly temporary. Do not reboot the server while the modified value is in place, as this could seriously interfere with domain-related services or system integrity.

I hope this helps others in a similar situation, and I strongly encourage Autodesk to update the installer logic to account for Domain Controllers properly — especially given how common this setup is in small office environments.