Q: APSDaemon.exe uses excessive CPU resources

Setting compatability mode to WIndows98/ME seems to have done the trick for me, running Windows XP.

Thanks!

Thanks alexis_nz. That does seem to have done the trick.

On one computer, apsdaemon came back, but I hadn't rebooted that one (Windows auto-update later did that for me anyway...) so it might have been still in memory when I restarted iTunes.

Now that both have rebooted, I haven't seen a return of the voracious CPU usage.

So any idea as to why we need to set the exe file to be compatible with a 14 year old version of Windows?

How did you work out this fix?

Thank you for this solution --- Its working for me.   The daemon went from constant 50% CPU usage down no more than 2 or 3.  This is on WinXP with latest patches.  

However, if Apple doesn't address this, then its rather irresponsible of them.

Yes, I have done the compatibility mode idea on two XP computers, and wirelessly sync with the computer on one of them. Unfortunately, I must now report that both computers are showing the old apsdaemon behaviour, of guzzling one of the CPUs on each. Back to square one, I'm afraid.

It seems to become a problem after the phone or ipad has "gone away" (ie, gone out of range of the lan).

Maybe it's about if they go without being disconnected?

But that doesn't explain the computer that does no syncing.

I'm at a loss. So too are Apple, it would seem.

I have one XP computer and one Windows 7 computer. I've been following this thread and following all the ideas and have to report that my XP system is doing exactly the same thing, APSdaemon.exe is still eating up one core (50% for both). The XP computer is the one that I sync my devices to but I have turned off wireless sync. The only thing that I have not turned off is the Home Sharing for the Apple TV. That is next....not sure if anyone is using that functionality. I can tell you that iTunes goes to zero cpu usage almost immediately after launching with the Home Sharing turned off. Where as with Home Sharing turned on, it takes about a minute or two to finally settle down to an idle.

I have no other problems with the system with any other applications, it is all up to date with patches, latest iTunes, etc... To temporarily fix the APSdaemon.exe cpu hogging, I close and restart iTunes. As far as I'm concerned, this is a software bug.

As far as the Windows 7 computer is concerned, it has not experienced the same problem with CPU utilization as the XP computer, however no devices have ever been associated with that system. I do have Home Sharing turned on for that system.

Update. Turning off Home Sharing did not change anything. APSdaemon.exe started using 50% of my dual core machine within an hour of launching iTunes. Killing it again... :-(

Yes sorry guys.. The bloody problem is back for me now too (using compatibility fix). It's doing my head in. I don't use wireless sync - so can't really tell what combination of events causes it to start again. Could be virus scans, could be leaving my WiFi network, could be use of AppleTV, could be switching Accounts on my PC (two users).

Anyway, as I don't use wireless sync - I have done the following (ugly I know)

• Go to the Startup tab and find ASPDaemon.exe. Uncheck it. This will stop the application from starting when your system does. 
• Go to C:\Program Files\Common Files\Apple\Apple Application Support and rename ASPDaemon.exe to something else (e.g. ASPDaemon.I_dont_want_this_to_run). This will stop iTunes from being able to start it.

I await Apples fix for this problem!  %&*^%*%&^%$&^%$&%

I too have the same issue.

iTunes 10.5.2.11. WinXP Pro SP3. Dual core Intel CPU. APSDaemon using 50% or more CPU.

I tried all the above mentions fixes with no improvement.

I hope Apple takes this issue seriously. My old CPU is running 70+C, 24/7, in this hot Queensland summer.

I'm using a 4S, XP Pro SP3, Pentium 2.00 GHz processor, 1.99 GB RAM, iTunes 10.5.2.11, and have the same problem.

Though rcharbon describes APSDaemon.exe as "the wireless sync service," I don't run the wireless capability and think the exe is in fact much more--it's the iTunes exe.

With my new phone, I took advantage of Apple's live support. Apple is clearly aware of the problem, but offered two--and only two--suggestions.

First, shut all Windows apps and then, from the command line, issue "netsh winsock reset." Reboot as instructed and keep your fingers crossed.

This first suggestion didn't work for me.

Second--if the first suggestion fails--remove and reinstall iTunes. I was given the following URL for guidance: http://support.apple.com/kb/HT1925?viewlocale=en_US

I haven't tried the second suggestion yet. I'll be interested to know if  anyone else has tried the remove and reinstall approach.

The same problem as mine. Is there any solution? I am sure that it it a bug from iTunes for Windows XP.

OK, now I followed Apple's directions to remove iTunes and related components, reinstalled, and the problem disappeared! While this isn't an elegant solution and I appreciate rcharbon's cynicism and skepticism, at least it's fixed.

Well, I tried the remove and reinstall approach.

Looked good for a day, and then crapped out today whilst I (and hence my iPhone) was away. And this is on the iTunes that isn't supposed to auto-sync with anything.

C'mon Apple! This is pathetic. It has been a significant problem for two months now.

Surely you know what you introduced with that version?

Can't you let us run a profile on apsdaemon to tell you where it's stuck?

Yes, I suspect @witaksm will get the same reappearance at some stage.The kill apsdaemon fix posted on Jan 12th is still working, but is no good for anywone that actually wants to use Wireless sync!

This fix was pinched from this blog post...  http://www.andyfrench.info/2012/01/apsdaemonexe-apples-machine-killer.html. It is interesting to read the authors point anout Kaspersky, however I'm running Norton internet security. What is almost certain is that apsdaemon is going into some sort of loop with another service or piece of software.

Regardless.. It is a Apple bug and Apple are less interested in fixing PC bugs than they are Mac problems.

Out of interested is anyone else running two accounts (profiles) on one XP system? As thats when it started to be an issue for me.