Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
I had an interigty client running for several moths under windows 10 without any significant problems.
Now it happens that if the gui should open a dialog for selecting something from the local filesystem
(eg add members, create sandbox, File->Compare Files...)
the gui and IntegrityClient.exe crash without any exeption dialog.
The gui diasappears and process IntegrityClient.exe get terminated.
So far I did not notice any other functionality beeing affected.
(eg I can still create sandboxes from commandline)
I tried uninstalling and reinstalling the client (WIN XP SP3 compability) but the problem persists.
I also tried deleting the .mks folder from User Profile directory with no success.
The only other traces of the crash I stumbled upon where some JAVA hs_err_pid???.log files.
Some extracts from such a file:
# Java VM: Java HotSpot(TM) Client VM (20.45-b01 mixed mode, sharing windows-x86 ) # Problematic frame: # C [MSVCR71.dll+0x10440] ...Stack: [0x0a130000,0x0a170000], sp=0x0a16f658, free space=253k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [MSVCR71.dll+0x10440] wcslen+0x4 j sun.awt.shell.Win32ShellFolder2.access$800(JJI)Ljava/lang/String;+4 j sun.awt.shell.Win32ShellFolder2$14.call()Ljava/lang/String;+15 j sun.awt.shell.Win32ShellFolder2$14.call()Ljava/lang/Object;+1 j java.util.concurrent.FutureTask$Sync.innerRun()V+30 j java.util.concurrent.FutureTask.run()V+4 j java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Ljava/lang/Runnable;)V+66 j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+33 j sun.awt.shell.Win32ShellFolderManager2$ComInvoker$3.run()V+7 j java.lang.Thread.run()V+11 .... |
Does anybode had a similar problem and found a solution?
Maybe also a detailed procedure description of some kind of "deep" uninstall
(wg sandbox registry, ...)
might also help.
Solved! Go to Solution.
It turned out that the crash was because a god mode link on the desktop.
Just google GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
The precense of a god mode link in a directory was sufficient for the error to occur.
In win10 directory and file selection dialogs contain a link to the destop, and I suppose
this (and the java version 10.4 uses) was the reason that it always crashed.
My enthusiansm for tweaks is dramatically degraded now 🙂
Hi Klaus,
It seems a fluke that a 10.4 Integrity client was working that long, on Windows 10, as Integrity client wasn't supported on Windows 10, until our Integrity 11.0 release, as changes to both the Integrity client, and the underlying Java JRE (Oracle Java also needed to be updated) were needed to support Windows 10.
It turned out that the crash was because a god mode link on the desktop.
Just google GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
The precense of a god mode link in a directory was sufficient for the error to occur.
In win10 directory and file selection dialogs contain a link to the destop, and I suppose
this (and the java version 10.4 uses) was the reason that it always crashed.
My enthusiansm for tweaks is dramatically degraded now 🙂