Hello, all. I've run into a bit of a mystery and am hoping someone here can help me out. While troubleshooting an issue related to delays connecting to network resources after logon, I took a look in the System log in Event Viewer on my system (Dell Precision M4300 laptop, Intel Core2 Duo 79300 @2.5 Ghz, 4 Gb RAM, Win XP x64 SP2) and found the following entries repeated over and over again, every 10 minutes, one right after the other (within seconds):Event Type: InformationEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7040Date: 5/26/2010Time: 12:53:08 PMUser: NT AUTHORITY\SYSTEMComputer: L124Description:The start type of the Background Intelligent Transfer Service service was changedfrom demand start to auto start.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: InformationEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7040Date: 5/26/2010Time: 12:53:10 PMUser: NT AUTHORITY\SYSTEMComputer: L124Description:The start type of the Background Intelligent Transfer Service service was changedfrom auto start to demand start.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.What would be causing BITS to toggle its status that way? We do have WSUS on the network, but I can't figure why BITS would toggle from automatic to manual every 10 minutes. Looking back further in the System log, there was a time (months ago) when this change was happening every three minutes or so.I'd like to figure out what is prompting the change, and if there is any way to stop it (it just seems like a waste of system resources and log space). I found a lot of search hits on BITS and various problems, but none describing this particular symptom. Has anyone run into this before? Any likely culprits?~HikingStick1 person needs an answerI do too

While I couldn't be sure of the cause I had the same problem with one of my citrix servers. I stopped it by changing the BITS startup type to automatic. This has since resolved the problem. There was a windows update waiting to install for it so most likely it was Automatic updates trying to start the service but as for why it occurs I am afraid I don't know.