There are times that you may need to install an older Windows application especially something developed using Visual Basic 6 or earlier. In these cases, you should always ensure that the installed application is using the most current common control library available from Microsoft. If not, you may receive strange error message that logs the following in the Event Viewer (abbreviated exception):
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Log Name: Application Source: Application Error Date: 07/08/2013 11:10:57 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: my-msft-surface Description: Faulting application name: TestComControls.exe, version: 220.127.116.11, time stamp: 0x4cb60c27 Faulting module name: comctl32.ocx, version: 18.104.22.168, time stamp: 0x3802598b Exception code: 0xc000041d Fault offset: 0x00020f51 Faulting process id: 0x858 Faulting application start time: 0x01ce7bed4062ea40 Faulting application path: C:\Program Files (x86)\Test\TestComControls.exe Faulting module path: C:\Windows\SYSTEM32\comctl32.ocx Report Id: 96a08c71-e7e0-11e2-be6c-6045bd92f0bd Faulting package full name: Faulting package-relative application ID:
On most Windows 8 machines, the application worked correctly. However, in the case of a touch device such as our Microsoft Surface Pro, whenever we used touch or the pen for input, this error would occur. So, in this case, we needed to update to the latest COM controls. These were found at http://www.microsoft.com/en-us/download/details.aspx?id=10019.