Correction: The reader version is: 11.0.0.7
I've been told that the error started showing up in 11.0.0.6 with security hardening. I like the idea of hardening, but not at the expense of stability and usability (If you disable the “Protected Mode as startup” the error goes away but it’s not something I'd tell a customer to do.)