2.4 KiB
Troubleshooting
Pester is not installed
Install Pester for the current user, then rerun the test runner:
Install-Module Pester -Scope CurrentUser -Force
.\Tests\\Run-AllTests.ps1
Script reports that administrator privileges are required
Apply, Repair, Restore, UpdatePortable, and Windows configuration changes require an elevated Windows PowerShell window. Use Plan, Audit, HealthCheck, or CreateWorkspace when elevation is not available.
A shared drive is unavailable
The setup expects S: for shared automotive data and P: for shared portable applications. HealthCheck reports their availability and labels. Portable applications fall back to the local C:\Automotive\PortableApps path when P: is unavailable, but shared profile data remains unavailable until the drive is mounted.
A download is blocked as insecure
Downloads must use HTTPS. HTTP is rejected unless the caller explicitly marks a documented vendor exception. The current exception is limited to the Xhorse assets whose vendor CDN does not provide HTTPS. Verify the vendor network/VPN path and confirm the URL before retrying.
A portable download fails hash or signature validation
Do not bypass the failure. Preserve the downloaded file, compare its SHA256 value with the trusted vendor release information, and inspect the Authenticode status. Remove the file only after the incident has been recorded. Update Config\\portable-apps.json only with a verified expected hash.
Resume after restart
Check C:\Automotive\Config\\.workstation-setup-state.json or the configured local root for the last checkpoint. Resume with the same profile and -ResumeFromCheckpoint. Completed work is revalidated because installers and vendor packages can change between runs.
Workspace creation fails
CreateWorkspace requires -JobId, -Manufacturer, and -Model. Job IDs, manufacturers, and models cannot contain path separators or Windows filename characters. Use a simple value such as VW001, Volkswagen, and Golf.
OEM or communication software installation
The setup does not silently install licensed OEM suites. Use the vendor installer, complete licensing and device registration on the current Windows installation, and verify J2534/USB drivers separately. Keep other isolated Windows installations without drive letters while working in the current profile.