0

I've disabled macros for MS Office products via GPO like this: https://superuser.com/a/1176677/440382. Unfortunately, this causes a very weird error in MS Word (both versions 2016 and 2013):

multiple alert windows pop up warning about macros (something like "The function you are attempting to run contains macros or content that requires macro language support..."): enter image description here

despite in GPO (AD Group Policy) there is "Disable all without notification" which also might be seen in local MS Word options itself: enter image description here

This error occurs only when you open a second MS Word window. When only one .DOC(X) file is opened, there is no such a problem.

Unfortunately, this problem occurs even when there are no macros whatsoever in the DOC(X) file(s).

Any ideas, how to fix it? It is VERY frustrating for our users...

PS:

  • I need to have macros globally disabled, because of security reasons
  • sorry for screenshots in Czech, that is how the software runs here...

related threads:

  1. https://superuser.com/a/1176677/440382
crysman
  • 762
  • 3
  • 10
  • 24
  • anyone, please? :/ – crysman Feb 06 '20 at 21:54
  • 1
    I've tested it today again on random two machines, and no issue! Interesting. We've been having this issue for several months! I therefore speculate it got resolved by some MS update (?) – crysman May 13 '20 at 15:47

2 Answers2

0

You could check for any addons that have modules installed or for any code in Personal workbook of the specific user.

IGRACH
  • 485
  • 3
  • 12
  • 24
  • Negative. Had been tested on various machines under various users, even fresh installs - does not depend on anything in workbook. More info here: https://superuser.com/questions/1499625/multiple-macro-warning-message-popups-when-more-than-one-ms-word-window-is-opene/1545475#comment2359421_1499625 – crysman May 13 '20 at 15:47
0

I was getting the same error after disabling VBA in MS Office. It was popping up whenever I opened a document, even a blank one.

enter image description here

Turned out to be an Adobe PDF addin as the cause:

enter image description here

KERR
  • 557
  • 6
  • 8
  • reasonable answer to another question but this one you can see from comments had no add-ins and was resolved by an MS correction/update/fix – K J Aug 16 '23 at 23:53