APPLICATION

TROUBLESHOOTING GUIDE
Release Note

Cimatron 14
Table of Contents
Introduction ............................................................................................................................... 3
Issue: Cimatron cannot start ..................................................................................................... 3
Cause 1: Programs injecting their DLLs into all programs during their load process ............ 3
Analysis: ............................................................................................................................. 4
Solution:............................................................................................................................. 6
Cause 2: Another program switching a Registry Key value ................................................... 8
Solution:............................................................................................................................. 8
Cause 3: Protection Packages, Antivirus, AntiLoggers (E.g. - Zemana AntiLogger) ............... 9
Solution:............................................................................................................................. 9
Example: ............................................................................................................................ 9

Application Troubleshooting Guide I

Introduction

Issue: Cimatron cannot start

Cimatron cannot start and one of the following error messages is displayed:

 The application was unable to start correctly (0xc0000142). Click OK to close the
application.
 The application was unable to start correctly (0xc0000005). Click OK to close the
application.

OR

Cimatron cannot start, but no error message is displayed.

OR

Cimatron does start, but no text shows up (Menu, Toolbar…).

Cause 1: Programs injecting their DLLs into all programs during their load
process
The common cause for Cimatron load failure is related to programs injecting their DLLs,
using the old Windows injection mechanism AppInit, into all windows programs during their
load process, disrupting the order of the application loaded DLLs. (The windows loader gets
tricked into initializing DLLs out of order).

Only a small set of legitimate applications uses this mechanism. Unfortunately, a larger set
of malware and malicious software uses this mechanism to hook their APIs.

Using AppInit, DLLs can unintentionally cause system deadlocks and performance problems,
because they are loaded during the initialization of user32.dll. Due to the potential threats
that AppInit infrastructure brings in, Microsoft strongly discourages its usage. (See KB
197571, which clearly explains this problem with windows 7/2008).

This problem is related to all operating systems older than Windows 8. Windows 8 adopted
UEFI (Unified Extensible Firmware Interface) and secure boot that, when enabled, disables
the AppInit_DLLs mechanism, to protect customers against malware and threats.

Microsoft’s recommendation for Operating Systems older than Windows 8, is to remove the
offending DLLs from the AppInit registry or to uninstall the related Software.

Application Troubleshooting Guide 3

Analysis:
In order to check if there is Software that conflicts with Cimatron, activate the Cimatron
Control Panel, select the Utilities tab and run the Software Conflict Test.

Application Troubleshooting Guide 4

The Software Conflict Test dialog is displayed:

Press the “Check Now” button.

If no conflicting software is found, the following message will appear:

If conflicting software is found, the following windows error will appear:

In addition, a list of problematic files is displayed:

Application Troubleshooting Guide 5

Solution:
To help troubleshoot and determine what Software is conflicting with Cimatron, the
Microsoft Autoruns utility should be used.

1. Download and install Autoruns.

2. Start Autoruns.
3. Start Cimatron.
4. Select the AppInit tab in the Autoruns window.

5. Review the DLL files listed and locate them based on the listed paths.
6. Rename the DLLs, one by one, testing the program startup after each change to try
to isolate the problematic DLL.
7. Once you have traced the DLL causing the conflict, trace the software that installed
it using the following procedure:
a. Right-click the DLL name, select the Properties option and switch to the
Details tab.
b. Look for the DLL name in the Internet.

Application Troubleshooting Guide 6

Known conflicting software and suggested solutions:

 NVIDIA drivers (a very few specific ones) - Visit the NVIDIA

website (www.nvidia.com) and update the drivers for your
graphics card.
 Adobe Acrobat 9 Pro Extended – Uninstall the program or
rename the following DLLs:
o C:\Windows\System32\acapture64.dll
o C:\Windows\SysWOW64\acapture32.dll
Alternatively, you may uninstall the "Adobe Acrobat 9 Pro
Extended 64-bit Add-On". On 32-bit systems, modify the Adobe
Acrobat 9 program to not have the "Capture CAD Modules"
installed.

 BeyondTrust - Uninstall the program or rename the btpload.dll/

btpload64.dll.
 Medusa - Uninstall the program or rename the
C:\Windows\System32\MdsDxgk.dll.
 The following programs are Malware/Adware/Spyware and
better be uninstalled (some are not simple to uninstall, check
the web for guidelines).
o Search Protect
o SW booster
o Smartbar
o iLivid Toolbar
o Searchqu toolbar

Application Troubleshooting Guide 7

Cause 2: Another program switching a Registry Key value
If the previous method didn’t solve the error, a different program may incorrectly be
switching the following registry key from 0 to 1.

Changing the value of the following registry key to 0 may help:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Windows\LoadAppInit_DLLs

Solution:
1. Press WINDOWS-R on the keyboard to bring up the Run window.
2. Type in REGEDIT and click OK.
3. In the Registry Editor, expand the various levels until you reach the Windows key
highlighted in the path above.
4. On the right side of the editor, double-click the LoadAppInit_DLLs value.
5. Change it to 0, and click OK.
6. Exit the Registry Editor, and restart the computer.
Note: Some applications may change that value back to 1 after they are launched!

Application Troubleshooting Guide 8

Cause 3: Protection Packages, Antivirus, AntiLoggers (E.g. - Zemana AntiLogger)
There are a variety of products in use that either lock down program access outright, or try
to prevent malicious software from running. The parameters that companies use to
determine inappropriate system access can vary greatly and could possibly affect specific
programs on your machine from running.

Solution:
Review the applications of this variety that may be installed, checking to see if there are
allowable exceptions in the coverage.

Example:
An example of a potential Cause 3 problem is the file DpoFeedb.dll.

DpoFeedb.dll is a process known as DigitalPersona OTS Feedback and can be installed by

different software such as DigitalPersona Pro or DigitalPersona Personal or Dell Data
Protection Security Tools or HP Client Security Manager or HPAsset component for HP Active
Support or DigitalPersona Fingerprint Software or Adobe Premiere Elements (version 10 HD)
or HP SimplePass Identity Protection.

DpoFeedb.dll is able to record keyboard and mouse inputs. Therefore, the technical security
rating is 49% dangerous. Some malware has been known to camouflage itself as
DpoFeedb.dll.

It is recommended to check the DpoFeedb.dll process on your PC to see if it is a threat:

https://www.file.net/process/dpofeedb.dll.html

If you have tried all of the above solutions and Cimatron still does not start, try renaming the
DpoFeedb.dll and restarting the computer. If Cimatron still does not start, rename the file
back to its original name and restart the computer again.

Application Troubleshooting Guide 9