As soon as Enscape attempts to launch immediate crash.
The issue you’re encountering occurs when the Microsoft Visual C++ runtime installed on the system does not meet Enscape’s minimum required version. This most often affects users in enterprise or managed IT environments and is commonly linked to Fiery printer drivers or, in some cases, Ricoh camera software.
When these drivers are installed or reinstalled, they can copy an extremely outdated version of the Microsoft Visual C++ runtime file msvcp140.dll into the Windows System32 folder, overriding the newer, Microsoft-supported runtime that Enscape and other modern applications require. Reinstalling Microsoft Visual C++ runtime with a newer version resolves the problem, but the issue often reoccurs when Windows Updates or automated driver maintenance are performed, as these can silently reinstall the same driver and overwrite the correct runtime with the outdated file once again.
You can find more technical details about this conflict on the Enscape forums and Fiery communities.
Please follow the steps below to resolve this issue:
- Ensure your graphics card driver is up-to-date.
- First, check what graphics card you have using the Windows Task Manager.
- For NVIDIA GPUs: Download drivers manually or use the NVIDIA application.
- For AMD GPUs: Download drivers manually or use AMD’s Auto-Detect & Install application.
- First, check what graphics card you have using the Windows Task Manager.
- Log in to your Chaos account and download and install the newest version of Enscape, if you haven’t already.
- With the latest version of Enscape installed, repair the required C++ package by running the file located at: “C:\Program Files\Enscape\redist\VC_redist.x64.exe”
To clarify, this issue is not caused by Enscape - Enscape is simply affected by the state of the Microsoft Visual C++ runtime available on the system. In many cases, Enscape appears to be the only affected application because it is one of the few programs on the system that depends on this specific runtime version.
While reinstalling or repairing the Visual C++ redistributable can temporarily restore functionality, the underlying cause remains external to Enscape. If Windows Updates or third-party drivers continue to reinstall outdated runtime files, the issue will recur. For a permanent resolution, this behavior must be addressed at the system or IT policy level to prevent the runtime from being overwritten again. If this issue is determined to be caused by a Fiery driver, we recommend contacting their support directly for further assistance.