July 7, 2017 10:30 am

An update on disabling VBScript in Internet Explorer 11

Beginning in the Windows 10 Fall Creators Update, we intend to disable VBScript execution in IE 11 for websites in the Internet Zone and the Restricted Sites Zone by default, to provide a more secure experience. This change was initially announced in a blog post in April. The new default behavior can be previewed beginning with today’s Windows Insider Preview release, build 16237.

For customers on previous versions of Windows, we intend to include this change in future cumulative security updates for Internet Explorer 11.The settings to enable, disable, or prompt for VBScript execution in Internet Explorer 11 will remain configurable per site security zone, via Registry, or via Group Policy, on released versions of Windows. We will continue to post updates here in advance of these changes to default settings for VBScript execution in Internet Explorer 11.

To provide feedback on this change, or to report any issues resulting from this change in Windows Insider Preview, you can use the Feedback Hub app on any Windows 10 device. Your feedback goes directly to our engineers to help make Windows even better.

— Brent Mills, Senior Program Manager

Join the conversation

  1. Hi Brent,

    Could you describe what effect this will have on IE11 running in compatibility mode, such as “IE=EmulateIE8”? Is VBScript being disabled regardless of the compatibility mode?

  2. You talk about older versions of Windows, but this also includes Windows Server 2016, as IE11 is presently the only option. If IE11 is dead, what is going to happen with Windows Server 2016 and beyond? Is Microsoft Edge going to an option any time soon?

  3. This is an historic move indeed. VBScript is breathing its last gasps, and soon, will be gone for good.

  4. Hi, the instructions on how to enable VB Script for Win 10 Pro (update 1709 Fall Creators Update) doesn’t work. I am still getting errors due to web app not allowed to run VB Script. Note that this is not an issue with Win 10 Enterprise (update 1709 Fall Creators Update).
    I tried all suggestions to fix this from this link:

    Does anyone know of other workarounds for this? Or maybe there was something missing from the steps in the link above?
    I will be ripping out the VB Script anyway now that it is in its death throes, but it would be nice to have a workaround until new code gets pushed.