Jetson63

Reply to "Internal application error..." - Known Bug, but is there any permanent fix ? in Bug Reports Stardock Forums

I've tried everything KAV is offering but it was useless. Actually, KAV doesn't seem to block anything at all (no entry in the log, etc.). For instance, when I try to create a new script in DesktopX it crashes. Hence a new script is empty there can't be any dangerous content to block. I'll see what helpservice can do... Greetings Jets

Reply to "Internal application error..." - Known Bug, but is there any permanent fix ? in Bug Reports Stardock Forums

@Bichur Re-installing the scripting host software doesn't help (I tried that too). Registering the two dlls with regsvr32 is all you need to do. Everything is fine then until you start KAV because it re-installs the hooks and DesktopX will crash the next time it performs a call to one of the scripting dlls. Greetings Jets

Reply to "Internal application error..." - Known Bug, but is there any permanent fix ? in Bug Reports Stardock Forums

Basically, I agree with you, Bichur. KAV changes the registry entries, therefore it causes the trouble. On the other hand, I think this could be a general issue when using DesktopX and anti virus software. I assume other anti virus programs install similar hooks in the registry to catch calls to the vbscript.dll or jscript.dll - you already mentioned Norton. Even when script checking/blocking is disabled in KAV, the link to scr_ch_pg.dll will

Reply to "Internal application error..." - Known Bug, but is there any permanent fix ? in Bug Reports Stardock Forums

Hi, I'm having the same problem each time I try to open a script associated with a widget. I checked the windows registry and saw that my anti virus program (KAV 6.0) manipulates some entries for vbscript.dll and jscript.dll in the registry. In order to scan scripts for dangerous content, KAV re-directs calls to vbscript.dll and jscript.dll to a scr_ch_pg.dll that is located in the KAV installation directory. This feature can't be turned