Thanks for sharing this fix with us. I had been working on this problem all week, and the "Official" fix from Inuit tech support was "uninstall and reinstall Office" - which I knew was not the proper solution from the beginning, but it was all I had - so I proceeded to do so (with mixed success) on over 30 workstations. This fix has worked on the 10 workstations I tried it on today and takes about 30 seconds per station - so thank you very, very much for giving me back the rest of my weekend!
One note - there is a typo in the above solution - where it says, "Go to state e-file state 22." It should be, "Go to state e-file state W2." Most people will likely figure that out on their own, but some may be confused by it, so it seems worth mentioning.
Btw - I'm an IT provider, not an accountant. That being said - I want to make anyone who ends up on this post aware of another particular threat that the problem could pose. If your end-users (accountants, or whoever) tried to fix this themselves prior to finding this solution - it is very possible/likely that they will have changed the trust settings for macros to "Enable VBA macros (not recommended; potentially dangerous code can run)" - which is definitely NOT a state you want to leave those workstations in. Macros without notification can be a huge security risk and should not be allowed to run in that manner. So if you're responsible for taking care of workstations that dealt with this issue, be sure to check that setting and get it back to "Disable VBA macros with notificiation." I know it's a nuisance to have to click "Allow Content" every time, but it's worth it to mitigate the potential security risks.
Hope this helps. Be sure to drop a like for the OP for being kind enough to share.
