---
title: "Why Does the Lasernet Developer Crash After Upgrading VMware?"
slug: "why-does-the-lasernet-developer-crash-after-upgrading-vmware"
updated: 2025-01-27T14:48:42Z
published: 2025-01-27T14:48:42Z
canonical: "kb.lasernetgroup.com/why-does-the-lasernet-developer-crash-after-upgrading-vmware"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Does the Lasernet Developer Crash After Upgrading VMware?

The Lasernet Developer may crash or fail to start due to a faulty VMware graphics driver. This is related to a VMware defect involving the **vm3dgl64.dll** file used by the OpenGL driver that is packaged with the VMware Tools 12.5.0.

Analysis of crash files provides the following result: `Access Violation exception in vm3dgl64.dll`.

To get the Lasernet Developer to start again, perform one of the following actions:

1. Revert to a previous working version of VMware.

OR
2. For Lasernet 10, start Lasernet without OpenGL by starting the **LnDeveloper.exe -noopengl** application using a command line from `\program files \formpipe software\lasernet 10`. An example is shown below:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-J1XB18OJ.png)

This solution can be used as a temporary method to validate if this is an OpenGL issue or a graphic driver issue, as the crash debug indicates.

OR

1. Install the Lasernet Developer on your local desktop and log in to the server remotely.

> [!NOTE]
> Note
> 
> - For Lasernet 9 and earlier, use the following solution: [Error when selecting Modules or Forms](/v1/docs/error-when-selecting-modules-or-forms)
> - Starting with Lasernet 10.10, all versions support the `-noopengl` parameter for **LnLogin.exe**.
> 
> **LnLogin.exe** is a commonly used application to start the Lasernet Developer to support synchronization of a version with the server.