Outlook security patches intentionally break custom forms
When Microsoft released its Outlook security patches on Sept. 12, several readers complained that their custom form printing capabilities disappeared. Ends up the bug that broke VBScript printing isn’t a bug at all.
Microsoft announced over the weekend that it intentionally disabled scripts in custom forms, and those with printable custom forms need to make manual Registry changes to bring the feature back.
Those of you who have installed any of this month’s Outlook security patches:
- Outlook 2007 KB 4011086
- Outlook 2010 KB 4011089
- Outlook 2013 KB 4011090
- Outlook 2016 KB 4011091
will have to dive into the Registry if you want to enable any custom form scripts, including the VBScript printing capability. It’s complicated, and the method varies, depending on which version of Office you’re using and the bittedness of Windows and Office. Diane Poremsky has detailed instructions on her Slipstick Systems site.
To read this article in full or to leave a comment, please click here