I'm experiencing much higher CPU usage with Beta 12 on Windows 10x64 Pro Pc. It is ~ 10 times higher than on Beta 11. Typically DF CPU usage runs ~ 0.4%, but on Beta 12 it is ~5.0%.

Attached is a Process Explorer mini dump. I can send you a full dump, but it is ~133 mbytes, so will need a "Where to Send".
Thus far, this issue is only on my Windows 10x64 Pro system and not on my Windows 11x64 Pro systems.

I tried Beta 12 again after Windows Update to Version 21H2 (OS Build 19044.1561) was released today (11-Feb-2022). This DF CPU usage issue did not change. It is much higher than Beta 11. Beta 11 typically runs 0.4-0.5% and Beta 12 is running 3.5-5.0%.
I will have to switch back to Beta 11.

I tried Beta 12 again after Windows Update updated to Version 21H2 (OS Build 19044.1566), released today (16-Feb-2022). The DF CPU usage issue did change somewhat to a lower CPU usage. It is still significantly higher than Beta 11 or DF 9.9. Beta 11 typically runs 0.4-0.5% and Beta 12 is now running 1.5-3.0%.
I am going to stay on Beta 12 to see if any further improvement occurs.

Sorry, no. I have tried disabling several of the features in Beta 12 with no positive affect on the CPU usage.

No, it doesn't help at all on my Windows 10x64 Pro. I closed down every pgm except DF. There is a very slight improvement but still significantly higher than Beta 11

I am having a similar issue with DisplayFusion 10.0 Beta 12. I have constant ~10% cpu usage. Even if I disable Multi-Monitor Taskbar and do everything listed in your screenshot and reply. After restart it still has high cpu usage.

Setting the 4 advanced settings does not make a difference. Logging is off. Beta 12 CPU usage remains ~ double that of Beta 11.

On Windows 11x64 Pro with basically the same cadre of applications, but on with a i9-11900k CPU, DF is running 0.1-0.3 CPU usage.

Beta 11: Malwarebytes on 0.38-1.32, Malwarebytes off 0.38-1.32

Beta 12: Malwarebytes on 0.76-4.54, Malwarebytes off 0.19-3.65

Measured by Process Explorer, 1 second cycle, monitoring Displayfusion.exe

Beta 13 appears to be a slight improvement (0.38-3.05 Cpu usage); however, still significantly higher than Beta 11.

Again, this is only an issue on Windows 10. Windows 11 is running 0.1-0.3.

I am still seeing higher CPU usage with Beta 13 vs Beta 10. Let me know if I should submit logs too. I don't have Malwarebytes or use WinSCP. I do however use Start 11 and Groupy from Stardock.

Beta 13 seems to have solved my CPU usage issues. I am back to under 1% and most of the time around ~0.4% usage. I use Avast Free Antivirus, so maybe it has something to do with how other AVs interact with DisplayFusion?

I reinstalled Beta 11 and rebooted. The Beta 11 numbers are:
0.19-1.51 via Process Explorer.

BTW, why is the Beta 13 installer still at 117 mbytes while Beta 11 is 97 mbytes? Seems Beta 13 is still carrying the runtime package.
Change: Removed bundled C++ runtime (it was added to try and resolve an issue, but didn't end up helping)

Keith, should I send through anything to help assess what could be causing the slightly elevated CPU usage on my Win 10 x64 PC? (as per previous post) Thanks.

I'm having similar issues with Beta 13 - specifically with gaming. Most games will studder or hang while display fusion is open and I literally move the mouse. If I exit Display fusion Beta 13, the game(s) perform normally. I'm noticing my GPU usage on the game drops to about 0 while this is happening. Again, exiting DF causes the game(s) to act normal. Very odd. I rolled back to Beta 11, works fine.
MSI B550-A Pro
Ryzen 7 3700x
32GB ram
Samsung 970 Pro 1TB
RTX 3070

I'm going to share a current experience and state an observation that may be a clue as to why DF is running higher CPU activity in recent betas.
I have a new Dell XPS 8940SE that came with Windows 10x64 Pro. I have two Dell U2719D monitors attached to it. I let this new system upgrade itself to Windows 11x64 Pro. I'm a Windows Insider so I set up the Insider update to Beta to get the latest updates of Windows 11x64 Pro. I've had DF running on it and it has had very low CPU activity...like 0.1-0.3 CPU usage consistently.
HOWEVER, in one of the beta releases a few weeks back, I completely lost the sound on the system. The sound device hardware was totally dead as if I had removed it from the system. New Realtek drivers updated, checking all settings, etc. but nothing would bring back the detection of the sound hardware. To clarify, this lost sound event occurred BEFORE I installed DF on this system.
I decided to perform a fresh/clean re-installation of Windows 11x64 Pro and all my software. The built-in sound device (driven by Realtek drivers) returned and is now working fine. I've re-installed my cadre of applications, etc., and all is working fine. HOWEVER, now DF is running a high CPU usage of0.2-2.5, every similar to my Windows 10x64 system on which I am using the ASUS built-in sound device driven by Realtek drivers.
My observation : Perhaps the DF higher CPU usage in recent Beta 12 and 13 may be the result of a conflict with the REALTEK sound drivers, eh?? Unfortunately, I have no data/facts to back up this observation.
As a test, I downgraded to Beta 11 on the new Dell. The CPU usage dropped to 0.09-1.54 similar to my Windows 10x64 system if I downgrade to Beta 11 on it.

Just the driver and the Realtek HD Audio Manager in the system Control Panel. On Windows 11, the Realtek HD Audio Manager is not present because I only have two speakers on the Dell XPS8940SE system.

No, not that I can measure. Sorry, guess it is a false observation.

I hadn't previously noticed the issue, but I see a fairly constant 5.5% going up to 8% periodically (and spiking at 20% when some window or DF activity occurs) for process DisplayFusion.exe.

Disabling the Multi-Monitor taskbar (two monitors) reduced the usage to 4.7% or so.

I am on Windows 10 x64 release 21H2 (recent upgrade) and DisplayFusion Pro 10.0 (Beta 13). I have CrowdStrike AV.

Beta 14 shows no improvement over Beta 13 on CPU usage as compared to Beta 9. 14 ranges 0.19-2.76 and seems to spend more time on the higher end of the scale

On my Windows 10x64 Pro desktop, I dropped back to Beta 11. The CPU usage range is 0.19-1.68 and it stays mostly on the low end range (0.19-0.55)

From what i see in ETW profiling data, with my limited understanding of Windows development tools, it looks like DisplayFusion.exe is creating a new thread each ~second, and spending almost all of its time in .
Trace is in attachment, maybe it will prove useful. It's taken with Beta 14, with DisplayFusion.exe CPU jumping between 5 and 15%.

Beta 15 shows no improvement in CPU usage on Windows 10x64 Pro (0.19-2.68, most hits on the high range of the scale).