Windows defender cloud protection ignoring exclusions

[Guest Filibuster]

I have a client with an application that has issues starting/operating when Windows defender is scanning its network share. There is an easy work-around for this - just add the folder/process path to the windows defender exclusion list and away you go. As of today, the "cloud protection" function is preventing this program from starting, just as it did before the exclusions were added. If I disable cloud protection everything works fine, but why is the cloud protection feature ignoring my excluded folders/processes? This is Windows 10 Pro 1903 and the July 2019 update just installed, but the behavior persists even after uninstalling the updates. Behavior is the same on several computers - perhaps a definition update that went wonky?

 

More...