Solution to client boot detection jam caused by setting up NOD 32 in local area network

Some time ago, I set up a NOD 32 virus update server in the local area network. I used version 4. I feel quite OK. You can run and advance in at least 2G and win7 environment.

But some time ago, the client came out of a problem, booted into the desktop, nod32 constantly tested files, a lot of memory, resulting in the machine faking death can not be used.

Due to the first encounter of such a situation, a little dizzy, so the temporary solution is: turn off the phone, and then turn it on. Or waiting for it to be tested before it is used. To tell the truth, this method is really sad.

Later, with the help of netizens, it turns out that by default, the client will have a planned task, which is to boot and automatically start file detection.

The cause of the problem:

NOD 32 boot test file

Solution: disable it and do not allow automatic detection on the boot.

Once you know the reason, you can find the answer according to the question.

Is that changed on every client? that's something that hurts.

Luckily, I met a kind-hearted person.

It was finally deactivated, and the effect is as shown below.

-=

Send the relevant operation below to facilitate later use.