Microsofthi Naveen_Shankar I am seeing the following error when installing AMD Chipset drivers. Appears like Microsoft should talk with AMD here.
The point is that - thankfully - vbscript optional feature is no longer installed in Windows 11 25H2.
repro:
Across the log there are different actions that invoke vbscript.
Action 21:36:12: INSTALL. Action start 21:36:12: INSTALL. MSI (c) (48:90) [21:36:12:899]: UI Sequence table 'InstallUISequence' is present and populated. MSI (c) (48:90) [21:36:12:899]: Running UISequence MSI (c) (48:90) [21:36:12:899]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'. MSI (c) (48:90) [21:36:12:899]: Skipping action: MSIExtract_MUP (condition is false) MSI (c) (48:90) [21:36:12:899]: Skipping action: ExitExtractionSetup (condition is false) MSI (c) (48:90) [21:36:12:899]: Doing action: DetectAMD Action 21:36:12: DetectAMD. Action start 21:36:12: DetectAMD. MSI (c) (48:E4) [21:36:12:902]: Cloaking enabled. MSI (c) (48:E4) [21:36:12:902]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (48:E4) [21:36:12:902]: Connected to service for CA interface. MSI (c) (48:30) [21:36:12:939]: Note: 1: 2738 Info 2738.Could not access VBScript run time for custom action . Action ended 21:36:12: DetectAMD. Return value 1. MSI (c) (48:90) [21:36:12:940]: Doing action: ISSetAllUsers
Remediation: Optional Features > Added vbscript
The AMD drivers installation probleme encountered by Karl-WE is only an ONE EXAMPLE of the countless applications that will break with this insane VBScript deprecation, motivated by nothing.
Why is https://www.change.org/p/ask-microsoft-to-cancel-their-planned-removal-of-vbscript-classic-asp growing ? Because this decision was absurd and dangerous.
Naveen_Shankar We are still desperately waiting for updates on the CLASSIC ASP platform, that is widely used by businesses, and big ones.
Hi AlexLaforge I do not have an opinion about the security aspect of vbscript.
Is it required that VBscript uses UAC when operating outside its security context?
Is it possible to sign VBscript so tampering will prevent execution?
The named driver is a very recent one and its failure shows that the ecosystem (Partners) seem not to be up to par with the speed of the deprecation process.
I believe that I have commented it earlier a number of Microsoft own stack uses vbscript still. And this has to change SOON™️.
And these are likely changed that are intrusive, should be down-level OS when security is a reason.
This means customers and users need a solution that will target:
There are a lot of items within the ecosystem of Microsoft that still rely on vbscript and I see no movement that they are replaced by signed PowerShell scripts or better PowerShell 7 modules / commandlets, as expected.
I would like to recommend that Naveen_Shankar and the teams, as this is a cross PG effort including Core OS, might look into a better and faster adoption rate by Microsoft internally and vendors, such as AMD, at the point when W11 25H2 has already raised the bar.
partial output of vbscripts in a Windows 11 25H2 installation
