What files, libraries, ocx, exe, ... are impacted by the deprecations of VBScript?

Question

What files, libraries, ocx, exe, ... are impacted by the deprecations of VBScript?

Daniel Pineault 626

With Microsoft announcing the deprecation of VBScript, what are the files that will no longer be accessible?

which (dll, ocx, exe, ...) are going to be removed by the deprecation of VBScript
which com objects will be lost by the deprecation of VBScript
wscript.exe, cscript.exe are they being deprecated with this announcement?
Are vbscript.dll, Scrrun.dll, ... going to no longer exist, be accessible once VBScript is deprecated?
Which VB/VBA libraries (FSO, RegEx, ...) will be lost due to this announcement?
etc.

Some of this is discussed in: https://nolongerset.com/vbscript-deprecation/

The official announcement

Sadly neither offers any information whatsoever on the subject!

Can we get a clear and concise list of everything that will be deprecated/removed so we can properly determine the true impact of what is to come.

What's being removed?
What will remain, but not get updates?
etc.

These are critical questions that need answers for proper planning!

Instead of leaving us all guessing, it would be great to have a detailed blog post on this that everyone can refer to and get all the details on the matter! When such an important announcement is made, a detailed post should have been already available. I don't get making such announcements, creating worry and panic, and offering absolutely no information, no details on what is actually coming.

0 comments

2 answers

Your answer

Answer 1

Daniel Pineault 626

Anyone from Microsoft care to help us out here!?

MotoX80 37,681 Reputation points

2024-03-30T14:19:45.5833333+00:00

I don't work for Microsoft, but it might be that the reason that they don't answer your question is because they can't. I would expect that the Windows project managers and lead technicians will eventually decide what files are impacted and when.

The MS users on this forum may not be able to contact those developers and even if they could get an answer, they may be prohibited from providing any detail beyond the official announcement. Just speculation on my part.

Cacls.exe and wmic.exe have been deprecated and they are still in win11, so I would think that it's going to be a long time before the 4 files that you listed go away.

Is there some specific functionality that concerns you? I would think that a policy of "no new/updated .vbs files, write Powershell .ps1 scripts instead" would be a good start.
MotoX80 37,681 Reputation points

2024-03-30T14:55:38.3833333+00:00

I just noticed that your tag line says MVP. Can't you use that to contact the product teams?

https://mvp.microsoft.com/en-US/mvp/overview

Key BenefitsKey benefits to MVPs include early access to Microsoft products and direct communication channels with our product teams.
Daniel Pineault 626 Reputation points

2024-04-02T11:37:56.72+00:00

We've asked and got not answer. The MVP title doesn't truly get you any extra info! I didn't even get an acknowledgement of my question. Nada. Not the first time, won't be the last either. Microsoft likes Yes men/women, not those like me who ask real questions.
Daniel Pineault 626 Reputation points

2024-04-02T11:46:23.7133333+00:00

We're trying to understand what VBA libraries are going to be killed off because of VBScript's deprecations. Are FSO, RegEx, ... dead?

I have been unable to find any Microsoft resource that actually list the files/libraries driven by VBScript, but via VBA we know those 2 use the vbscript library, but I'm sure there are more we just aren't aware of.

So the real question for me is what VB/VBA libraries are dying along with VBScript's deprecation.

The article https://nolongerset.com/vbscript-deprecation/ raises much concern about this issue.
MotoX80 37,681 Reputation points

2024-04-02T12:40:16.0033333+00:00

Yeah, I don't know. It seems to me that they can't kill/cripple Office VBA. The impact on the worldwide user community would be massive.

Maybe the Office team takes ownership of scrrun.dll.

https://learn.microsoft.com/en-us/office/vba/language/reference/objects-visual-basic-for-applications
Daniel Pineault 626 Reputation points

2024-04-02T13:25:41.14+00:00

Sadly, Microsoft is already moving in a direction directly impacting VBA, I'm refering to the New Outlook not supporting any VBA automation, and they don't care. Sadly, Microsoft is slowly moving away from compatibility and truly caring about VBA. Because of such actions, I no longer assume they won't kill libraries and why I am asking for a direct answer from Microsoft.

Only they truly know and it would be nice of them to share such critical information.

Answer 2

Olaf Helper 47,616

With Microsoft announcing the deprecation of VBScript

What a strange question.

VBScript is deprecated, end of the storie, nothing more.

Has no effect on anything else, especially of file extension like "dll"; it's a file extension, nothing more.

Daniel Pineault 626 Reputation points

2024-04-02T11:33:33.52+00:00

Sadly, you do not understand the issue at hand. I've tried updating the original question to make it clearer as to what I am asking.

It's deprecation means we are loosing functionalities, loosing certain programming libraries, loosing access to specific dlls, ocx...

https://nolongerset.com/vbscript-deprecation/

The development community needs to understand which ones are going the way of the dodo and which will remain.

VBScript drives things like the FSO and RegEx libraries, are they dead too? So what VB/VBA libraries are being deprecated as a result of VBScript's deprecation?

For whatever reason Microsoft won't answer the simple question leaving developers in limbo!

Share via

What files, libraries, ocx, exe, ... are impacted by the deprecations of VBScript?

2 answers

Your answer