Tech Support Guy banner

SpyShelter Protection Issue

1829 Views 15 Replies 3 Participants Last post by  commute201
Need reply from someone who's a knowledgeable user of the SpyShelter software which is for anti-kelogging and anti-screen capture. Today noticed the Keystrokes Protection item is disabled in the Protection tab of the most recent version of SpyShelter Premium 12.7 installed two weeks ago on my laptop and the toggle switch does not allow enabling it. All other items in the Protection tab are enabled including the Protection status item. Am unsure if the issue started with an earlier version of SpyShelter. Also have for security software on this Windows 7 32-bit system McAfee Total Protection v16.0 R31 Build 19.1.165 and Malwarebytes Premium 4.4.9. Troubleshooting tried so far which has not worked:
* Disabling SpyShelter momentarily and immediately reenabled with no effect on the issue.
* When installed the latest version earlier this month, I selected Keystroke Encryption even for East Asian languages, as normally do for each version update, which do not even use (English speaker).
* Uninstalled SpyShelter and chose the option to not save my Rules, restarted my PC, and reinstalled the latest version of SpyShelter again, but this time selected Keystroke Encryption only for other than East Asian language selecting only 1 of the 2 check boxes during the install. Restarted my PC again after the reinstall.
* SpyShelter support says I have a problem with SHA-2 signature recognition. At their suggestion, confirmed already have Microsoft Windows Updates KB4474419 and KB4490628 already previously installed.
* Installed remaining Microsoft Windows optional security updates at their support suggestion and restarted PC.
* Right clicked on SpyShelterKB.sys (right), its Digital Signature tab in Windows which says This digital signature is OK from DATPOL Janusz Siemienowicz on ‎Monday, ‎October ‎11, ‎2021 2:17:54 PM and Countersignature from Globalsign TSA for Advanced - G4 also on/at same date/time.

At this point with this all troubleshooting, SpyShelter support is clueless, except to rebuild my PC from scratch which is many hours or days of effort. Any other suggestions besides what already tried above?

If no other ideas to troubleshoot, any other anti-keylogging or anti-screen capture packages can try, as long as the annual subscription is under $100 (currently paying $35)? (With the exception of Zenama, which other software review sites had concern was in Turkey, in a somewhat unstable political region). I live in the USA.
See less See more
Status
Not open for further replies.
1 - 16 of 16 Posts
I used to use SpyShelter in Windows XP days and I thought the program was discontinued - good to see that it is still around.
As you know Microsoft support of Windows 7 has now ended but is it possible that you now have too much protection - too many security programs scanning/guarding any changes to the system in real-time, all tripping over each other as they try to protect the same system?

SpyShelter - McAfee Total Protection and Malwarebytes Premium 4.4.9, are all running at the same time.
Do you trust that McAfee is giving you Total Protection? Have you checked what that protection includes?
As a test, disable Malwarebytes from running and from running at startup, reboot the pc. What protection can you now enable in SpyShelter?
If there is a conflict between the layers of security, it is something that changed within one of the softwares recently that caused the issue, because as far as could see before all worked in harmony together. I would like to try your suggestion about temporarily disabling Malwarebytes, but only if I can find a way of disabling it for the next PC startup without having to totally uninstall the software. Checking and a Google search found nothing which steps listed that works for recent Malwarebytes software versions.

Agreeably can too have too much security software, but at same time time, had worked in the software security industry at one time, though not in the security department, but companywide they kept repeating the need for layered security, because one security package cannot catch every security threat. Many are duped thinking anti-virus software is all one needs. McAfee's Total Protection, a misnomer but still very good software that many cable companies deploy to their customers, product description as far can find does not mention anything about ransomeware and keylogging attacks protection, two of the worst malware attacks. Typical of many anti-virus software, they do not catch the majority of keylogging attacks. Malwarebytes has ransomeware protection, and SpyShelter and the like are focused on keylogging. Though not yet have had a ransomware attack, had a keylogging attack in 2002, an earlier internet time when protection software was not as advanced, and it took weeks to clean up.

Also agree at some point need to upgrade from Windows 7, but need to replace my computer first. To save money over a lifetime, I tend to run my electronics to the ground until there is strong need to replace them. And with the pandemic, computers having chips, unsure with that shortage how long will take to get a new device shipped, which typically buy online vs. even pre-pandemic, limited variety choices in local stores.

My gut feeling is SpyShelter issue have is something Windows related, but it is finding that needle in the haystack?
See less See more
Malwarebytes has ransomeware protection, and SpyShelter and the like are focused on keylogging.
If there is an effective way to block keyloggers then I would have thought that Malwarebytes, would be first in line to include it in their program - just a thought.
======
Are SpyShelter support aware that you are running other real-time protection software when you spoke to them?
As you realise and soon to come, the weakest part of your system will not be the virus-malware-keylogger programs that you have installed, but the operating system itself.
======
To check your system files - you could run system file checker.
Click on Start - Search - Type cmd
Right click on cmd select Run as Administrator.
At the Command Prompt - Type or copy and paste.
sfc /scannow
Press Enter.
Let it run to completion - but do not close the cmd window.
To save the log file.
Copy and Paste the following command in the Command Prompt.
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
Press Enter
On your desktop you will see a text file called sfcdetails.txt
See less See more
blues_harp28 - I ran the scan you suggested

