If I disable AMON and leave it disabled while restarting my PC, NOD32 (version 2.50.25) takes a long time to load on the subsequent startup of Windows XP. The splash screen just sits there on the screen with the build number area left blank for 30 seconds to 1 minute. Eventually it loads. The following error is logged in the event viewer (My Computer -> Manage -> Event Viewer -> System): Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7022 Date: 8/6/2005 Time: 11:02:29 PM User: N/A Computer: *********** Description: The NOD32 Kernel Service service hung on starting. This is 100% reproducible on my system with the following steps: 1. Uncheck “File system monitor (AMON) enabled.” 2. Start -> Turn Off -> Restart to reboot PC. 3. Log into windows. 4. Watch the NOD32 splash screen hang. I contacted ESET support, but we were unable to figure out the cause of this problem. So, I’m turning to this forum for help. Mainly, I would like to know if this error happens on all computers and is a general bug in NOD32 or if it has something to do with a conflict on my system. However, this problem occurs on my system even after a fresh install (just Windows XP, OfficeXP, required drivers, and security updates). Can anyone successfully disable AMON and then not have it hang on reboot? I did a search on these forums regarding this issue and found the following related threads (unfortunately, none of them have any solutions that I can descry). Yet, it seems like some other people notice this problem too: https://www.wilderssecurity.com/showthread.php?t=85590&highlight=7022 https://www.wilderssecurity.com/showthread.php?t=85276&highlight=7022 https://www.wilderssecurity.com/showthread.php?t=84754&highlight=7022 https://www.wilderssecurity.com/showthread.php?t=83102&highlight=7022 Thanks for any help you can provide!