Na głownej stronie tego programu znalazłem takie coś. Przetłumacz sobie:
If Tank Inspector crashes on start, or doesn’t run at all, while no sti.log file is generated and the dump folder is empty, it is very likely to be crashed into .NET Framework itself. We have received several reports of this situation. There are some known issues on .NET Frameworks 4.0 which might cause this problem, if you are not sure about how to get it fixed and you are not running under Windows XP, you can try to install .NET Framework 4.5 instead. Many issues in .NET 4.0 is fixed in it.
A crash might happen while loading data from your game client, if it is located in a folder which is not able to get a write access without an administrator privilege. This is caused by a mistake in coding, a piece of code requests a write access to the version.xml file of your game client, while all it does is to read the client version. This bug will be fixed in the next release. For now, there are two workarounds:
Copy your game client to a place where no elevated privilege is required to get a write access, and delete the %APPDATA%\..\Local\Smellyriver folder (just copy this path to your Explorer), so you can select the path of the client copy as Tank Inspector’s data source. OR,
Run Tank Inspector under administrator privilege, by right-clicking on Smellyriver.TankInspector.exe and select Run as Administrator.
A crash might happen while launching Tank Inspector, sometimes it might look like nothing happened when you run Tank Inspector. This is very possible to be tied to a known .NET Framework 4.0 issue. To solve this problem, Microsoft has provided a hotfix, which however has to be applied by you yourself. Here is how it works:
in your browser
accept to the terms if you are being asked
input your email address (twice) and the captcha
the download address to this hotfix will be sent to the email you provided, you can then download the hotfix and apply it.
A very rare crash might happen while launching Tank Inspector in a non-fully trusted place, such as a network shared folder. It might be caused by a known .NET Framework 4.0 issue, which could be fixed by applying a patch.