Microsoft to Disable VBScript in IE 11 in Windows 7 and 8.x

Continuing a years-long push to phase out its insecure legacy technologies, Microsoft has announced a new milestone for VBScript. This month, it will disable VBScript by default in Internet Explorer 11 running under Windows 7, 8, and 8.1.

“The change to disable VBScript will take effect in the upcoming cumulative updates for Windows 7, 8, and 8.1 on August 13, 2019,” the Microsoft Edge team revealed. “VBScript will be disabled by default for Internet Explorer 11 and [web browser controls] for Internet and Untrusted zones on all platforms running Internet Explorer 11. This change is effective for Internet Explorer 11 on Windows 10 as of the July 9th, 2019 cumulative updates.”

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

For those unfamiliar with VBScript, it’s a scripting language based on classic Visual Basic that first launched in 1996 alongside JScript, Microsoft’s 90s take on JavaScript. VBScript could be used on both the client- and server-sides on the web, but because the client version was only supported in Internet Explorer, it didn’t gain much traction against JavaScript, which was universally supported. VBScript did see some success on the server, however, as it could be used to power database-backed websites running on Microsoft’s Internet Information Server (IIS) using Active Server Pages (ASP).

VBScript was also used for writing scripts—basically more modern versions of MS-DOS batch files—that ran under the Windows Scripting Host (WSH) starting in Windows 95 (later renamed Windows Script Host). And it was briefly used as a scripting language in just one Microsoft Office application, Outlook 97. It was even used in Windows CE.

But by the turn of the century, Microsoft was transitioning to .NET and VBScript was left behind. Microsoft transitioned Office to Visual Basic for Applications (VBA), it utilized Visual Basic .NET for both client- and server-side development, and it eventually replaced WSH with PowerShell. By the 2010s, Microsoft explained that VBScript was deprecated and “should no longer be used as a scripting language.” It was only permitted for websites rendered in legacy document modes, and then only in IE 11.

In 2017, Microsoft released a cumulative update for Windows 10 that included an option for blocking VBScript execution in IE 11 for all document modes. And it noted that it would disable VBScript entirely in some future update. That day has arrived: Microsoft disabled VBScript by default in IE 11 on Windows 10 in July, and it is doing so today on all remaining supported Windows versions.

“Should you still need to utilize this legacy scripting language, the settings to enable or disable for VBScript execution in Internet Explorer 11 will remain configurable per site security zone, via Registry, or via Group Policy,” Microsoft notes.

Normally, I would assume that once IE 11 is no longer supported, Microsoft would officially kill VBScript for good. But IE 11 will be supported for the supported life of Windows 10, which is currently indefinite. I assume that will have to change at some point. But for now, VBScript continues forward, albeit in dramatically diminished form.

Share post

Please check our Community Guidelines before commenting

Conversation 15 comments

  • MikeGalos

    03 August, 2019 - 10:31 am

    <p>Actually, JScript became the standard (ECMA 262) for the proprietary Javascript because, among other things, it was Y2K compliant. Javascript, despite being designed in the mid-1990s, treated all years as "19" + the 2-digit year.</p><p><br></p><p>What you use today as Javascript really is the Microsoft version.</p>

    • RonH

      Premium Member
      03 August, 2019 - 10:54 am

      <blockquote><em><a href="#447216">In reply to MikeGalos:</a></em></blockquote><p>That is an interesting tidbit</p>

  • webdev511

    Premium Member
    03 August, 2019 - 10:58 am

    <p>I had that book and used it too. Got me started with ASP 1.0 page development which I rode all the way to ASP 3.0. </p>

  • skane2600

    03 August, 2019 - 12:10 pm

    <p>Hopefully outside of IE, it is still supported on Windows (although what is inside and outside IE is ill-defined). VBScript has automation capabilities that VBA doesn't have, namely the ability to automate Office programs (and others) from the outside. Also it was a option that avoided all the version issues that plagued .NET. </p><p><br></p><p>It obviously wasn't something you'd use to create a stand-alone application of any significance but as a scripting language it was quite useful.</p>

  • hrlngrv

    Premium Member
    04 August, 2019 - 5:08 pm

    <p>Meta: I got an error trying to post the comment below when I had included <strong>dot</strong> and <strong>EXE</strong> following CMD. When I deleted the extension, posting worked. That's some awfully fussy text filtering.</p>

    • hrlngrv

      Premium Member
      04 August, 2019 - 5:12 pm

      <p>VBScript was MSFT's response to Unix-originated scripting languages. Python won that particular war.</p><p>FWIW, I was tasked with converting some front-ends from batch files to VBScript. VBScript was more of a PITA for several things, especially for what CMD batch files could handle.</p><p>This had better not mean removing the Windows Script Host (actual name, not <em>Script</em><strong><em>ing</em></strong>) DLLs. Excel may be getting regular expression functions, but the Dictionary object is very useful in VBA.</p>

      • skane2600

        04 August, 2019 - 8:50 pm

        <blockquote><em><a href="#447342">In reply to hrlngrv:</a></em></blockquote><p>VBScript support being included as part of Windows' standard install made the existence of other scripting languages somewhat moot on Windows. Not a matter of quality or power, but of practicality. </p><p><br></p><p>Yes, the potential removal of wscript.exe was what I was concerned with along with mshta.exe.</p>

      • wright_is

        Premium Member
        05 August, 2019 - 2:52 am

        <blockquote><em><a href="#447342">In reply to hrlngrv:</a></em></blockquote><p>The article only says it is being removed from IE.</p>

        • skane2600

          05 August, 2019 - 9:31 am

          <blockquote><em><a href="#447348">In reply to wright_is:</a></em></blockquote><p>The concern stems from the fact that a number of these technologies were bundled as part of IE (recall MS's legal argument was that removing IE would break Windows) and thus could be in jeopardy depending on how Microsoft plays it.</p>

        • hrlngrv

          Premium Member
          05 August, 2019 - 4:42 pm

          <p><a href="; target="_blank"><em>In reply to wright_is:</em></a></p><p>Perspective is important. From the perspective of someone who used Excel on a daily basis and maintains a lot of VBA code, the form of deprecation of the SQLREQUEST add-in makes it prudent to be concerned for the worst.</p>

  • sharpsone

    05 August, 2019 - 11:49 pm

    <p>RIP vbscript you saved my ass many times. </p>

  • harris0n

    06 August, 2019 - 11:58 am

    <p>Paul, VBScript is alive and well on the server side (as you know?). My company's site source code contains thousands of lines of it, among newer code. And my company is not alone. The prospect of 'officially killing VBScript for good'? – nowhere near reality. The story is spooking executives, for no reason other than an unfamiliarity with client-side / server-side concepts.</p>

  • gelfer

    Premium Member
    07 August, 2019 - 7:43 am

    <p>Hey Paul, a new experience: dutch book title written by you! Did not know it existed. Maybe your Amsterdam house-swap friend helped with the translation? </p><p>BTW: keep up the good work on this site &amp; the programming windows series, I'm really enjoying them and learning a lot!</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC