OSDStage v1.0.0-rc3

OSDStage v1.0.0-rc3

• Third public release candidate, not GA. Includes Windows Update staging and the documentation/catalog improvements merged since RC2. The JSON/HTML delivery report is planned separately and is not included.
• Add Add-OSDStageWindowsUpdate: one final native Windows Update scan/install pass after all apps and configuration. Eligible quality classifications cover applicable Windows, .NET, Defender and MSRT servicing; feature upgrades and recognized previews are excluded. Earlier failed/skipped packages suppress the pass.
• Drivers remain disabled by default. -IncludeDrivers opts in to all WUA driver classes, including firmware and optional offers; -DriverClass narrows selection to the specified classes. Download all selected payloads before quiet installation. No update-source/policy changes or OSDCloud USB caching; Windows Update uses its configured infrastructure and may reuse its own cache.
• Continue while a later restart is pending, stopping only when WUA requires a restart before the next installation. Report per-update outcomes and aggregate restart requirements; never request a reboot, schedule a retry or resume after OOBE. Success applies to this scan, not all possible future updates.
• Fresh x64 SetupComplete acceptance on PC1, 3 November 2026: 3/3 packages succeeded (7-Zip, file configuration, Windows Update), with 36/36 updates installed in 265.3 seconds. Independent deployment/order/marker checks passed; Windows Update ran last, returned success with restart required (3010), requested no restart and left the Windows release unchanged. Normal OOBE completed to a regular-account desktop.
• Seven further offers were installed through Windows Settings, followed by a normal restart and a green scan. Two same-version Intel titles did not recur; their initial re-offer cause is unproven. A newer Security platform and additional audio components were among the follow-up offers. BIOS 1.19.3 was already current from the previous test, so it is not fresh firmware-flash evidence for this run.
• Earlier manual OOBE acceptance installed 29/29 driver offers, verified active firmware/network/audio/video versions after restart, and completed a later 10/10 component pass. Monthly cumulative Windows/.NET updates, Autopilot enrollment, cancellation and additional hardware remain separate field coverage; ARM64 has not been physically validated.
• Improve catalog terminology and configuration icons, homepage examples and deployment flow. Website publication is separate from module publication.
• Install with Install-Module OSDStage -Repository PSGallery -RequiredVersion '1.0.0-rc3' -AllowPrerelease -Force. RC versions share the numeric module folder 1.0.0; use a fresh PowerShell session and verify the loaded prerelease label.

OSDStage v1.0.0-rc2

OSDStage v1.0.0-rc2

• Second public release candidate. Not a GA release. Includes the tested changes merged after RC1; no repository schema, cache-path or command-name migration is required from RC1.

• Acquire and refresh Company Portal and CMTrace Open automatically during PreInstall, with optional OSDCloud USB caching and validated offline fallback. WinPE can stage both without prepared cache; fully offline preflight still requires verified content.

• Use Deploy-OSDCloud-style timestamped [INFO]/[WARN]/[ERROR] lines and terminal-aware colors, with no extra blank lines between results, across cmdlet result types without replacing PowerShell objects or changing JSON properties. Preserve explicit detail/table views, diagnostics and failure details; distinguish staging, cache reuse, validation, authoring and cleanup. Configuration updates use a suppressible information message when -PassThru is omitted.

• Add Add-OSDStageDirectory and Add-OSDStageFile for ordered, one-shot SetupComplete file operations. Support literal paths, directory creation/removal, text or source-file content, explicit -Force replacement and separate -Recurse removal. Include integrity-checked offline staging, per-operation results, help and a disposable test example. Physical acceptance passed on 1 November 2026: nine operations succeeded and all five independent content/removal checks passed. The published RC1 does not contain these commands.

• Physical x64 acceptance: Company Portal and CMTrace Open both completed fresh online acquisition and installation, then reused validated cached content on the next deployment; both apps were confirmed working. File-system acceptance completed nine operations with five independent content/removal checks. Compact output was verified with preserved result properties and explicit detailed views.

• Refresh the GitHub Pages homepage, task guides, source register and release-availability documentation. Website content is deployed separately from the module.

• Windows Update staging and optional Windows Update drivers remain in experimental PR #111 and are not included. ARM64 physical validation is still outstanding.

• Upgrade from RC1 with an explicit prerelease install: Install-Module OSDStage -Repository PSGallery -RequiredVersion '1.0.0-rc2' -AllowPrerelease -Force. RC1 and RC2 use the same numeric PowerShell module folder (1.0.0); close existing PowerShell sessions and verify the loaded prerelease label before testing.

OSDStage v1.0.0-rc1

OSDStage v1.0.0-rc1

• First public OSDStage release candidate for the PowerShell Gallery installation and WinPE deployment test. Not a GA release.
• Include built-in apps, schema 2 repository packages (App, Script, Font, Certificate and Driver), registry settings, machine variables, services, Wi-Fi, initial associations, Start/taskbar pins, optional features, capabilities and explicit inbox app cleanup.
• Support prerelease identity consistently across manifest, immutable Git tag, GitHub prerelease and exact Gallery download verification. Preserve numeric PowerShell module folders and compare downloaded release files by SHA-256.
• Document the online Gallery route with -AllowPrerelease; the USB content cache remains optional and automatically detected.
• Existing physical x64 deployment evidence is retained in the validation documentation. The published Gallery-to-WinPE route is the remaining RC acceptance test; ARM64 has not been physically validated.

OSDApps v0.51.0

OSDApps v0.51.0

