VBScript is deprecated

[Acters]

As of right now, there are a lot of references and uses in the scripts to slmgr.vbs and ospp.vbs for activation and checking status.
How will this be handled once future releases of windows remove VBScript functionality? (Windows 11 allows for VBS to be optionally removed)
Will the MAScripts transition to PowerShell script alternatives?

[WindowsAddict]

It's already using WMI directly instead of slmgr.vbs tool for activation-related commands. In very few places, the script relies on slmgr.vbs, we can easily add alternative commands.
Furthermore, I don't think they will make it unavailable by default, they will most likely treat it as they did with wmic.exe, available by default but can be removed.

[Tragen]

The newest Windows 11 installations have it disabled by default and can enable it if needed.
We will see if it's needed. I used it often for small things. It was nice and easy.

[WindowsAddict]

@Tragen they did the same thing with wmic.exe as well, at first in insider builds they removed it but later in public release, they added it back and made it available by default.

[Meyers07]

Just a suggestion, when the time come where VBS didn't became part of Windows anymore, there should be either:
-a guide to users to install VBS again
-a drop in replacement for VBS commands
because as i see most of the codes still rely on slmgr vbs and i often use older apps (such as game mod tools) that rely on VBS.

[WindowsAddict]

@Meyers07 so far vbs is not removed in any insider build of Windows. I'll replace all the vbs codes with wmi/powershell in next update of MAS.

[kdejeqq]

Ok thank you very much for your hard work 😉💪 Le dim. 19 nov. 2023, 14:23, WindowsAddict ***@***.***> a écrit :

…

@Meyers07 <https://github.com/Meyers07> so far vbs is not removed in any insider build of Windows. I'll replace all the vbs codes with wmi/powershell in next update of MAS. — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP4KDEJHLDCVSSUGBUCFPZTYFIB4TAVCNFSM6AAAAAA53ZZQY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHA2TIMRWHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[Meyers07]

@Meyers07 so far vbs is not removed in any insider build of Windows. I'll replace all the vbs codes with wmi/powershell in next update of MAS.

Nice idea though keep provide fallback methods (as in the methods that still use vbs) as within Windows itself, the method how to see license types verbosely can only be done thru slmgr vbs, let me know if powershell can do slmgr too.

[WindowsAddict]

@Meyers07 so far vbs is not removed in any insider build of Windows. I'll replace all the vbs codes with wmi/powershell in next update of MAS.

Nice idea though keep provide fallback methods (as in the methods that still use vbs) as within Windows itself, the method how to see license types verbosely can only be done thru slmgr vbs, let me know if powershell can do slmgr too.

Every use of slmgr.vbs can be replaced by wmi/powershell in the script.

[Acters]

It's already using WMI directly instead of slmgr.vbs tool for activation-related commands. In very few places, the script relies on slmgr.vbs, we can easily add alternative commands. Furthermore, I don't think they will make it unavailable by default, they will most likely treat it as they did with wmic.exe, available by default but can be removed.

The bigger idea is to move towards deprecating all VBS related functions and calls as there are PS equivalents of both slmgr.vbs and ospp.vbs capabilities that can be used instead without regressions or loss of function. I am glad to hear these scripts will be replaced.

Someone made a "drop in" replacement to the usual scripts that made use of slmgr.vbs functions. The major command doing the heavy lifting is the new CIM, Get-CimInstance. Found here: https://gist.github.com/zbalkan/4ba92656a3a8387e6b220bcf8fcd5fc6

Only difference between WMI and CIM is on how it communicates with remote systems. WMI is allegedly deprecated because it is windows only, while CIM can be multiplatform.

OSPP is similar but it is specific to office. The Get-CimInstance command can still work for this purpose. website with decent documented Powershell equivalents https://woshub.com/checking-office-2016-365-activation-status/

[WindowsAddict]

Looks like they have dropped the idea of removing VBS support by default in the upcoming RTM build, its available by default. VBS uses will be removed from MAS anyway, closing this issue here now.