I have been advised of a problem with component updates in a corporate setting where an update server on the LAN is used for clients. If component update is allowed, but a reboot is not forced, it appears that the antivirus definition files will not be updated again until the reboot occurs. Nod32 appears to still be running fine, and protecting against viruses, but the definition files will not be updated until the unit is rebooted. This is annoying on the workstations, but not a huge problem, since most of them are rebooted daily (all should be, but you know how some users are ). My big problem with this is that the update server itself quits taking virus definition updates until a reboot of the server is done. That means that NONE of the clients on our network receive definition updates until the server is rebooted. Our server cannot be allowed to reboot at will, so this presents a serious problem. Hopefully this is a bug, and not the designed behaviour. If it is, it makes the automatic component update feature pretty much unusable in a coporate setting, at least with us. Thanks for any help.