The application failed to initialize properly

Reported Fault

"The application failed to initialize properly(0xc0000005). Click on OK to terminate the application"

Symptoms

1. kwiklook runs on the kwiklook Server computer but won't run on Client workstation. The above error message appears.

Cause

1. An older version of kwiklook is installed.
2. Your workstation does not meet the minimum requirements of kwiklook.
3. Windows Program Compatibility Assistant (PCA) is stopping kwiklook from running successfully.
4. Symantec Endpoint Protection causes issues with applications.
5. Sophos Endpoint Protection causes issues with applications.
6. The Domain Group Policy causes issues with applications on Windows 7 and Vista workstations.
7. DEP (Data Execution Prevention) causes issues with applications.
8. The computer does not have sufficient memory (RAM), has faulty memory (RAM), or is missing a Windows component (faulty Windows installation).

Remedy

1. Upgrade kwiklook to V4.4.0.092 or later. Check your version of kwiklook by clicking Help > About.
2. Check that the workstation meets the kwiklook minimum requirements.
3. Check the Windows Registry for an entry that can cause kwiklook to stop working:
   1. Click 'Start > Run' (or 'Start > Search Programs and Files' in Windows 7).
   2. Type in 'regedit' and press enter.
   3. Expand 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags'
   4. Delete all entries that contain the keyword 'kwiklook'.
   5. Close the Registry Editor and test running kwiklook again. You may need to follow these steps while logged in as each Windows Users that uses the workstation.
   6. For more information please view the Microsoft Support article.
4. Uninstall Symantec Endpoint Protection, or install kwiklook on a different hard drive partition or USB stick.
5. Uninstall Sophos Endpoint Protection, or install kwiklook on a different hard drive partition or USB stick.
6. Install kwiklook or leecareplus on the different partition (or USB stick) on the client workstation.
7. Log into the workstation as the Domain Administrator and test running kwiklook. If kwiklook runs successfully when logged into the workstation as the Domain Administrator then your Domain Controller settings may be stopping your non-administrator users from running kwiklook successfully.
8. Check the kwiklook Database Connection Parameters to make sure that the SQL Server Connection Parameter uses the IP Address of the SQL Server instead of a UNC path.
9. Run Memtest to check for faulty RAM on the workstation.
10. Remove the workstation from the Domain.
11. Turn Data Execution Prevention off.
12. Re-load Windows on the computer.