Skip to main content

How to restore missing Run a script option in Outlook rule?

In certain versions of Outlook, particularly in recent updates, the "Run a Script" option may be disabled by default as a security measure. To activate the "Run a Script" option in Outlook, enabling the creation of rules with VBA scripts, you will usually need to modify specific registry settings. Continue reading for detailed instructions on how to do this.


Enable missing "Run a script" option in Outlook

To restore the missing run a script option in the Outlook rules wizard, first ensure that Outlook is closed, and then proceed with the following steps:

  1. Press the Win + R keys together to open the Run dialog box. In this dialog box, type regedit and then click the OK button.
  2. In the popping out User Account Control dialog box, please click the Yes button.
  3. In the Registry Editor window, navigate to the below path to access the Security setting: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security
  4. Right click on the Security key, and select New > DWORD (32-bit) Value.
  5. Name the created DWORD as EnableUnsafeClientMailRules.
  6. Double click on the EnableUnsafeClientMailRules DWORD to open the Edit DWORD (32-bit) Value dialog box. Type 1 in the Value data box, and click OK.
  7. Restart your Microsoft Outlook.

By following the steps outlined above, you will be able to locate and use the "run a script" option when creating rules in Outlook.


Related Articles


Best Office Productivity Tools

Kutools for Outlook - Over 100 Powerful Features to Supercharge Your Outlook

📧 Email Automation: Out of Office (Available for POP and IMAP)  /  Schedule Send Emails  /  Auto CC/BCC by Rules When Sending Email  /  Auto Forward (Advanced Rules)   /  Auto Add Greeting   /  Automatically Split Multi-Recipient Emails into Individual Messages ...

📨 Email Management: Easily Recall Emails  /  Block Scam Emails by Subjects and Others  /  Delete Duplicate Emails  /  Advanced Search  /  Consolidate Folders ...

📁 Attachments ProBatch Save  /  Batch Detach  /  Batch Compress  /  Auto Save   /  Auto Detach  /  Auto Compress ...

🌟 Interface Magic: 😊More Pretty and Cool Emojis   /  Boost Your Outlook Productivity with Tabbed Views  /  Minimize Outlook Instead of Closing ...

👍 One-click Wonders: Reply All with Incoming Attachments  /   Anti-Phishing Emails  /  🕘Show Sender's Time Zone ...

👩🏼‍🤝‍👩🏻 Contacts & Calendar: Batch Add Contacts From Selected Emails  /  Split a Contact Group to Individual Groups  /  Remove Birthday Reminders ...

Over 100 Features Await Your Exploration! Click Here to Discover More.

Read More       Free Download      Purchase
 

 

Comments (26)
No ratings yet. Be the first to rate!
This comment was minimized by the moderator on the site
You switched from 32 bit to 64 bit without explanation. See "New > DWORD (32-BIT Value)" then after "6. In the Edit QWORD (64-BIT)". Which is it ? Or is it both?
This comment was minimized by the moderator on the site
Sorry for the confusion. It should be the DWORD (32-bit) Value. And I've fixed it in the tutorial. 🙂
This comment was minimized by the moderator on the site
You change from DWORD to QWORD at the end.
It should be DWORD
This comment was minimized by the moderator on the site
Thank you for bringing this to my attention. I've made the necessary correction in the tutorial.
This comment was minimized by the moderator on the site
Great! Thanks
This comment was minimized by the moderator on the site
This worked for me in Outlook for Office 365. Once point to clarify, the instructions flip-flop between DWORD and QWORD, which are mutually exclusive. I used DWORD and it worked.
This comment was minimized by the moderator on the site
I also didn't have a security folder. To get around the issue, I set a rule to forward all emails fitting a specific rule to IFTTT so I can use their automation instead. Won't work for everybody, and attachments get a long number added to them if saving to Dropbox.
This comment was minimized by the moderator on the site
what applet did you use on IFTTT, or did you make your own?
This comment was minimized by the moderator on the site
I set an email trigger, and set the action to be to save to Dropbox. However, I've since switched to Microsoft Flow for saving Gmail directly to Dropbox. My specific goal was to save Gmail attachments to Dropbox, and Flow worked best for that after IFTTT dropped support for reading emails from Gmail.
This comment was minimized by the moderator on the site
I Don't Have a security folder after HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook
This comment was minimized by the moderator on the site
It's because Microsoft has yet again changed something concerning this feature. Most likely, this registry key path has completely changed, or has been outright omitted. I have a Premier Support ticket open with MS currently to have them provide us the CORRECT registry setting for Office2016/2019 current monthly channel to bring the Run a Script in Rules Actions back. It is completely unacceptable for MS to continue to alter/omit features like this without clear & priority notification to clients. I understand the security risks behind using such a feature, but in certain scenarios, this still is used.
This comment was minimized by the moderator on the site
By playing around I found the correct key:
Computer\HKEY_USERS\{whichevertheuserkeyis}\Software\Microsoft\Office\16.0\Outlook\Security

So do not use HKEY_Current_User, instead use HKEY_USERS
This comment was minimized by the moderator on the site
This doesn't seem to work for Outlook 2013. Is there a method that will work for this version? Also, your instructions reference DWORD and the images imply QWORD.
This comment was minimized by the moderator on the site
For 2013 I used HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Security and DWORD EnableUnsafeClientMailRules with value 1.
Each version of office has its own folder in "HKEY_CURRENT_USER\Software\Microsoft\Office\"

You also need to allow the macro to run in outlook 2013:

File -> Options -> Trust Centre -> Trust centre settings
-> Macro settings -> "Notifications for all macros"

This will ask you to allow the macro the first time the rule runs, but be careful not to allow any other unknown macros during day to day use. You could also use a digitally signed macro, and only allow digitally signed ones to run.

Then create your script, create a rule that runs it, and you should be set.
This comment was minimized by the moderator on the site
Did not work for me.  I have Outlook 2013, but maybe now that Office 365 has overstepped this setting somehow.  I have the trust settings enabled to notify for all Macros.
This comment was minimized by the moderator on the site
DWORD or QWORD? A bit confusing to understand which to use... Had to create DWORD to make it work. Thanks
This comment was minimized by the moderator on the site
Do You have instructions how to enable this option also for outlook 2010?
This comment was minimized by the moderator on the site
Thank You! It worked for me and as mentioned in one of the comments below, Step 6 was DWORD dialogue box for me.
There are no comments posted here yet
Load More
Please leave your comments in English
Posting as Guest
×
Rate this post:
0   Characters
Suggested Locations