• Add the opt-in Microsoft Company Portal built-in. Sync-OSDAppMicrosoftCompanyPortal now downloads the official Microsoft Preinstall Kit automatically on full Windows, while -KitPath remains available for a manual/offline source. Stage the architecture-matched bundle, offline license and dependencies in WinPE; provision Company Portal for future user profiles during SetupComplete.
• Add the opt-in CMTrace Open built-in. Synchronize the latest stable upstream x64 or ARM64 MSI, validate the official GitHub release SHA-256 and Authenticode signature on full Windows, preserve the vendor MSI filename, and verify integrity again before silent MSI installation during SetupComplete. Support previously synchronized legacy Package.msi caches without another download.
• Keep both built-ins independent of custom Azure repository packages and compatible with the existing OSDApps application queue and Windows Inbox Cleanup script.
• Physical x64 validation (PC1): Windows Inbox Cleanup removed the three selected packages under SYSTEM; Company Portal 11.2.1495.0 provisioned and was available to the signed-in Autopilot user; CMTrace Open 1.6.3 and the separate DisplayLink repository package installed. Result: four succeeded, zero failed or skipped.
• Separate full-Windows preparation test confirmed the automatic Microsoft Company Portal download without -KitPath: Updated=True, CacheReused=False, seven selected cached files, official Microsoft Download Center source. ARM64 is supported in the interface but was not physically validated.

OSDApps v0.50.0

OSDApps v0.50.0

• Add opt-in Add-OSDAppWindowsInboxCleanup built-in Script with explicit package selection or the Tested13 preset, integrity-checked offline staging, SYSTEM execution during SetupComplete, early diagnostics and per-package result reporting. No Azure catalog or vendor download is needed.
• Skip bundled scripts in the PreInstall acquisition phase without changing the ordered SetupComplete queue. Include preflight hash verification, read-only Viewer metadata and regression tests. Keep the separate WindowsInboxAppCleanup repository package compatible and unchanged.
• Fix the startup failure when powershell.exe -File evaluated a $PSScriptRoot-dependent parameter default before entering the script body. Resolve config.json only after parameter binding; add regression coverage.
• Validate on a physical Windows deployment: the built-in ran as NT AUTHORITY\SYSTEM, removed all 13 selected packages with zero failures and exit code 0. The operator confirmed they remained absent after completing Autopilot. See validation evidence.

OSDApps v0.49.1

OSDApps v0.49.1

• Persist automatic VisualCppRedist/SevenZip predecessor cleanup outcomes in the existing client and PreInstall logs, including preservation reasons and failures. Keep cleanup guards, cache reuse and synchronization result objects unchanged; logging failures do not change cleanup decisions.

• Add Diagnostics mode to the standalone maintenance tool: export deployment results, runtime log rotations and bounded installer-log candidates to a local ZIP with a source inventory, hashes and collection warnings. No new module cmdlet or runtime behavior change.

• Clarify the scope of local cache integrity, publisher checks, Office configuration compatibility and vendor freshness in the maintenance guide, FAQ and Viewer documentation.

OSDApps v0.49.0

OSDApps v0.49.0

• Automatically remove known retired VisualCppRedist and SevenZip cache variants after validating their canonical replacements. Preserve other architectures, links and recovery content.

• Add explicit Clear-OSDAppCache -BuiltIn -Prune maintenance for unmanaged built-in root folders and loose files. Preserve managed variants, legacy payload filenames, registered aliases, filesystem links and recovery content. Support read-only preview, per-item confirmation and the existing exclusive cache writer lock.

• Preserve vendor installer filenames for built-in downloads, USB caches and Windows staging, including the Teams MSIX. Continue reading legacy generic-name caches without forced downloads. Keep the Package.zip contract for custom repository apps and scripts. Reject unsafe download filenames and ambiguous built-in payloads.

• Document Intune ESP detection for applications preinstalled by OSDApps, including compatible newer versions.

• Validate vendor filenames and legacy cache reuse on two physical deployments and USB caches, plus isolated automatic cleanup on Windows.

OSDApps v0.48.1

OSDApps v0.48.1

• Explain built-in cache reuse, acquisition, offline fallback and failures with a per-deployment CacheDecisionReason in PreInstall results, Runner results and acquisition logs. Preserve the existing cache policies and distinguish changed HTTP metadata from a confirmed new application version.

OSDApps v0.48.0

OSDApps v0.48.0

• Add Visual C++ v14 x86/x64 and .NET Runtime/Desktop built-ins with separate variant identities, Microsoft verification, transactional caches and installed-version checks. Runtime items are staged before applications.
• Require exactly one explicit architecture for all four runtime Add/Sync cmdlets. Offer only supported stable .NET channels, enforce offline support deadlines and reject known EOL channels without cached fallback. Network failures may still use verified cache content within the supported channel lifetime.
• Use VisualCRedist consistently for public commands, package IDs and cache folders. Earlier preview cache folders are not migrated or deleted automatically.
• Validate physical cold and warm deployments of Visual C++ x86/x64 and .NET 10 Runtime x86/Desktop x64, followed by a successful deployment using the final VisualCRedist names. All four installed versions and exit codes passed; staging was removed. See validation evidence.

OSDApps v0.47.0

OSDApps v0.47.0

• Add Visual Studio Code Stable system-installer staging and synchronization for x64 and ARM64, with official release SHA-256, Microsoft publisher verification and transactional cache replacement.

• Add 7Zip built-in staging and cache synchronization for x64, x86 and ARM64, with official release SHA-256 verification and transactional cache replacement.

• Record successful physical x64 7Zip and Visual Studio Code deployment tests, including installed versions and runtime cleanup. See validation evidence.

• Gate automatic release creation on a module version increase. Other manifest changes skip publication; manual release requests retain strict tag and source validation.