New Update VoodooShield CyberLock 7.0

This version 7.83 keeps locking up my system after a few hours.
Not having issue at my end. Did you try doing a fresh install? @danb mentioned a lot of changes under the hood in his beta release post before this stable was released so you might try backing up your whitelist or just doing a complete fresh install which is what I did and haven't had any issue.
 
Not having issue at my end. Did you try doing a fresh install? @danb mentioned a lot of changes under the hood in his beta release post before this stable was released so you might try backing up your whitelist or just doing a complete fresh install which is what I did and haven't had any issue.
I uninstalled the old version (7.81), keeping all settings and configs, and installed the new version 7.83.
After experiencing the issue, I've manually cleared all logs and lists etc., still having issue.
I will uninstall, discarding everything, and reinstall fresh later.
 
I uninstalled the old version (7.81), keeping all settings and configs, and installed the new version 7.83.
After experiencing the issue, I've manually cleared all logs and lists etc., still having issue.
I will uninstall, discarding everything, and reinstall fresh later.
Before you uninstall and "discard everything" you might want to consider sending some of the logs to Dan for him to review.
 
Hi I'd like to try this product again ,is there a free version available?
It's a paid product but you can contact the dev and ask for a discount (he is a wonderful dev and will definitely help you get a fair deal if it's too expansive for your buying power)
But about free no it's not free there are alternative software you can use for free but cyberlock is a paid product
 
I spoke too soon yesterday. I still got locked up with CL fresh install. Today I was greeted with this message:
Cyberlock.png


Cyberlock Service is running:
Cyberlock service.png


Is there a button in the program to extract the logs? I looked around but couldn't find it. Or which files I need to get from the program folder? Thanks.
 
I think Cyberlock might somehow be impacting one of my Steam games. It's called Escape Simulator and I play it via multiplayer with my son. We've been playing it together for quite some time and it's never had an issue. Recently, there was some new DLC that I purchased/downloaded and installed. In the middle of playing the DLC, my game stopped responding and then I had to exit the game and go back in. Upon trying to re-enter the multiplayer game, I received an error code. Then, I tried hosting a multiplayer game and could not do that either. I have followed the recommendations on Steam to verify the installed files and rebooted multiple times. The only thing I can think of is that the new DLC might have triggered Cyberlock. Where can I look in Cyberlock to find if it has somehow blocked one of the game or Steam or DLC files?
 
  • Like
Reactions: simmerskool
Where can I look in Cyberlock to find if it has somehow blocked one of the game or Steam or DLC files?
VS Settings > User Log, and Program Data > DeveloperLog.log

BTW, What VS mode are you using? 🤔
 
VS Settings > User Log, and Program Data > DeveloperLog.log

BTW, What VS mode are you using? 🤔
I use Smart Mode>aggressive

Can you be a little more specific on where to find the developer log? Is it Windows or Users or the Cyberlock folder? The reason I ask is that I have a fairly small SSD C drive, so I install most of my programs onto my D drive (non-SSD).

EDIT: I found it along with several others that are old files. Can you remind me how to email that log to Dan?
 
Last edited:
  • Like
Reactions: simmerskool
Code:
support@voodooshield.com

Did you find anything blocking Steam or DLC in the VS User Log?
Yes, but I do not know how to interpret it or what to do about it?

Mono path[0] = 'D:/Steam/steamapps/common/Escape Simulator/Escape Simulator_Data/Managed'
Mono config path = 'D:/Steam/steamapps/common/Escape Simulator/MonoBleedingEdge/etc'
[PhysX] Initialized MultithreadedTaskDispatcher with 16 workers.
Initialize engine version: 2022.3.52f1 (1120fcb54228)
[Subsystems] Discovering subsystems at path D:/Steam/steamapps/common/Escape Simulator/Escape Simulator_Data/UnitySubsystems
[Subsystems] No descriptors matched for examples in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json.
[Subsystems] 1 'inputs' descriptors matched in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json
[Subsystems] 1 'displays' descriptors matched in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json
[Subsystems] No descriptors matched for meshings in UnitySubsystems/OculusXRPlugin/UnitySubsystemsManifest.json.
[Subsystems] No descriptors matched for examples in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json.
[Subsystems] 1 'inputs' descriptors matched in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json
[Subsystems] 1 'displays' descriptors matched in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json
[Subsystems] No descriptors matched for meshings in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json.
GfxDevice: creating device client; threaded=1; jobified=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1660 SUPER (ID=0x21c4)
Vendor: NVIDIA
VRAM: 5980 MB
Driver: 31.0.15.3640
Begin MonoManager ReloadAssembly
- Loaded All Assemblies, in 0.312 seconds
- Finished resetting the current domain, in 0.002 seconds
XRGeneral Settings awakening...
Fallback handler could not load library D:/Steam/steamapps/common/Escape Simulator/Escape Simulator_Data/MonoBleedingEdge/OculusXRPlugin
Fallback handler could not load library D:/Steam/steamapps/common/Escape Simulator/Escape Simulator_Data/MonoBleedingEdge/OculusXRPlugin.dll
Fallback handler could not load library D:/Steam/steamapps/common/Escape Simulator/Escape Simulator_Data/MonoBleedingEdge/OculusXRPlugin.dll
 
Yes, but I do not know how to interpret it or what to do about it?
What you post looks like the DeveloperServiceLog.log file. It isn't the user log in the VS UI. This is.
1735920659416.png It's the first place to look when you have blocks or other issues.

You'll want to email @danb the DeveloperLog.log file, not the DeveloperServiceLog.log.
 
  • +Reputation
Reactions: simmerskool
What you post looks like the DeveloperServiceLog.log file. It isn't the user log in the VS UI. This is.
View attachment 286986 It's the first place to look when you have blocks or other issues.

You'll want to email @danb the DeveloperLog.log file, not the DeveloperServiceLog.log.

There is nothing in the user log that shows as not allowed or blocked:

1735921622388.png