Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 1081927" data-attributes="member: 62850">Since you are having this issue with both executables and scripts, my best guess is that you created a rule or custom folder that auto allows everything.&nbsp; It should tell you in the developer log why a file was allowed: C:\ProgramData\CyberLock\DeveloperLog.logBut if we are only considering scripts, you might be running the script from a text editor or IDE, in which case CyberLock is designed not to block these events, that way developers can use our software without it interfering with their workflow.&nbsp; That is, most novices and intermediate users do not use text editors or IDE&#039;s to write code.CyberLock has always been very capable in blocking all common, and even many lesser known scripts.&nbsp; With the new File Type feature, it covers even more scripts, but honestly it will not make a huge difference because most users do not have the additional script hosts on their machines, so the script would never run in the first place.&nbsp; But I figured, why not add them anyway, just to be safe, especially since CyberLock has this capability now.What are the file types of the scripts that are not being blocked?&nbsp; If the file type is not included in our new File Type feature, then I will probably add it.&nbsp; But I would be surprised if it is not already on the list.&nbsp; That is why I am thinking that you inadvertently wrote a rule that auto allows everything.</blockquote>

[QUOTE="danb, post: 1081927, member: 62850"] Since you are having this issue with both executables and scripts, my best guess is that you created a rule or custom folder that auto allows everything. It should tell you in the developer log why a file was allowed: C:\ProgramData\CyberLock\DeveloperLog.log But if we are only considering scripts, you might be running the script from a text editor or IDE, in which case CyberLock is designed not to block these events, that way developers can use our software without it interfering with their workflow. That is, most novices and intermediate users do not use text editors or IDE's to write code. CyberLock has always been very capable in blocking all common, and even many lesser known scripts. With the new File Type feature, it covers even more scripts, but honestly it will not make a huge difference because most users do not have the additional script hosts on their machines, so the script would never run in the first place. But I figured, why not add them anyway, just to be safe, especially since CyberLock has this capability now. What are the file types of the scripts that are not being blocked? If the file type is not included in our new File Type feature, then I will probably add it. But I would be surprised if it is not already on the list. That is why I am thinking that you inadvertently wrote a rule that auto allows everything. [/QUOTE]

Verification