Bigbluee Posted November 15, 2017 Report Share Posted November 15, 2017 Hi I decided to log in and post this subject as it does happen second month in a row. I have WIn10 with autoupdates and Immunet 188.8.131.5200 In the day when Microsoft publishes security patch, Immunet takes 99% of cpu for COUPLE DAYS !! As You can suppose, in that time, working on laptop is almost impossible. I am IT person but not with security knowledge on that level, to know why Immunet tales over my laptop and blocks my drive during downloading and installing a monthly patch. My WIndows is fresh. It is 3 months old. Ok, but details: Once i notice that WIndows Update starts to download security patch and progress bar starts to move, my work on laptop ends. Performance manager shows 99% of disk utilization for SFC.exe. DB-Journal grows all the time int Immunet folder as it scans i have no idea how many files and why so long. What files exactly it scans? Files located in: C:\Windows\Software Distribution\Download C:\Windows\CbsTemp C:\WIndows\WinSxS Prewious sec update for Win10 (2017-10) was running all the time 24h for 3 days until I lost my patience and uninstalled Immunet. Then it installed patch without delay. Then installed Immunet again This month I have exactly same issue. It scans 2017-11 patch from the morning. This time I decided in the evening, after I lost whole day, to work with Exclusion method. Added exclusions in Immunet for: C:\Windows\Software Distribution\Download C:\Program Files\Immunet C:\WIndows\WinSxS After this, utilization of disk dropped to acceptable level and even if it grows, it is related to transfer of big files by svchost and ratio jumps to 20 or 30mb/s on disk for couple seconds. Finally progress bar of patch installation started to move. After adding exceptions, WIndows finished patch download process and installation within next 20 minutes. Is it a normal behaviour of Immunet? Is it safe to keep these exclusions? Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.