Why are instrument panel gauges blank in FS2004?

Blank instrument panel gauges in Microsoft Flight Simulator 2004 (FS2004/FS9) are usually caused by lost electrical or avionics power, missing or misplaced .gau/.cab files, or incorrect references in panel.cfg. Load a stock aircraft first: if its instruments work, repair the affected add-on rather than reinstalling the whole simulator.

What does a blank FS2004 gauge indicate?

The pattern of the failure usually identifies whether the cause is aircraft power, a missing gauge package or the wrong panel configuration.

How do I fix blank gauges in one FS2004 aircraft?

If only one aircraft is affected, check its power state and panel installation before changing any simulator-wide files.

1. Start with electrical power. Switch on the battery master, avionics master and generators, then raise the instrument and display brightness controls. Start the engines or auxiliary power source if the aircraft requires them. A fresh default flight is useful because a saved flight can restore a cold-and-dark cockpit or failed generator.
2. Compare a stock aircraft. Load a default FS2004 aircraft in a new flight and check both its 2D panel and virtual cockpit. Working stock instruments show that FS9's core panel system and shared gauges are functioning.
3. Back up the affected panel. Copy the aircraft's panel folder and aircraft.cfg before editing them. A normal location is [FS2004 root]\Aircraft\AircraftName\panel.
4. Confirm which panel folder FS2004 selects. In each relevant [fltsim.x] section of aircraft.cfg, a blank or absent panel= entry uses the standard panel folder. An entry such as panel=wide selects panel.wide. That folder must exist and contain a valid panel.cfg.
5. Install every supplied gauge dependency. Shared legacy .gau modules normally belong in [FS2004 root]\Gauges. XML gauges may be supplied as a .cab package or ordinary folder for either the panel folder or the shared Gauges folder. Follow the package instructions and do not unpack a cabinet that is meant to remain intact. Our detailed checks for missing FS2004 gauges and incorrect file locations cover these dependencies.
6. Remove accidental extra folder levels. FS2004 will not search recursively through mistakes such as Gauges\Gauges or AircraftName\AircraftName\panel. This often happens when an archive's top-level folder is copied without checking its contents.
7. Inspect panel.cfg. Entries under [WindowXX] and [VcockpitXX] must refer to installed gauges. In a reference such as Package!GaugeName, the text before the exclamation mark identifies the package and the text after it identifies the gauge inside that package. Each gaugeXX label should be unique within its section, and its position, width and height must be sensible. See our explanation of how to read and correct FS2004 panel and gauge entries before changing coordinates.
8. Check for a panel alias. A small panel.cfg may contain an alias= entry instead of its own gauge sections. The referenced aircraft and panel folder must still be installed under the expected path. Deleting a default aircraft can therefore break an add-on that borrows its panel.
9. Reload the aircraft properly. Close and restart FS2004 after replacing binary gauges or editing panel files. Merely switching views may leave part of the existing panel loaded in memory.

Why are the gauge screens black but the panel is visible?

Black glass displays with visible bezels usually indicate missing electrical power, switched-off avionics or display brightness set to minimum.

If analogue instruments work while radios, GPS units or electronic flight displays remain dark, concentrate on the battery, avionics bus, generators and brightness controls first. Test a fresh flight to rule out a saved electrical state.

If power is definitely available, the next suspects are a missing XML gauge package or FS2004's rendering configuration. Our black-instrument diagnostic guide explains how to separate an unpowered display from a missing gauge or Render to Texture problem.

Why do the 2D gauges work but the virtual cockpit remains blank?

When the 2D panel works, blank virtual-cockpit instruments point to the aircraft's [VcockpitXX] sections, VC textures, rendering settings or model rather than the shared Gauges folder.

Compare the gaugeXX references in the working [WindowXX] sections with those in [VcockpitXX]. The virtual-cockpit sections also depend on correctly mapped panel textures in the aircraft model; copying a working 2D section does not create a functional VC if the model lacks that geometry.

Confirm that FS2004's Render to Texture option has not been disabled when the cockpit depends on it. For a failure confined to that view, use our virtual-cockpit-only gauge and texture checks.

What if every FS2004 aircraft has blank gauges?

If default aircraft are also affected, repair the shared FS2004 installation rather than reinstalling individual add-ons.

• Close FS2004, back up modified files and restore original shared gauges and stock panel files using the installation media or its repair method.
• Check whether a recently installed add-on overwrote a stock file in the main Gauges folder. Restore the original version rather than copying in another simulator's gauges.
• Back up and temporarily rename the user fs9.cfg file, then start FS2004 so it creates a clean configuration. This resets preferences and may require controls and display settings to be configured again.
• Review security-software quarantine records for gauge modules removed during installation. Restore a file only when it came from the complete, trusted add-on package.

Do not replace PANEL.DLL merely because one aircraft has blank instruments. A core DLL fault normally affects stock aircraft too and may cause loading errors or crashes, not just a few empty gauge positions.

What should I check if it still doesn't work?

If it still doesn't work after reinstalling the panel, verify that FS2004 is reading the files you edited and that the gauges were actually made for FS9.

• Hidden file extensions: make sure the configuration file is really panel.cfg, not panel.cfg.txt, and that a cabinet has not become GaugeName.cab.zip.
• Protected installation folders: Windows may deny or redirect edits when FS2004 is installed under a protected programme folder. Reopen the file from the active aircraft directory and check its contents and modification time; an older copy in a compatibility or virtualised folder may be the one being changed.
• Duplicate aircraft folders: confirm that you edited the aircraft variant selected in FS2004. Near-identical folders left by separate installations are a common reason a correct edit appears to do nothing.
• Wrong simulator version: gauges built for FSX, Prepar3D or newer Microsoft Flight Simulator releases cannot be assumed to run in FS2004. Use the package's FS2004/FS9 edition.
• Missing supporting components: some classic panels require additional modules, sounds or runtime components installed by the original package. Commercial panels may also require their original installer rather than a manual copy of the aircraft folder.

The result of the stock-aircraft test remains the deciding factor: if stock gauges work, the add-on is incomplete, incompatible or incorrectly configured. If stock gauges are blank as well, restore FS2004's shared files and configuration before troubleshooting any individual aircraft.