none
Outlook 2016 has disabled the internal VBA macros. RRS feed

  • Question

  • Hi,

    Outlook 2016 (Windows 10) has blocked the VBA projects. I created an e-mail rule that includes a command file which worked properly. And then one day to the next (after work I switched off my notebook, the next day I turned it on) the VBA did not run only the rules did. When I wanted to repair the macro, clicking on the link in the rule, it wrote that: "In the current mode, this action is not available.". If I opened the Visual Basic Editor finding and run the code of command file, it wrote that: "A VBA project error occurred during validation of the signature. The macros will be disabled. I tried all settings in the Trust Center, you can read in the forums. I also tried Digital signature, but nothing changed.

    Friday, January 6, 2017 10:16 AM

All replies

  • I just discovered smothing similar. I have a rule on a shared inbox that runs some VBA code on email arrival.

    Outlook is no claiming that there is an error on that rule ("This rule is not available in the current mode.").

    I think this came after the very recent update.

    Any ideas how to fix it?

    Friday, January 6, 2017 12:57 PM
  • I just discovered smothing similar. I have a rule on a shared inbox that runs some VBA code on email arrival.

    Outlook is no claiming that there is an error on that rule ("This rule is not available in the current mode.").

    I think this came after the very recent update.

    Any ideas how to fix it?

    I just tried recreating the rule, but there is no more option to "run" code in the rule wizard.
    Friday, January 6, 2017 1:08 PM
  • Hello,

    Did you have a chance to check out the VBA Macro settings in the Trust Center? Are unsigned macros allowed to run?

    For example, take a look at the similar issue - Macros and add-ins do not run when security is set to High in PowerPoint and Word .


    profile for Eugene Astafiev at Stack Overflow, Q&A for professional and enthusiast programmers

    Friday, January 6, 2017 1:35 PM
  • Hello,

    I have tried set all of security levels (including digital signature), but nothin happened. One day before it worked properly without digital sign and with the same security settings.

    Friday, January 6, 2017 2:13 PM
  • Did you install any updates for Outlook after that? 

    profile for Eugene Astafiev at Stack Overflow, Q&A for professional and enthusiast programmers

    Friday, January 6, 2017 2:18 PM
  • No. As far as I know.
    Friday, January 6, 2017 2:34 PM
  • I have checked it. Last update was installed on 14.12.2016. The VBA worked properly on 02.01.2017 and I faced with this problem on 03.01.2017. 
    Friday, January 6, 2017 3:32 PM
  • Yes. It is correctly set.

    This happened after the recent update on 4th January. I followed instructions to return to a previous version but this has not changed anything.

    I also tried a registry change to have the "run script" option appear again in the wizard, which worked, but scripts will not show in the list of scripts.

    Friday, January 6, 2017 5:17 PM
  • Same problem here with Outlook 2016 (64 bit) 16.0.7571.7063.  This started right after I allowed an Office update to install a day or two ago.  Rules with Macros/VBA run from them fail, and when creating a new rule executing a Macro/VBA is no longer an option.  Even with the "all all macros" in security.  Argh...
    Saturday, January 7, 2017 1:13 AM
  • Same issue, need remedy! Tried all suggestions in thread.
    Saturday, January 7, 2017 2:56 PM
  • Do you have any antivirus software installed on the machine?

    Could an administrator apply changes to your machine?


    profile for Eugene Astafiev at Stack Overflow, Q&A for professional and enthusiast programmers

    Saturday, January 7, 2017 3:04 PM
  • Do you have any antivirus software installed on the machine?

    Could an administrator apply changes to your machine?


    profile for Eugene Astafiev at Stack Overflow, Q&A for professional and enthusiast programmers


    My installation was a personal machine at home, no domain, etc.  Just using Microsoft Security Essentials, no changes there.  It was the Office update recently pushed...
    Saturday, January 7, 2017 3:15 PM
  • An antivirus would not alter the Outlook menus. At worst, the option would be there but wouldn't work.
    Saturday, January 7, 2017 3:21 PM
  • I am the administrator on my machine. I have only Windows Defender and there was not any significant event or update as I chacked it.
    Sunday, January 8, 2017 3:17 PM
  • Monday, January 9, 2017 6:05 AM
  • Hi,

    What are your specific versions of Office?

    Please visit Version and build numbers of update channel releases for Office 365 clients to check your channel and version.

    I suggest you check office update.

    Sorry that we do not have the version: 1611 Build 7571.2109 to test.

    After updating, I could run a script for rules with Current channel: Version 1612(Build 7668.2048) and First Release: Version 1609(Build 7369.2102) and Deferred: 16.0.6965.2117

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.



    Monday, January 9, 2017 9:36 AM
    Moderator
  • Thanks for the info.

    I'm on 1611 Build 7571.2109 and no other updates are showing for now.

    In addition, Version 1612(Build 7668.2048) is not listed on https://technet.microsoft.com/en-SG/library/mt592918.aspx.

    Regards

    Stefan.

    Monday, January 9, 2017 9:44 AM
  • Hi,

    Version 1612(Build 7668.2048) is Office insider version. I have Office insider version, so I don’t have 7571.2109 for Current channel to confirm if the issue exists.

    If the issue occurs in 1611 Build 7571.2109, I suggest you try to revert to an earlier version following https://support.microsoft.com/en-sg/kb/2770432 and you could submit a feedback on UserVoice site: https://outlook.uservoice.com/

    If the issue is urgent, I suggest you contact the Microsoft professional support.

    If the support engineer determines that the issue is the result of a bug, the service request will be a no-charge case and you won't be charged.

    Please visit the link below to see the various paid support options that are available to better meet your needs.  

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, January 9, 2017 9:56 AM
    Moderator
  • Thanks, but I already reverted to previous versions but the issue remained. I'm not sure why.

    I have since then re-enabled the updates and am back on the latest version.

    I also tried th registry mod that worked in that the option re-appears in the Rules wizard, but previously visible scripts were no longer visible and I was unable to get them to appear.

    As for the issue existing, I think there are enough complaints now on forums indicating that the issue exists.

    I had to work over the weekend to find a work around so that our day-to-day business was not affected. Not fun...

    Thanks for your support though :-)


    Monday, January 9, 2017 10:21 AM
  • I installed the registry key setting in this articie mentioned, but the problem still exist.
    Monday, January 9, 2017 9:59 PM
  • Hi,

    Sorry that I failed to reproduce your issue.

    Due to the limitation of the community support channel, I suggest you contact the Microsoft professional support, so that Microsoft engineers can work closely with you to troubleshoot this issue. Please visit the link below to see the various paid support options.

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

    If the support engineer determines that the issue causes from bug, you won't be charged for the service request.

    Regards,
    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, January 10, 2017 6:30 AM
    Moderator
  • Hi,

    Sorry but I don't want to write in more forums especially not for money. I reinstalled the Office 2016 and switched off the automatic upgrade. It solved the problem.

    Tuesday, January 10, 2017 10:28 AM
  • Was in the same boat :-D! You need this:

    [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security]
    "EnableUnsafeClientMailRules"=dword:00000001

    • Proposed as answer by ba7ranya Sunday, January 13, 2019 11:33 AM
    Tuesday, January 10, 2017 3:28 PM
  • Did the trick for me. Thank you!
    Monday, May 29, 2017 7:52 AM
  • I have this registry key and the 'run a script' option is available, but the script does not run.

    Monday, February 4, 2019 7:28 PM
  • In case there is anyone who still needs some input on an answer:  Try uninstalling the OUTLOOK App that is now preinstalled with the OS Win10 and seems to be downloading with updates.

    I, too, had a brand new win1064bit ver 1903 running MS Dynamics with VBA customizations that launched Outlook 2016 working very nicely.  Then, from a Friday night to Monday morning, the launch stopped working with the debug error stuck on CreateObject(“Outlook.Application).  I paid our MS certified support vendor for $195 for 1 hour min (5 minutes) to tell me they were not familiar with my system and would have to charge to investigate the error. Suggested I uninstall Outlook and reinstall to see if that fixed the error and if that didn't work, then uninstall the MSDSL2015 client and reinstall and see if that fixed it.  Needless to say, I tried all those steps before calling them, so had to walk away.  I also tried installing Office 2013 to see if that affected the code from launching, still didn't launch on the same machine.  All other machines in our office are working flawlessly.

    I started with a new, identical machine and tried to repeat the installation of our softwares identically, but this time, the error started immediately.  Now on ver 1909.  I followed the suggestion and put in the key above "EnableUnsafeClientMailRules"=dword:00000001 and all that did was throw a different error and advance to the next line of code.  So I hit the advance or run (green arrow) key in the debugger and a strange thing happened, my Outlook setup for an account came up again, but it looked just slightly different.  It made me install the network account again and opened the screen, but it was slightly different looking.  Then I realized I was in the OUTLOOK App not Office 2016 Outlook.  OMG!  I went out, typed in Outlook in the search bar, clicked on the preinstalled OUTLOOK App from MS, uninstalled it.  My VBA code was hitting the App first.  Once uninstalled, my launch to Office2016 Outlook worked perfect as programmed.  Now I can fix my other machine and have it as a spare ready to go on the shelf.  Hope this helps someone.

    Friday, December 13, 2019 12:02 AM