Resources » Technical Support Blog » FormIt Installation Issue Troubleshooting

FormIt Installation Issue Troubleshooting

February 16, 2024 Gregory Lee

FormIt Versions: 2022, 2023 & 2024

Issue:

FormIt won’t start and is stuck at the launching screen. Re-installation doesn’t fix the launching issue.

Causes:

Multiple factors could lead to FormIt launch failure.

  • Faulty installation
  • Graphic Driver issue
  • C++ issue
  • *NVIDIA RTX gaming graphic card using the game-ready drive

Solution:

The troubleshooting process start with a clean uninstall.

  1. Verify the user’s graphic card type and drive version
    • NVIDIA RTX Gaming graphic card may be using the game-ready driver. Make sure to download Studio driver.                                                                     
    • For all other graphic drivers, make sure the driver is up to date.
  2. Verify if a user is using a 4K monitor with generic graphics card. If this is case, disable the 4K monitor before re-installation
  3. Install C++ redistributor files
  4. Download FormIt from Products and service page
  5. After installation is completed, go to https://formit.autodesk.com/page/download/ and download the latest release update.
  6. Install the update
  7. Reboot the computer
  8. Launch the FormIt but make sure the 4K monitor is turned off before the launch.

About the Author

Gregory Lee

Sr Technical Support Specialist<br><br> Skilled in AutoCAD, Mixed-use, Renovation, Revit, and Sustainable Design. Strong arts and design professional with a BA in Urban design focused in Architecture from University of Washington.

Follow on Linkedin More Content by Gregory Lee
Previous Article
PlanGrid Access issue with Build Subscription
PlanGrid Access issue with Build Subscription

PlanGrid access issue after subscribing to Build

Next Article
BIM 360 Team Folder Issue
BIM 360 Team Folder Issue

BIM 360 team folder yellow marker issue

×

Get Tips Delivered.

Subscribe to Email Updates.

First Name
Last Name
Country
Thank you!
Error - something went wrong!
Return to Resources