Why Does LizardTech GeoExpress Sometimes Crash in Remote Desktop or Virtualized Environments?

If LizardTech GeoExpress will not open or crashes on a remote computer, the graphics subsystem is often a contributing factor, especially when using Remote Desktop or virtualized environments.

Common graphics-related causes include:

1. Remote Desktop GPU Acceleration Issues

   
   

GeoExpress uses Windows graphics APIs for rendering parts of the user interface. When connecting through Microsoft Remote Desktop, the application may encounter problems if:

• Hardware GPU acceleration is unavailable.

• The remote session uses a generic display driver.

• OpenGL or DirectX features are not exposed to the session.

• The graphics driver on the remote machine is outdated.

Test:

• Log in directly at the remote computer's console and launch GeoExpress.

• If it works locally but not via Remote Desktop, the issue is likely graphics-session related.

2. Outdated or Incompatible Graphics Drivers

GeoExpress may fail to initialize properly if:

• The display driver is corrupted.

• Windows is using a Microsoft Basic Display Adapter.

• The GPU driver is significantly outdated.

Check:

• Open Device Manager.

• Expand Display Adapters.

• Verify that the correct NVIDIA, AMD, or Intel driver is installed.

• Update to the latest certified driver.

3. Virtual Machine Environment

If GeoExpress is running inside:

• VMware

• Hyper-V

• VirtualBox

• Citrix

• Azure Virtual Desktop

ensure that:

• 3D acceleration is enabled.

• GPU passthrough or vGPU is configured (if available).

• VMware Tools or equivalent guest additions are installed.

4. High DPI / Multi-Monitor Issues

Sometimes the application launches but appears off-screen or immediately closes.

Try:

• Disconnecting additional monitors.

• Setting display scaling to 100%.

• Lowering screen resolution temporarily.

5. Missing Runtime Components

The problem may appear graphics-related but actually be caused by:

• Missing Microsoft Visual C++ Redistributables.

• Damaged .NET Framework installation.

• Corrupted GeoExpress installation.

  
  

Try repairing or reinstalling GeoExpress.

6. Event Viewer Diagnostics

Check:

Windows Event Viewer → Windows Logs → Application

Look for:

• Application Error

• .NET Runtime

• Display Driver crashes

• Faulting module names such as:

  • nvwgf2um.dll

  • igd*.dll

  • atidxx*.dll

  • d3d*.dll

    
    

These often indicate GPU driver issues.

For GeoExpress Support Cases

Useful information to collect:

• GeoExpress version (e.g., 10.0.1)

• Windows version

• Local or Remote Desktop session

• Physical machine or VM

• Graphics card model

• Exact error message

• Whether the splash screen appears before the crash

If you can provide the GeoExpress version and the exact behavior (error message, crash, blank screen, etc.), I can help narrow down the specific graphics-card issue.