CyberLock 9.0

  • Thread starter Thread starter danb
  • Start date Start date
  • Featured
update to last re CL 9.06, I noticed today looking at taskmanager that Cyberlock was reading "very high" power usage in the processes tab, and it seemed to continue for longer than I thought it would, then notice the integrated SiriusGPT last scan took 149.17 seconds, which seems like a lot a time as IIRC there was not much going on in win10, unless perhaps something like 0patch was updating or had just updated...?? is there a "normal" sirius scan time?
 
Hey Guys!

Here are the latest versions, we will probably be releasing these to the public this week. Please let me know if you find anything we need to fix.

CyberLock 9.09
SHA-256: 87817e5bc83110d9a781d711f066061c3cc215ea1348a6e44d3492553f378090

SiriusGPT 1.09
SHA-256: 9e8c63066ea6a3366b1f529a4dc307ca09dedf69b4da4bf52cd320a091328d31

SiriusLLM 1.09
SHA-256: 9da2c075a63d6e5d65db7d4f9a6a96f2c99a64908899dc260993e42d8dbb948f

DefenderUI 2.09
SHA-256: aa10538c9427cb1784fcdb9ad8a3c745f5b0ae5f3c4d2ca321d779236181afd4

DefenderUIPro 2.09
SHA-256: 7fcf69ca7d119610771e889ab562fb83b2e61cfdac25f24889f9b5133c6dfb40

DefenderUISilent 2.09
SHA-256: 753c2d98dac95da1001e58d4646d9ba67a5196c6b2956ad36aedbb34310f3e6c

WDAC Lockdown 2.09
SHA-256: 20ba9a7e871735d51f2c2bda6d3128594427e6be8a21d805d064beedaa6b0b5a

DefenderUIARM64 2.09
SHA-256: d278740ac3a07ee76d93dd4128d471d4008d037f8f4199109cc2e62374665a62

Thank you guys!
 
I notice that all the executables have been updated from versions #.06, released on 3rd May CyberLock 9.0 to versions #.09 so not with the usual numeric progression of the previous releases. It's not relevant but I wonder why.
 
Last edited:
  • Like
Reactions: simmerskool
I notice that all the executables have been updated from versions #.06, released on 3rd May CyberLock 9.0 to versions #.09 so not with the usual numeric progression of the previous releases. It's not relevant but I wonder why.
Yes, I have been working on getting the 139 potentially malicious file extension blocks feature to work exactly how we want it to. So the last few versions have been mainly focused on that. They have been small but significant changes because it was important that we got it right. I am quite certain it is 100% correct in #.09, so I think we are good to go for a public release.
 
Hey Guys,

We have released all of our updated products to the public and have enabled the auto update for all products.

This version had a small command line fix, that was the only change.

CyberLock 9.10
SHA-256: a4d364609939de6e751e9edeb20545a7a2c65bc73f5765454bd7496f03ed9b99

SiriusGPT 1.10
SHA-256: 8a6dcecb843906cb0153ec1d3faada128197c5f0d01dbf75e8c6a25b27c3351e

SiriusLLM 1.10
SHA-256: 08070415a1bfd55e045610a0d37e3770a9442e54a2bd04b322099954c6c74645

DefenderUI 2.10
SHA-256: a65796609998aa5ddf37ce23de2890732e3b25902f46c8d0dbbb0c10f4e230b6

DefenderUIPro 2.10
SHA-256: 29c72f097824c162e1953e2c575754147ab60a11d09cf482c3a29aece41f549a

DefenderUISilent 2.10
SHA-256: 623296ede52e6332f55506ccd1354a37539c9bc82ea2c280250b7234b04af9b9

WDAC Lockdown 2.10
SHA-256: ff39b818292f2e2977e8422e03b8f00d4322e8d2a6161e5c07f0012fd14249cb

DefenderUIARM64 2.10
SHA-256: 9b02a45949d82e47ddcd651ca0c8cdc26655b4440398ae9f5ab78265386732c0


Thank you guys!
 
Hey Guys,

We have released all of our updated products to the public and have enabled the auto update for all products.

This version had a small command line fix, that was the only change.

CyberLock 9.10
SHA-256: a4d364609939de6e751e9edeb20545a7a2c65bc73f5765454bd7496f03ed9b99

SiriusGPT 1.10
SHA-256: 8a6dcecb843906cb0153ec1d3faada128197c5f0d01dbf75e8c6a25b27c3351e

SiriusLLM 1.10
SHA-256: 08070415a1bfd55e045610a0d37e3770a9442e54a2bd04b322099954c6c74645

DefenderUI 2.10
SHA-256: a65796609998aa5ddf37ce23de2890732e3b25902f46c8d0dbbb0c10f4e230b6

DefenderUIPro 2.10
SHA-256: 29c72f097824c162e1953e2c575754147ab60a11d09cf482c3a29aece41f549a

DefenderUISilent 2.10
SHA-256: 623296ede52e6332f55506ccd1354a37539c9bc82ea2c280250b7234b04af9b9

WDAC Lockdown 2.10
SHA-256: ff39b818292f2e2977e8422e03b8f00d4322e8d2a6161e5c07f0012fd14249cb

DefenderUIARM64 2.10
SHA-256: 9b02a45949d82e47ddcd651ca0c8cdc26655b4440398ae9f5ab78265386732c0


Thank you guys!

I wish this program had the capacity to disable Ms Defender. At least as a choice.
 
I wish this program had the capacity to disable Ms Defender.
Hello,
I don't know if Dan wants to implement this feature as DefenderUI is a front-end for MS Defender so disabling it it's not the purpose of this software. If you wish to disable MS Defender this guide could be useful for you, maybe. Disable Microsoft Defender Antivirus on Windows 11 Safely
Anyway disabling MS Defender isn't a easy task and it's rather risky, I think.
The other softwares (CyberLock, WDAC Lockdown, SiriusGPT, SiriusLLM) provide added cybersecurity and they are complementary to an antivirus but they don't replace it, in my opinion, so I guess that a option to disable MS Defender will not be implemented.
Also from this post by Dan CyberLock 9.0 "the best use case for our products is serving as a pre‑execution filter for traditional antivirus or EDR solutions."
 
Last edited:
  • +Reputation
Reactions: ErzCrz
I wish this program had the capacity to disable Ms Defender. At least as a choice.
Never gonna happen. Cyberlock has nothing to do with Defender.

And it makes no sense that Dan would include a "Disable Defender" feature in DefenderUI when its whole purpose is to configure Defender.