v1.4.1 — Phase 08 prerequisite download folder
[1.4.1] - 2026-08-14
Bug-fix release. Fixes #1,
reported by @ehindola.
Fixed
-
Phase 08 failed deterministically when no offline prerequisite cache
was staged.Install-CMSiteonly createdC:\Install\CM-PreReqsas a
side effect of pushing an offline cache, insideif ($CMPreReqsPath).
With no cache staged that block is skipped entirely -- but the generated
unattend INI still pointsPrerequisitePathat that folder, and CM setup
does not create its own download folder. Setup aborted in about 30
seconds withWARNING: Download folder C:\Install\CM-PreReqs does not existandFailed to download product updates (0x80070003)
(ERROR_PATH_NOT_FOUND). The folder is now ensured unconditionally
before the INI is written, on both the cached and download paths.This branch was never exercised in testing: every verified end-to-end run
hadC:\LabSources\SoftwarePackages\CM-Prereqsstaged, so
Install-HomeLab's auto-discovery always found a cache and the folder
always got created incidentally. -
A hard setup failure was reported as "in progress" and then hidden for
12 minutes.Resolve-CMSetupLogStatusdid not recognise CM 2509's own
terminal banner,Failed Configuration Manager Server Setup-- the word
order is reversed from theConfiguration Manager Setup failedphrase it
did match, withServerinserted. Setup's failure therefore scored as
InProgress, the engine logged the benign "normal 2509 async handoff"
message, waited out the fullWait-CMReadytimeout, and threw
SMS_EXECUTIVE / CM provider did not come ready within 12m-- pointing at
the wrong phase entirely. The banner and
Setup failed to download prerequisite componentsare now matched, so
this class of failure surfaces immediately with the real log context.Success detection is deliberately unchanged: a healthy install logs
InProgressatsetup.exeexit and is recovered byWait-CMReady
(re-confirmed against a clean 2026-08-12 run), and a regression test now
pins that behaviour so the new patterns cannot flip it.