Same issue here with me. But I noticed something. This is probably not the issue with many of you who replied to this thread, but I run a headless home automation server on win10. So when I configure it, I RDP to the PC.
This build 1903 has also peaked my CPU (ran from ~8% to ~54% after the update). I tried all the suggestion in this thread to no avail.
But I noticed that when I was RDP to the PC, the cpu ran ~15-20%. But when I logged out of the RDP session, the CPU went back up to +50% (I can tell because the automation software runs a WMI poll of CPU and MEM, which I trigger an email on if it exceeds
40%.)
Anyway, I added a monitor, keyboard, and mouse to watch the PC when not RDP'd in to see if I could catch a process spiking the CPU. I was thinking it was a maint task, or scan.
But to my surprise with a monitor and keyboard/mouse attached, the PC runs back down ~8-10% again.
Just to be sure, I removed the monitor keyboard and mouse again, rebooted, waited a few and it spiked again.
I think I found my issue, Not sure this is the same use case as others, but thought I would mention it.
Chuck