I noticed that when playing Deathloop (via Steam), the CPU usage of webroot goes up to 25% and fluctuates between that number and 10% constantly.
I tried adding the deathloop.exe to the ignore file in the PC security options, but it doesn’t let me (It’s almost ½ gig in size).
Any solutions?
Thanks.
Hello
It’s best to Contact Webroot support and they will help you sort it out, it could be simple thing of getting some files whitelisted in the Webroot Cloud database!
Webroot Support:
Submit a ticket 24/7/365
Call 1-866-612-4227 during the week Mon - Fri 7 AM to 5:30 PM (MDT)
Note: When submitting a Support Ticket, Please wait for a response from Support. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue.
Thanks,
Contacting support is best option. There might be a game file that’s unknown to the agent, therefor the agent is “monitoring/journaling” the file and that can eat up some resources.
John
The best thing to do in this situation temporarily - if you don’t want to wait until a response, is to WHITELIST the folder for Deathloop.
As this is a genuine folder as you know it, downloaded from a reputable source (Steam)
No one wants to game with heavy resource usage :P
The best thing to do in this situation temporarily - if you don’t want to wait until a response, is to WHITELIST the folder for Deathloop.
As this is a genuine folder as you know it, downloaded from a reputable source (Steam)
No one wants to game with heavy resource usage :P
If it’s the Consumer version you can’t add a Folder and even if you Allow deathloop.exe it will still be monitored but I’m not sure in the Business version but that’s why it’s best to contact Webroot Support.
Find out the path it’s monitoring and then just allow/whitelist access to that. That is a local fix, so reaching Support will be the permanent fix and will take that MD5 of the file and then whitelist it on our cloud backend so EVERYONE will have this file determined
Find out the path it’s monitoring and then just allow/whitelist access to that. That is a local fix, so reaching Support will be the permanent fix and will take that MD5 of the file and then whitelist it on our cloud backend so EVERYONE will have this file determined
That’s right!
Thanks!
Yes it would look something like this from a scan log:
Thu 2022-10-13 12:13:54.0234 Monitoring process C:\Windows\Installer\MSIF588.tmp tD9AC8AE78726F7F335E09C230CCA5B01]. Type: 3 (24873)
Thu 2022-10-13 12:13:54.0234 Monitoring process C:\Windows\Installer\MSIF588.tmp 8D9AC8AE78726F7F335E09C230CCA5B01]. Type: 4 (24873)
Thu 2022-10-13 12:13:54.0251 Monitoring process C:\Windows\Installer\MSIF588.tmp ID9AC8AE78726F7F335E09C230CCA5B01]. Type: 8 (24873)
Thu 2022-10-13 12:13:54.0251 Monitoring process C:\Windows\Installer\MSIF588.tmp \D9AC8AE78726F7F335E09C230CCA5B01]. Type: 6 (24873)
Thu 2022-10-13 12:13:54.0554 Monitoring process C:\Windows\Installer\MSIF6C2.tmp lD9AC8AE78726F7F335E09C230CCA5B01]. Type: 3 (24873)
Thu 2022-10-13 12:13:54.0554 Monitoring process C:\Windows\Installer\MSIF6C2.tmp tD9AC8AE78726F7F335E09C230CCA5B01]. Type: 4 (24873)
Thu 2022-10-13 12:13:54.0564 Monitoring process C:\Windows\Installer\MSIF6C2.tmp ID9AC8AE78726F7F335E09C230CCA5B01]. Type: 8 (24873)
Thu 2022-10-13 12:13:54.0564 Monitoring process C:\Windows\Installer\MSIF6C2.tmp wD9AC8AE78726F7F335E09C230CCA5B01]. Type: 6 (24873)
Thu 2022-10-13 12:13:54.0874 Monitoring process C:\Windows\Installer\MSIF80D.tmp nD9AC8AE78726F7F335E09C230CCA5B01]. Type: 3 (24873)
Thu 2022-10-13 12:13:54.0874 Monitoring process C:\Windows\Installer\MSIF80D.tmp \D9AC8AE78726F7F335E09C230CCA5B01]. Type: 4 (24873)
Thu 2022-10-13 12:13:54.0884 Monitoring process C:\Windows\Installer\MSIF80D.tmp D9AC8AE78726F7F335E09C230CCA5B01]. Type: 8 (24873)
Thu 2022-10-13 12:13:54.0884 Monitoring process C:\Windows\Installer\MSIF80D.tmp eD9AC8AE78726F7F335E09C230CCA5B01]. Type: 6 (24873)
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
