Sandbox 啟用後執行，如果經過微軟商店更新，就會造成無法正常啟動Sandbox

When the above script works for you, you can apply the following script to work with customized configuration files, i.e., wsb files.

run_sandbox_with_wsb.ps1

# ==========================================
# 1. Receive external WSB file path parameter
# ==========================================
param(
    [string]$TargetWsb
)
# Resolve working directory switching issue during Admin elevation; record the initial script folder
$ScriptDir = $PSScriptRoot
if ([string]::IsNullOrEmpty($ScriptDir)) { $ScriptDir = Get-Location }
# If the user did not drag-and-drop or pass a file, automatically pop up a file picker window
if ([string]::IsNullOrEmpty($TargetWsb)) {
    Add-Type -AssemblyName System.Windows.Forms
    $FileBrowser = New-Object System.Windows.Forms.OpenFileDialog
    $FileBrowser.Filter = "Windows Sandbox Config (*.wsb)|*.wsb"
    $FileBrowser.InitialDirectory = $ScriptDir
    $FileBrowser.Title = "Select a WSB configuration file"
    
    if ($FileBrowser.ShowDialog() -eq "OK") {
        $TargetWsb = $FileBrowser.FileName
    } else {
        Write-Warning "No WSB file selected. Exiting..."
        Start-Sleep -Seconds 2
        exit
    }
}
# Critical Fix: Force relative path conversion to system absolute path
if (-not [System.IO.Path]::IsPathRooted($TargetWsb)) {
    $TargetWsb = Join-Path $ScriptDir $TargetWsb
}
# Fail-safe check: Intercept and prevent sandbox launch if the file does not exist
if (-not (Test-Path $TargetWsb)) {
    Write-Error "Error: The WSB file '$TargetWsb' does not exist!"
    Pause
    exit
}
# ==========================================
# 2. Force Admin UAC Prompt (Pass absolute path fully)
# ==========================================
if (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Start-Process powershell.exe -ArgumentList "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`" -TargetWsb `"$TargetWsb`"" -Verb RunAs
    exit
}
# ==========================================
# 3. Core Logic (Run as Admin)
# ==========================================
$IntelDevice = Get-PnpDevice -FriendlyName "*Intel*Graphics*" -ErrorAction SilentlyContinue
if ($null -eq $IntelDevice) {
    Write-Error "Cannot find Intel Graphics Device."
    Pause ; exit
}
$IntelID = $IntelDevice.InstanceId
# Execution
Write-Host "Target Config: $TargetWsb" -ForegroundColor Cyan
Write-Host "[1/3] Disabling Intel GPU temporarily..." -ForegroundColor Yellow
pnputil /disable-device $IntelID
Write-Host "[2/3] Launching Windows Sandbox with selected WSB..." -ForegroundColor Green
# Enclose path with double quotes to prevent parsing errors caused by spaces in the path (e.g., OneDrive or workspace)
Start-Process "C:\Windows\System32\WindowsSandbox.exe" -ArgumentList "`"$TargetWsb`""
Write-Host "Waiting for Sandbox initialization (5s)..." -ForegroundColor Cyan
Start-Sleep -Seconds 5
Write-Host "[3/3] Re-enabling Intel GPU..." -ForegroundColor Green
pnputil /enable-device $IntelID
Write-Host "All done!" -ForegroundColor Cyan
Start-Sleep -Seconds 2

1. 執行 Disable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -Online 後 重新啟動
2. 執行 Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -Online 後再次重新啟動
3. 啟動後，在 Applications and Services Logs > Microsoft > Windows > 沒有找到 Sandbox-Unit 這個目錄
4. 停留在 Sandbox 卡在啟動畫面「Windows Sandbox」轉圈
5. 此次 微軟商店雖然設定為 應用程式更新 暫停一周，但仍被觸發更新，一開始啟動是舊的視窗樣式，也是跳出 與「 Windows 沙箱環境的連線已中斷，是否要重新連線?」

使用平台：

OS: win 11 pro 25H2 26200.7623

Dell NB, G15 with NVIDIA Geforce RTX 4060 Laptop GPU, Driver: 32.0.15.8195