I'm lately getting high CPU usage (20-25) from wfcs.exe after every PC restart and it doesn't settle down. I've added it to the scanning & monitoring exclusions of EAM (Emsisoft) but problem remains. Perhaps I'll try uninstalling EAM as a test. Problem only goes away if I restart the WFC service. Notifications are enabled and I only log the blocked connections (these have always been my settings - this issue appeared only recently). W10 x64 Pro 1803 / 17134.345 update: looks like EAM is the cause - I'll let them know and let you know if required.