在VBS中嵌套多引号单行运行含环境变量的PowerShell代码问题

Got it, let's fix that nested quoting mess and get your MSHTA command working smoothly for the login scheduled task. Here's the breakdown and final working solution:

The biggest pain here is handling quote escaping across three layers (MSHTA, VBS, PowerShell) while making sure the $env:USERDNSDOMAIN variable is parsed correctly by PowerShell. Let's break this down step by step.

Key Rules to Follow #

• In VBS, double quotes inside a string must be escaped with another double quote ("").
• When passing commands to PowerShell via -Command, paths with spaces need proper quoting, and environment variables must be left intact so PowerShell (not VBS) resolves them.
• Each nested layer requires escaping quotes one more level deep.

Final Working Command #

mshta vbscript:Execute("CreateObject(""Wscript.Shell"").Run ""powershell -NoLogo -Command """"& '\\\\$env:USERDNSDOMAIN\\FOLDER1\\FOLDER with Spaces\\Folder3\\YourScript.ps1'"""" , 0, False""; window.close")

Breakdown of the Quoting Logic #

1. VBS Wrapper: The entire VBS snippet is wrapped in vbscript:Execute("..."). Inside this, we use "" to escape every double quote needed for VBS syntax (like CreateObject(""Wscript.Shell"")).
2. PowerShell Launch: The Run method's command argument is wrapped in ""powershell ...""—this escapes the entire PowerShell command string for VBS.
3. PowerShell -Command Handling: To pass the quoted UNC path to PowerShell, we use """" (which becomes a single " after VBS parses it). This ensures PowerShell recognizes the spaced path as a single string.
4. Environment Variable & UNC Path: $env:USERDNSDOMAIN is left unmodified so PowerShell resolves it. We double all backslashes (\\\\) so VBS passes the correct \\ prefix for the UNC path to PowerShell.
5. Window Behavior: The , 0, False flag hides the PowerShell window (ideal for scheduled tasks) and doesn't wait for the script to finish. window.close immediately closes the MSHTA GUI window after triggering the command.

Quick Test Tip #

Before setting up the scheduled task, run the command directly in Command Prompt. You should see the MSHTA window flash briefly, and your PowerShell script should execute in the background—this confirms the quoting and variable resolution work as expected.

内容的提问来源于stack exchange，提问作者montag