Referencing this thread: https://www.wilderssecurity.com/showthread.php?t=85276&highlight=7022 My problem is not with the fact that NOD32 (XP) doesn't stay disabled after reboot, but rather, why when I disable AMON and then happen to reboot does NOD32 take so long to start up again? It effectively stalls the final stages of the boot (well after the Desktop has come up), and even prevents making an Internet connection, for between one and two minutes. When you boot, NOD32 has to start up all over again from scratch whether AMON is disabled or enabled last, so what's the difference? I have to say, before searching and finding the older thread, I didn't even make the connection between this problem occuring when AMON was disabled as opposed to when it's enabled, though I probably would have picked up on it eventually. I just thought it was randomly failing.