Hello everybody,
can someone reproduce that the (File) Explorer crashes when accessing .dll/.exe/.ico files if their name is exactly two characters long?
If CATIA V5 from Dassault Systemes is installed in an AppStack, I can't open "Programs and Features" because the registry value "DisplayIcon" of CATIA refers to the file "C:\Program Files\Dassault Systemes\B26\win_b64\resources\graphic\icons\DS.ico".
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Dassault Systemes B26_0]
"DisplayIcon"="C:\Program Files\Dassault Systemes\B26\win_b64\resources\graphic\icons\DS.ico"
If FormingSuite 2018 from FTI is installed in an AppStack, the Explorer crashes because the installer creates a shortcut on the desktop that refers to the file "C:\FTI\FormingSuite\FS.exe".
We do see this issue.. File explorer is crashing when appstack (app volume 2.14) is attached. Any fix or work around is much appreciated.
maharajan.be My workaround using Catia as an example:
Resolved our issue after enabling "Launch folder windows in a separate process"
The error seems to be caused by the Horizon Agent scanner redirection/FabulaTech Isolation driver. The Problem is gone if you add "*\explorer.exe" to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ftsjail\ExcludeProcesses".
How were you able to update that registry key?
I've tried "explorer.exe" and "*\explorer.exe" at the beginning and at the end but no matter what it gets removed when I reboot the system.
Hello hermanc01,
I just added the value at the end of the list. That's all I can tell you.
This worked for me. Another answer is to not install scanner redirection or serial port redirection. Installing either of these will install the isolation driver. There is a property when installing named FT_INSTALL_JAIL that I tried to set, but it was overridden.
Hi! I think this would not happen if the redirection was done using software, not hardware. I used the usb over ethernet program for webcams and I did not have a similar problem. Most of all, it was a direct action.
Hello everybody,
this problem should be fixed with next upcoming minor release of Horizon.