I rebooted yesterday to allow MS to finish some updates, and it put through updates for
both x86 and x64 runtimes of the .NET v4 assemblies.

Since then Display Fusion has been using 100% of 1 cpu. (The service seems ok, but the desktop tray client
seems to be what is soaking the cpu.

When it was not set for 1-cpu affinity, it tried to use about 150% cpu.

Odd.. if I turn off the service nothing seems different.

I.e. I can tell it to move forward to a new random image (2 monitors, so new image on each)

It's set for random pick from folders (different list for each monitor as they are different sizes).

I had advanced logging on, but log only most important stuff...
so tried turning that off and it seems to have dropped to only using 25% of 1 cpu...which is still insane.

Why is it using any cpu when waiting between wall changes.

It isn't using any hooks and isn't doing any window management....

ideas?