M. and Mrs. "Nonsense" have a child...
...it's called "Microsoft". 👶

During their early years of marriage, they had their first child, named "Microsoft IntelliSense". But with age, DNA weakens, and the couple welcomed their little brother, "Microsoft NonSense".

This kid tries to appear nice, but he's scattered. He actually suffers from severe ADHD.

• He tries to be a search engine but struggles to think better than his classmates, especially the top one, Google.
• He tried to make phones by buying the phone-making machine from his classmate "Nokia", but ended up messing it up and breaking it.
• He likes AI and befriended a classmate named "OpenAI" who was very talented in that field. But he clumsily tried to imitate him by building Copilot, and the pilot sent him crashing into a wall. The friendship with OpenAI didn't survive.

The cute little "Microsoft NonSense" inherited some wonderful toys from his big brother, like Windows 10 and the VBScript scripting engine. 🕹

But he decided he could do everything better than his big brother and started customizing, tweaking, and modifying these toys in a completely unstructured way. 👾

He drew a big number "11" on Windows 10 with a marker and replaced the working code with code generated by Copilot. His parents tell him it's good and congratulate him, but secretly they still prefer using Windows Millennium Edition instead of Windows 11.

And now that Microsoft NonSense is completely overwhelmed, he throws a tantrum and decides to literally smash his big brother's toys, especially VBScript.

He doesn't realize the consequences of his actions. 🤦‍♂️ We must bring him to his senses.

• ‼️ Enterprise Automation : Countless companies have built their CRM and Management tools using the Office + VBA + VBS files stack over the years. They are DEEPLY intermangled. SAP GUI scripting uses VBScript too. SAP documentation notes impacts on GUI scripting if VBScript is removed; environments that rely on VBScript for automation hooks will fail. This will disrupt organizations relying on it. Worldwide Economy is just in a catastrophic situation from a financial point of view, resource availability, environmental impact, and confidence in the future. Driving thousands of businesses into bankruptcy and putting their employees out of work is a stroke of genius. 👏 Applause for Microsoft NonSense.

• ‼️ Microsoft Tools : Microsoft's own dependencies list on VBS: take a coffee. A lot of long-established tools within the Microsoft ecosystem rely on VBScript, without any sign that they will be replaced by signed PowerShell scripts, modules or cmdlets :
  • Office Activation (ospp.vbs)
  • Windows Activation (slmgr.vbs)
  • Printer VBS scripts in c:\windows\system32
  • Intune/Autopilot
  • Microsoft Deployment Toolkit (MDT / TSS)
  • Countless analysis, performance diagnosis and auditing scripts, tools, toolkits (Security Compliance Toolkit, Debug Diagnostics Tools, WMI Tools, and so on)
  • List stopped for brevity. 👏 Applause for Microsoft NonSense.

• ‼️ Installers : Graphic Cards and maaaany other hardware vendors use VBScript as part of their deployment and packaging solutions. The first of these being MSI Installer. Even non-MSI installers can embed or launch VBScript scripts for validation or configuration. NVIDIA driver installers. Intel drivers and chipset packages. OEM utilities that wrap driver installations with scripted logic. These will just purely break: your hardware JUST becomes a brick. MSI Custom Action Types 6, 22, 38, and 54 using VBScripts? Just not working anymore. At All. Any news or alternatives for installation package makers in the official docs? Absolutely none. Almost all Deployment packages available on this planet for the last decades in Windows make intensive use of VBScript because it is efficient and convenient for plugging and gluing things like (excuse the understatement) :
  • Modify registry settings
  • Check system prerequisites
  • Stop/start services
  • Configure application state
  • Validate system configuration
  • Cleanup previous versions
  • Without VBScript, these custom actions fail. 👏 Applause for Microsoft NonSense.

• ‼️ Classic ASP Websystems and applications : A major impact if Microsoft NonSense decides to remove the VBScript engine. Approximately 5,000,000 enterprise intranets and corporate tools still rely on VBScript. If they have survived to this day, it is because they are well maintained, mature, and indispensable. Pages that execute VBScript on the server will break if the underlying VBScript engine is removed, as ASP uses the Active Scripting VBScript engine by default. Uninstalling the VBScript FOD completely breaks the ASP ISAPI module in IIS. 👏 Applause for Microsoft NonSense.
  • No, Applause should definitely go to Pieter Cooreman for ASP4 and Lucas Guimarães for AxonASP. Seriously? Do we, independent developers, have to develop platforms capable of running Classic ASP applications that are mission-critical for our numerous and renowned clients? Some of the most active developers, dedicated to the ASP platform, know its value and its essential role. Should they be trying to recreate runtimes in their spare time, for $0 ?
    • Microsoft net income (profit) is $101.83 billion in 2025.
    • It's simply shameful to offload this onto independent developers.
    • Microsoft should open-source the Classic ASP VBScript engine, or make it sustainable and integrated within IIS itself.

• ‼️ System Administration : System Administrators that do not use Linux but Microsoft Windows Server products play a great role in the adoption of Microsoft solutions within their company. So they have played by Microsoft rules: build administration tools using Microsoft tools. Using VBScript, PowerShell, CMD, WMI, WSH, even HTA. As a reward, Microsoft says "Thank you SysAdmins: see you in hell". Should they audit and map EVERY piece of their company infrastructure? They can't. Because these infrastructures are quite BIG and were built by some people who left the company years ago, the actual SysAdmins only being maintainers of these perfectly working legacy tools.
  • Login scripting
  • System configuration
  • Automated tasks
  • Deployment tasks
  • Scheduled Tasks invoking .vbs
  • All Gone. 👏 Applause for Microsoft NonSense.

• ‼️ MS Office : Microsoft NonSense is reinventing the scrrun.dll and vbscript.dll in the Office vbe7.dll. This action proves that he secretly admits the need for these libraries. He is currently coding something to replace what he is about to remove. The same thing. Where does the logic reside?. 👏 Applause for Microsoft NonSense.

Microsoft NonSense should pay for auditing and migrating all of this. He will not because he's a difficult child. 🤑

While Microsoft is increasingly using AI to shorten development cycles in order to replicate the excellent Windows Millennium Edition by renaming it Windows 11, and companies like Nvidia being forced to release patches to address the flaws in the OS itself, it seems clear that removing VBScript support from Windows is not relevant.

"Legacy" isn't an insult. Everything is already in place within companies to use Classic ASP + VBScript securely: access rights, dedicated user accounts, ACLs, antivirus systems, monitoring, sandboxes, restricted IIS Application Pools, backups, and replicas. The security argument to deprecate VBScript is similar to invoking "AI" for firing employees nowadays. A lie.

✅ VBScript is perfect at gluing things : Mount shared devices, configure printers, apply user parameters, read/write Registry, interop between databases, filesystems, COM components, even manipulate PowerShell and CMD stdout. Classic ASP is perfect at the same task.

☘️🤞Hey, lil child, just keep VBScript and Classic ASP afloat. You will make your parents proud of you.