Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 1074303" data-attributes="member: 62850">Thank you for the info, there are a total of 2 bocks in your Developer Log.1)&nbsp; surunext.dll block - this is blocked because it is a Windows Control Panel applet that is not native to Windows.&nbsp; CyberLock is correct in blocking any non-native control panel applets.&nbsp; Simply allow the command line block once and you are good to go.&nbsp; I allowed this block on my test machine earlier today, and just to test, fired up that machine again, and it is being properly and automatically allowed.2)&nbsp; w32time block – same here, this item needs to be blocked and manually allowed by the user the first time it runs.&nbsp; It should not be blocked after that.All you need to do is to go into the Command Lines tab in CyberLock Settings and right click each of the two items and choose Allow one time, then they should be automatically allowed in the future.&nbsp; Or you can simply click allow in the user prompt when they are blocked.On a side note, I have to reset my whitelist and command lines quite often for testing purposes.&nbsp; Each time I do, I have to manually allow one command line block from the backup software I use.&nbsp; I could hardwire that item into CyberLock, but why add it if it only affects a small handful of users?We are both triggering SuRun the same (with a right click in Windows Explorer), so we are good to go there.If these are the only two blocks, then CyberLock is performing exactly as expected.&nbsp; In fact, if CyberLock did not initially block these two items, then your computer would not be properly protected.</blockquote>

[QUOTE="danb, post: 1074303, member: 62850"] Thank you for the info, there are a total of 2 bocks in your Developer Log. 1) surunext.dll block - this is blocked because it is a Windows Control Panel applet that is not native to Windows. CyberLock is correct in blocking any non-native control panel applets. Simply allow the command line block once and you are good to go. I allowed this block on my test machine earlier today, and just to test, fired up that machine again, and it is being properly and automatically allowed. 2) w32time block – same here, this item needs to be blocked and manually allowed by the user the first time it runs. It should not be blocked after that. All you need to do is to go into the Command Lines tab in CyberLock Settings and right click each of the two items and choose Allow one time, then they should be automatically allowed in the future. Or you can simply click allow in the user prompt when they are blocked. On a side note, I have to reset my whitelist and command lines quite often for testing purposes. Each time I do, I have to manually allow one command line block from the backup software I use. I could hardwire that item into CyberLock, but why add it if it only affects a small handful of users? We are both triggering SuRun the same (with a right click in Windows Explorer), so we are good to go there. If these are the only two blocks, then CyberLock is performing exactly as expected. In fact, if CyberLock did not initially block these two items, then your computer would not be properly protected. [/QUOTE]

Verification