Note: The other languages of the website are Google-translated. Back to English
Log in Register

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

You may have noticed the run a script option disappears from the Rules wizard after an Office update. That will prevent users from creating Outlook rule with VBA script. This article will introduce a way to restore the missing run a script option in the Outlook rules wizard easily.

Restore missing Run a script option in Outlook 2016

Restore missing Run a script option in Outlook 2016

To restore the missing run a script option in the Outlook rules wizard, please do as follows:

1. Press Win + R keys together to open the Run dialog box, in the dialog box type regedit in the Open box, and click the OK button. See screenshot:

2. In the popping out User Account Control dialog box, please click the Yes button. See screenshot:

3. In the Registry Editor window, please open the Security key with below path:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security

4. Right click the Security key, and select New > DWORD (32-BIT Value) from the right-clicking menu, and then name the new DWORD as EnableUnsafeClientMailRules. See screenshot:

5. Double click the EnableUnsafeClientMailRules DWORD to open the Edit QWORD Value dialog box. See screenshot:

6. In the Edit QWORD (64-BIT) Value dialog box, type 1 in the Value data box, and click the OK button. See screenshot above.

7. Restart your Microsoft Outlook.

And now you will find out the run a script option in the Step 1: Select action (s) of Rules Wizard.

Related Articles

Kutools for Outlook - Brings 100 Advanced Features to Outlook, and Make Work Much Easier!

  • Auto CC/BCC by rules when sending email; Auto Forward Multiple Emails by custom; Auto Reply without exchange server, and more automatic features...
  • BCC Warning - show message when you try to reply all if your mail address is in the BCC list; Remind When Missing Attachments, and more remind features...
  • Reply (All) With All Attachments in the mail conversation; Reply Many Emails in seconds; Auto Add Greeting when reply; Add Date into subject...
  • Attachment Tools: Manage All Attachments in All Mails, Auto Detach, Compress All, Rename All, Save All... Quick Report, Count Selected Mails...
  • Powerful Junk Emails by custom; Remove Duplicate Mails and Contacts... Enable you to do smarter, faster and better in Outlook.
shot kutools outlook kutools tab 1180x121
shot kutools outlook kutools plus tab 1180x121
 
Comments (23)
No ratings yet. Be the first to rate!
Mickael
Guest
This comment was minimized by the moderator on the site
Seems to be working even though in step 6 it's the DWORD dialog box that opens up on my end. Thank you very much!
Mickael
Reply
Rob
Guest     Mickael
This comment was minimized by the moderator on the site
Worked in that it shows up but will not run the script when called any ideas?
Rob
Reply
Luis Astudillo
Guest     Rob
This comment was minimized by the moderator on the site
Don't run the script.
Luis Astudillo
Reply
Anil
Guest     Rob
This comment was minimized by the moderator on the site
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" or allow all macros
Anil
Reply
Gideon
Guest
This comment was minimized by the moderator on the site
It seems to block my incoming mail when the rule holds.
Gideon
Reply
kelly001
kelly001     Gideon
This comment was minimized by the moderator on the site
Hi Gideon,
This article just guilds you to restore the “Run a script” option when creating rules in Outlook, it won’t create any rules at all.
What about checking outlook rules you created and disabling them in the Rules and Alerts dialog?
kelly001
Reply
Report
Bblz
Guest
This comment was minimized by the moderator on the site
This is perfect! Solved my problem!! Had a few software updates the other day and my scripts in my Outlook rules stopped working. Didn't even have the option to create a new rule to run the script. All fixed now! Step 6 was the DWORD dialogue box for me.
Bblz
Reply
abhi
Guest
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.
abhi
Reply
Rafal
Guest
This comment was minimized by the moderator on the site
Do You have instructions how to enable this option also for outlook 2010?
Rafal
Reply
Espen
Guest
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
Espen
Reply
Jason
Guest
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.
Jason
Reply
Lukie
Guest     Jason
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.
Lukie
Reply
Marine
Guest     Lukie
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.
Marine
Reply
Sagar
Guest
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
Sagar
Reply
IT Engineer
Guest     Sagar
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.
IT Engineer
Reply
Azza
Guest     IT Engineer
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
Azza
Reply
FerretWilliams
Guest
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.
FerretWilliams
Reply
dan
Guest     FerretWilliams
This comment was minimized by the moderator on the site
what applet did you use on IFTTT, or did you make your own?
dan
Reply
FerretWilliams
Guest     dan
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.
FerretWilliams
Reply
Ethan H
Guest
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.
Ethan H
Reply
Max
Guest
This comment was minimized by the moderator on the site
Great! Thanks
Max
Reply
Joseph Longoria
Joseph Longoria
This comment was minimized by the moderator on the site
You change from DWORD to QWORD at the end.
It should be DWORD
Joseph Longoria
Reply
Report
Graham
Guest
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?
Graham
Reply
There are no comments posted here yet
Leave your comments
Guest
Posting as Guest
Login
×
Rate this post:
Reset
0  Characters
Suggested Locations