****
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\USERS\SELFAD~1>cd\

C:\>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
****

I also ran a full scan with McAfee yesterday and Malwarebytes earlier this week, and no infections found.

I did let SpyShelter support know of my other security software. Their support of Windows software is limited like other software companies. They did refer to the event log, not offering to tell me where it is even when asked, but once I found the system log myself, I found the following entry in it:

The following boot-start or system-start driver(s) failed to load:
SpyshelterKb

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7026</EventID>
<Version>0</Version>
<Level>2</Level>
See less See more
Download MiniToolBox.
Place a tick in List last 10 Event Viewer Errors
Leave the tick in Only Problems.
Let it scan the pc - copy and paste the logfile below.

https://www.bleepingcomputer.com/download/minitoolbox/
======
Check and post the TSG System Information Utility - found here.
https://static.techguy.org/download/tsginfo.exe
Here you go. Note SpyShelter errors at bottom of log.

MiniToolBox by Farbar Version: 17-06-2016
Ran by Self Admin (administrator) on 28-10-2021 at 10:50:40
Running from "C:\Downloads"
Microsoft Windows 7 Home Premium Service Pack 1 (X86)
Model: Latitude E5530 non-vPro Manufacturer: Dell Inc.
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (10/28/2021 09:15:12 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 08:23:37 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 06:32:28 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.769]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.650]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.545]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.445]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.345]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.239]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.126]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

System errors:
=============
Error: (10/28/2021 10:04:34 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:33 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:32 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:32 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:30 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:30 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:29 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 10:04:29 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 09:17:26 AM) (Source: Service Control Manager) (User: )
Description: The McAfee SiteAdvisor Service service failed to start due to the following error:
%%2 = The system cannot find the file specified.

Error: (10/28/2021 09:15:19 AM) (Source: Service Control Manager) (User: )
Description: The McAfee SiteAdvisor Service service failed to start due to the following error:
%%2 = The system cannot find the file specified.

Microsoft Office Sessions:
=========================
Error: (10/28/2021 09:15:12 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 08:23:37 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 06:32:28 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.769]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.650]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.545]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.445]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.345]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.239]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.126]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

CodeIntegrity Errors:
===================================
Date: 2021-10-28 10:28:38.226
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:28:38.066
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:28:38.046
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:28:37.996
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:26:22.521
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:26:22.421
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:26:22.371
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:26:22.321
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:24:22.836
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 10:24:22.816
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

**** End of log ****
See less See more
The event viewer is showing some errors.
Error: (10/28/2021 09:15:19 AM) (Source: Service Control Manager) (User: )
Description: The McAfee SiteAdvisor Service service failed to start due to the following error:
%%2 = The system cannot find the file specified.
Date: 2021-10-28 10:24:22.816
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.
If Mcafee and SpyShelter are up and running all should-possibly, be OK.
The errors that are shown on startup in Event Viewer, come and go as the system is starting up and settling down and may not be on going problems.

I have just run MiniToolBox on my system and errors are showing there too.
Not sure of your next move - I will post back when I have other suggestions.
To see if it made any difference, just shortly ago today uninstalled (clearing rules also) and reinstalled SpyShelter again fresh from their website*after* doing additional Windows Updates yesterday. Same original issue exists.

Ran MiniToolBox again after what done in previous paragraph and immediately after PC bootup, with results below including new error message found. "Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. " Checked digital signature of the SpyShelterKb.sys file which says it is OK. Interesting?

MiniToolBox by Farbar Version: 17-06-2016
Ran by Self Admin (administrator) on 28-10-2021 at 11:43:39
Running from "C:\Downloads\UtilitiesOther"
Microsoft Windows 7 Home Premium Service Pack 1 (X86)
Model: Latitude E5530 non-vPro Manufacturer: Dell Inc.
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (10/28/2021 11:40:36 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:30:45 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:21:12 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:02:21 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 09:15:12 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 08:23:37 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 06:32:28 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.769]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.650]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog) (User: )
Description: STI BrtSTI: [2021/10/27 19:47:38.545]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

System errors:
=============
Error: (10/28/2021 11:43:32 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:43:31 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:43:31 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:43:30 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:42:24 AM) (Source: Service Control Manager) (User: )
Description: The McAfee SiteAdvisor Service service failed to start due to the following error:
%%2 = The system cannot find the file specified.

