Hi Palmer, Michael,
Thank you for your question regarding BGInfo and VBScript deprecation.
Currently, Microsoft has not announced official plans for PowerShell support in BGInfo or provided guidance on how the tool will handle the VBScript deprecation timeline. While BGInfo continues to receive updates (most recently version 4.33 in February 2025), there has been no public communication from the Sysinternals team about this specific concern.
Given the VBScript deprecation timeline you mentioned, with Phase 2 expected around 2027 where VBScript will be disabled by default, this is certainly a valid concern for BGInfo users who rely on custom field scripting functionality.
I'd recommend monitoring the official blog and release notes for any announcements. You may also want to submit feedback directly to Microsoft through official channels to help raise visibility of this requirement.
In the interim, you can continue using BGInfo as normal. When Phase 2 arrives, VBScript can still be manually enabled as a Feature on Demand if needed, though this wouldn't be a long-term solution given Phase 3's complete removal.
If you need immediate PowerShell-based alternatives, there are community-developed solutions available, though I understand that doesn't address your question about Microsoft's official plans for BGInfo itself.
I hope this clarifies the current status.
Best regards