Comodo Firewall: inspect.sys Continues to Consume High CPU When the Firewall Is Disabled

Comodo Firewall: inspect.sys Continues to Consume High CPU When the Firewall Is Disabled

Description

During heavy network activity, particularly when transferring files between computers over the local network, the inspect.sys kernel-mode driver continues to consume significant CPU resources even after Comodo Firewall has been disabled.

I monitored the activity using Process Explorer. The CPU usage is attributed to a thread within the Windows System process (the kernel process associated with ntoskrnl.exe), with the execution activity involving Comodo’s inspect.sys driver. This is not a separate user-mode process.

Expected behaviour

When Comodo Firewall is disabled, I would expect its network inspection driver, inspect.sys, to stop inspecting network traffic or at least significantly reduce its CPU activity.

Actual behaviour

Even with Comodo Firewall disabled, inspect.sys continues to be associated with high CPU usage during heavy network traffic, especially when transferring files between computers on the local network.

Question

Is this expected behaviour, or does inspect.sys continue processing or inspecting network traffic even when Comodo Firewall is disabled?

1 Like

I’m not 100% sure but you may also need to disable website protection (cavwp) process which might use the same drivers. Hopefully @C.O.M.O.D.O_RT will be able to confirm.

Hi user9823742,

Thank you for reporting.
We will reach you through private message to get required log for further investigation.

Thanks
C.O.M.O.D.O RT

Disabling the firewall in the interface usually leaves the driver loaded, so it can still watch local traffic while a transfer is running.
Try a full restart after disabling it, then test the same transfer again and note whether the System process stays high.