Error: (10/28/2021 11:42:07 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:42:06 AM) (Source: Schannel) (User: NT AUTHORITY)
Description: The following fatal alert was received: 70.

Error: (10/28/2021 11:41:31 AM) (Source: Disk) (User: )
Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Error: (10/28/2021 11:40:23 AM) (Source: Service Control Manager) (User: )
Description: The McAfee SiteAdvisor Service service failed to start due to the following error:
%%2 = The system cannot find the file specified.

Error: (10/28/2021 11:40:20 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
SpyshelterKb

Microsoft Office Sessions:
=========================
Error: (10/28/2021 11:40:36 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:30:45 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:21:12 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 11:02:21 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 09:15:12 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 08:23:37 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/28/2021 06:32:28 AM) (Source: WinMgmt)(User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.769]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.650]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

Error: (10/27/2021 07:47:38 PM) (Source: Brother BrLog)(User: )
Description: STIBrtSTI: [2021/10/27 19:47:38.545]: [00006488]: CUsbScnDev: DeviceIoControl() failed. ErrorCode = 5

CodeIntegrity Errors:
===================================
Date: 2021-10-28 11:38:41.398
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Date: 2021-10-28 11:38:41.382
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Date: 2021-10-28 11:28:59.523
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Date: 2021-10-28 11:28:59.507
Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Date: 2021-10-28 11:27:14.944
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 11:27:14.913
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 11:27:14.882
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 11:27:14.866
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 11:05:53.950
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

Date: 2021-10-28 11:05:53.903
Description: Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because the set of per-page image hashes could not be found on the system.

**** End of log ****
See less See more
"Windows is unable to verify the image integrity of the file \Device\HarddiskVolume3\Program Files\SpyShelter Premium\SpyshelterKb.sys because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source
If SpyShelter is now up and running then all files must have been found and loaded.
As a test, if you can run the pc without Malwarebytes running that will exclude a possible conflict between them.
My bad if my last comments confusing. SpyShelter's Keystrokes Protection item is still disabled and the toggle switch does not allow enabling it. If the software is otherwise working, then it has a broken toggle switch.

What have found since last post, have installed lightweight KeyScrambler by QFX 1.5 MB with keystroke encryption which installed on top of SpyShelter which left installed. So far, no conflicts. At no cost, works with browsers which confirm does with Firefox and MS Edge which is where I need most/nearly all of my keystroke encryption, or I may pay later to get this coverage for other applications.

Will see in the coming days, weeks, or months, will see where this goes. Have had past experience with broken software that somehow fixed itself with an update of itself or another software.
What have found since last post, have installed lightweight KeyScrambler by QFX 1.5 MB with keystroke encryption which installed on top of SpyShelter which left installed.
I'm unsure why you think these two programs installed over each other is going to protect your pc - it is likely to do the opposite.

If this was my pc and I wanted to keep using McAfee - Spyshelter and Malwarebytes, I would re-download all three programs to the desktop, disconnect from the internet and uninstall the existing programs one at a time.
Restart the pc after each program is uninstalled and one at a time reinstall them.
As a test, disable Malwarebytes from running and from running at startup, reboot the pc. What protection can you now enable in SpyShelter?
I did this. The Keystroke Protection item is still disabled in SpyShelter and the toggle switch does not allow enabled.

As an additional test while I had Malwarebytes disabled, I downloaded SpyShelter's security test which runs outside a browser. I also temporarily disabled KeyScrambler. With the SpyShelter issue, as expected, the keyboarding logging test failed and I could see what I had typed in the browser. I then reenabled KeyScramber and ran the same SpyShelter security test, when I typed something else in the browser, the results came out gibberish in the security test. So the test worked for KeyScramber, but not for SpyShelter.

KeyScrambler uses SHA-2 signature recognition per their FAQ as well as SpyShelter. With the MiniToolBox test, this suggests something else is going on with the SpyShelterKb.sys file, but I am unsure what and/or how to address it.
commute201,

I've edited your post to use the quote tags which is the preferred method when replying to a specific point from another member. Otherwise, it's too confusing to see who said what. An easy way to do it is use your cursor to highlight the text you want to quote and click on Reply from the drop down menu. Then just type your response after what already appears in the text reply box. :)
So the test worked for KeyScramber, but not for SpyShelter.
So are you saying the Spyshelter failed the very test set by, Spyshelter?
When you installed both KeyScramber and SpyShelter, their own keylogging definition files are now installed on your system.
Each program is attempting to protect your system but may be tripping over each other and also could be seeing the other programs definition files, as a threat.
In some cases, two is not better that one. Decide which works best for you and remove the other.
As in The Apprentice TV show airing here in the States USA a few years ago, I fired SpyShelter software (uninstalled) as could not troubleshoot it. I found an alternative solution.

Sent from my Android
1 - 16 of 16 Posts
Status
Not open for further replies.
Top