We've checked with Spiceworks forum and here, currently we're seeing the following:
Checked through most of our systems here and have found a pattern that EventID: 808 tend to be the error that the PowerShell Script everyone is looking at. Most of the errors so far are legitimate Printer driver issues due to remote connection of some kind.
Knowing that IT Admins utilize specific Print Drivers for systems, could ESET get the hash of the files (DLL et al) that's used and have that as a check on servers to verify that it's something we've said are okay? I know we have some VPN users, but normally we don't allow printing to them anyway so blocking them wouldn't be an issue for us here, though I could see it being an issue for others. To that, I'd say have a Print-to-file that they can have emailed to their email or similar.
Not sure if this would stop it, but it could be a start for now.