[BobScott49]

No joy with keyappID

 

Farbar Recovery Scan Tool (x64) Version: 08-01-2020
Ran by Bob Scott (11-01-2020 10:50:55)
Running from C:\Users\Bob Scott\Desktop
Boot Mode: Normal

================== Search Files: "keyAppID" =============


====== End of Search ======

 

Farbar Recovery Scan Tool (x64) Version: 08-01-2020
Ran by Bob Scott (11-01-2020 10:50:55)
Running from C:\Users\Bob Scott\Desktop
Boot Mode: Normal

================== Search Files: "keyAppID" =============


====== End of Search ======

 

Lots of logs here

 

 

 

 

Here's the activity_log.log

 

 

[Advertisements]

Sorry the activity_log.log won't upload to this reply so doing it this way

 

https://send.firefox...wxeLJVPLcyGIc2w

 

 

[BobScott49]

Sorry the activity_log.log won't upload to this reply so doing it this way

 

https://send.firefox...wxeLJVPLcyGIc2w

 

 

[BobScott49]

Also not sure if you wanted to see these:

 

 cryptog.reg   538bytes   162 downloads

 

 Type001.reg   488bytes   180 downloads

[RKinner]

We are going to leave the house in a few minutes.  Probably going to be gone all day.  Taking the grandkids to something about 30 miles south of here.

[BobScott49]

Have a good day

[RKinner]

No idea where the key is so I think you need to get the person in charge of this junk to reinstall it.  Perhaps McAfee ate the key.  I would remove or uninstall the programs we ran before you let them reinstall.  Don't think anything will interfere but they might not understand what we were trying to do.  Let me know how it goes.

 

I searched for info on the software but there isn't much.  I did find this:

http://help.e-safesy...tion=show&cat=0

Appears to be the manual for the server that your guard ware client talks to.  Interesting that the client also can do keylogging.

[BobScott49]

There's a bit of a problem there in that they will want to know why I am asking them to reinstall it, i.e. how would I know that the e-safe thing isn't working unless I've been messing with it, which I am definitely not allowed to do! 

 

So I need to think about that one

[RKinner]

Show them the vew output?  Process explorer log?

[BobScott49]

The VEW output is a good call.  Bear in mind I'm not a techie, hence I came to you. 

Would I be okay telling them I looked at VEW because the pc was slow and I wanted to see if I could see what was causing it and it looked like it was the GuardwareProxy?

[RKinner]

Sounds good to me.

[BobScott49]

Okay well it's that or just ignore it and assume I don't know there's something wrong!  Just to put my mind at rest, nothing we have done has caused the problem, right?

[RKinner]

It was broken when we started.  Go back to your first post and look at the bottom of Addition.txt.
 

 

System errors:
=============
Error: (12/23/2019 05:50:09 PM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The GuardWareProxy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: (12/23/2019 05:50:09 PM) (Source: Service Control Manager) (EventID: 7009) (User: )
Description: A timeout was reached (300000 milliseconds) while waiting for the GuardWareProxy service to connect.
Error: (12/23/2019 05:50:04 PM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The GuardWareProxy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: (12/23/2019 05:50:04 PM) (Source: Service Control Manager) (EventID: 7009) (User: )
Description: A timeout was reached (300000 milliseconds) while waiting for the GuardWareProxy service to connect.
Error: (12/23/2019 05:49:56 PM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The GuardWareProxy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: (12/23/2019 05:49:56 PM) (Source: Service Control Manager) (EventID: 7009) (User: )
Description: A timeout was reached (300000 milliseconds) while waiting for the GuardWareProxy service to connect.
Error: (12/23/2019 05:49:51 PM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The GuardWareProxy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: (12/23/2019 05:49:51 PM) (Source: Service Control Manager) (EventID: 7009) (User: )
Description: A timeout was reached (300000 milliseconds) while waiting for the GuardWareProxy service to connect.

 

 

[BobScott49]

Okay, great.

 

I guess that's it then.

 

I want to thank you very much for all your patience, support and help over the past few weeks, your advice has been invaluable