AutoCAD Open File Dialog Not Showing? Open Button Does Nothing — Fix FILEDIA = 0

With FILEDIA at 0, the Open button, Ctrl+O and the OPEN command all start normally, but instead of the Select File dialog the command line shows a prompt like the one below. AutoCAD is waiting for you to type the path of the file, so nothing is wrong with the program itself.

It isn't only Open. FILEDIA suppresses the file navigation dialogs for every command that reads or writes files. Autodesk's own example is SAVEAS, which prompts on the command line instead of showing the Save Drawing As dialog. If more than one file dialog has gone missing at once, FILEDIA is almost certainly the cause.

Press Esc to cancel the pending prompt first. Otherwise whatever you type next is read as a file path, and AutoCAD ignores your other input, even an attempt to close it.

Then type FILEDIA on the command line and press Enter. AutoCAD shows the current value in angle brackets. A value of 0 means file dialogs are switched off. The normal value is 1.

At the same prompt, type 1 and press Enter. If the prompt has already gone, type FILEDIA again.

FILEDIA is stored in the Windows registry rather than in the drawing, so the change applies to every drawing and survives closing and restarting AutoCAD. You can make it from a blank drawing; which drawing is open doesn't matter.

Click Open again. The Select File dialog appears, and Save As and the other file dialogs come back with it.

If something is deliberately keeping FILEDIA at 0, for example a script that is running or a company routine, you don't have to change it. Autodesk's documentation says that with FILEDIA at 0 you can still request a file dialog by entering a tilde (~) in response to the prompt.

At the Enter name of drawing to open prompt, type ~ and press Enter. The Select File dialog opens for that one command, and FILEDIA stays 0. You can also type the full path of the drawing at the same prompt.

Autodesk explains the usual cause. A LISP routine, a menu macro or a batch script that opens or saves files sets FILEDIA to 0 so that a dialog doesn't interrupt it, and is meant to put it back to 1 when it finishes. If the routine is cancelled, or fails, and has no error handling that restores the value, FILEDIA stays at 0 and you see the symptom on the next Open.

Add-ins and startup routines that run LISP when AutoCAD loads can leave it at 0 in the same way. If FILEDIA is 0 right after starting AutoCAD, look at what loads at startup: the Startup Suite in APPLOAD, and any acad.lsp or acaddoc.lsp files on the support path. To narrow it down, set FILEDIA to 1, run one tool or load one add-in at a time, and check FILEDIA after each.

If you write your own routines, save the old value with GETVAR before setting FILEDIA to 0, and restore it in the error handler as well as at the normal exit.

AutoCAD has a System Variable Monitor that compares the variables you choose against the value you prefer and warns you when something changes one of them, whether that is you, a script or an add-in. Type SYSVARMONITOR to open its dialog. If FILEDIA isn't in the list, add it and set the preferred value to 1.

The next time a routine switches file dialogs off, you get the notification straight away, instead of finding out when Open does nothing.

If FILEDIA is already 1 and still nothing shows, AutoCAD may be waiting on a dialog that exists but isn't visible, for example one opened behind the main window or on a monitor that is no longer connected. Try Alt+Tab. That is a different problem from FILEDIA: a FILEDIA value of 0 always leaves a prompt on the command line, which is how you tell the two apart.