I guess this is a lost cause. The copy protection module used by SAM Broadcaster (Oreans Winlicense/Themida) is to blame here.
This is meant as an extra protection against finding out how the copy protection works and then working around it.
While Winlicense is usually broken in a few months after each update, they're one of the strongest copy protections used outside the Game industry and cracks rarely make it to the public.
If you only occasionally use Procmon, the trick is to exit procmon and reboot your system before starting SAM again. Procmon doesn't unload it's driver when the software is closed, because that might cause problems when a process that was previously monitored isn't finished sending data.
Here's a good writeup on how/why this works by a dutch developer of a music library software: http://www.alwinhoogerdijk.com/2009/12/ ... mment-1846
. They decided to disable the monitoring protection for the copy protection module on their software. That's apparently the only way to get rid of conflicts with Procmon and Regmon.
I wish good luck in convincing the Spacial Support team to forward this information to their developers and management and also have them decide to turn this off for the handful of people using such software. (Hint: I don't think it will happen. Spacial likes to play big corporate with their support team that has never even used the software themselves I think. Getting them to forward your info to a developer and then having them convince the management to disable a minor protection feature of their licensing/copy-protection module sounds close to impossible to me)