3d31a39099
Invoke-Odt returned $true unconditionally after setup.exe, so a failed or not-yet-finished Click-to-Run install surfaced only as a bare "ospp.vbs not found after install". Root-cause fixes: - <Logging> in the config XML -> a capture dir, read back on failure so the real setup.exe exit code / error is reported (and sent as telemetry). - setup.exe run with -PassThru; non-zero (not 0/3010) exit -> fail + log tail. - Wait-OfficeInstalled polls on-disk state (ospp.vbs + ProductReleaseIds) instead of trusting setup.exe's early return under Display Level=None. - After removing incompatible consumer Office (e.g. O365HomePremRetail), a pending reboot now stops the run with reboot+re-run guidance rather than half-completing the VL install in the same session (idempotent on re-run). |
||
|---|---|---|
| .. | ||
| css | ||
| js | ||
| scripts | ||