> Sure, every single one of them is written by a guy who knows the difference between private working set and shared memory ... I think this is a pretty big as

> Sure, every single one of them is written by a guy who knows the difference between private working set and shared memory ... I think this is a pretty big assumption. Anybody can create a Windows service in visual studio in about 3 clicks. Also, these other services may hook things in Windows, hold on to a bunch of handles, constantly poll for things, etc. We really try to be well-behaved in XobniService. It uses a single thread, sleeps the majority (about 99.96%) of the time, has few private bytes, and will probably be swapped out to disk most of the time (unless nothing else needs the memory). So XobniService has virtually nil impact on performance, besides an extra entry in task manager. If Windows had a workable cron implementation, I'd just have used that. I'm thinking about removing it anyway, despite the low impact on performance, since user perception is obviously important. I've been thinking of some workable alternatives, but they don't provide as nice an update experience. If it's really the only thing keeping you away, you can Start/Run 'sc delete XobniService' and the Outlook plugin will still work just fine. You may not receive future updates this way, though. Thanks for the feedback, hope you come back to us :)