Compatibility troubleshooter in Windows 8

When I used NX Client on my Windows 8 Pro 64-bit computer, I was getting the following errors and I finally found a way to fix it.  I’m posting it here hoping it would save other people the trouble of finding a solution.


The error message I was getting from Reliability Monitor was this:


Basically, whenever I started NX Client, I would get these errors (see box in green with rows stating “NXWin.exe  Stopped working”).

Left clicking on any of the rows, it shows this:


Stopped working

‎8/‎2/‎2013 5:51 PM

Report sent

Faulting Application Path:    C:\Program Files (x86)\NX Client for Windows\bin\NXWin.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    NXWin.exe
Application Version:
Application Timestamp:    4fc77b52
Fault Module Name:    HsSrv.dll
Fault Module Version:
Fault Module Timestamp:    4f064d85
Exception Code:    c0000005
Exception Offset:    0000b481
OS Version:    6.2.9200.
Locale ID:    1033
Additional Information 1:    4125
Additional Information 2:    4125b231bd3ddf9861e263612899c963
Additional Information 3:    a667
Additional Information 4:    a6676e506b7760b265f7e9897a1ec304

Extra information about the problem
Bucket ID:    70197882306108d625b9ca84af3fdad5 (-1102094631)


The solution I found was to run a built-in Windows 8 program called Compatibility Troubleshooter. This program isn’t started by simply typing the words “Compatibiilty Troubleshooter” in the Windows 8 Start Screen.  You have to find the applications executable (i.e., files with the “.exe” extension) and right-click on it.  Let me show you how this is done.  I’ll use my failing NX Client program as an example.

First, find the application’s executable file.  For NX Client, I type “NX Client” on the Start Screen


Right-click on the the program and a task bar on the bottom of the screen shows up.


Left-click on Open File Location.  This is so that I can go the the directory where the program is located.


After left-clicking on Open File Location, Windows 8 starts Explorer on the Desktop and displays the directory where the program can be found.


Right-click on the program to show a drop-down menu, then left-click on “Troubleshoot compatibility”


Windows 8 will begin to figure out what the best settings are to run the program..


Once Windows 8 figures it out, left-click on Try recommended settings


Windows 8 offers you the option the try out the new settings by left-clicking on the button labeled Test the program.


I didn’t show a screenshot of the program actually running.  However, I know the problem went away in Reliability Monitor because normally another row of “NXWin.exe  Stopped working” would show up at the same time as I would run NX Client.  If the program wasn’t working properly, we would see an entry stating “NXWin.exe   Stopped working at today’s date on 6:06 PM”.  But since it didn’t show up, I know the problem has been fixed.


Now that things are working fine, left-click on Yes, save these settings for the program.


And last of all, left-click on Close the troubleshooter.


That’s it. 

I’m really glad someone at Microsoft thought this one up and created it.  I hope you find this useful and have a good day!

Event Log Red Herring Alert (ERHA) –InitialFirewallConfig.wfw

From time to time, I check my Windows 8 Event Logs to see what’s going on with my system and the applications that I run.  One Error that showed up was this.


…the General tab provides more detail and it reads this…

Function: fileExists
File: .\Utility\sysutils.cpp
Line: 500
Invoked Function: _tstat
Return Code: 2 (0x00000002)
Description: The system cannot find the file specified.

File: C:\ProgramData\Cisco\Cisco AnyConnect VPN Client\InitialFirewallConfig.wfw
Error: No such file or directory

I noticed that it would happen whenever I started running a program called Cisco Any Connect VPN Client.  Scouring the internet, I couldn’t find any useful information about it.

I created an empty file with the same name in the C:\ProgramData\Cisco\Cisco AnyConnect VPN Client directory and restarted Cisco Any Connect VPN Client.  Lo’ and behold, the file disappeared.  It appears that it is a file that Cisco Any Connect VPN Client needs at startup then removes.  Cisco Any Connect VPN Client still runs with or without this file so I think its messy programming to have an Error be logged in the Event Log.

I posted this for others to see that this file is really not that important and neither is the Error.

Good luck!