bingdesktop.exe over 20% CPU

Anonymous
2013-04-02T09:16:53+00:00

Hello,

Bing Desktop (bingdesktop.exe) constantly uses more than 20% of my CPU. 

I'm running W7 on an i7 quad-core with 8GB,

Does anyone know how to fix this?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-04-06T11:42:40+00:00

Hi,

I found a solution: uninstall and reinstall! It works perfectly now: CPU used = 0% and the background picture is correctly refreshed.

Regards

Was this answer helpful?

1 person found this answer helpful.
0 comments

41 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-04-02T14:05:41+00:00

    I was seeing varying percentages on the different computers. On one it was using about 15% on  the other two was moving between 30% and more than 40%.

    For what is worth, removing and reinstalling did fix the problem for me on all devices.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-04-02T13:27:19+00:00

    Yes, it looks like you are right.

    I don't see 30 or 40% but a constant rate of 12% which still is way to high for an idle background app.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-02T13:06:48+00:00

    It actually makes sense. Mine stopped working on both, PC and laptop last Saturday night too. That was the night we've changed time in UK.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-04-02T11:53:33+00:00

    Exactly a year after the first post in this thread, I'm experiencing exactly the same problem. I have Bing desktop installed on three different PCs and on all of them as of last weekend, the client is taking more than 30% or even 40% CPU and the wallpaper do not change anymore.

    Now I have a weird theory. The only thing that last year problem and this year problem have in common is that they occurred on the weekend of switching from standard time to summer time.

    Of course the previous post on October 10th may seem to disprove my theory, unless that week in October was when you switched back from summer to standard time?

    Was this answer helpful?

    0 comments