BITOSDT 2.0 END-USER DOCUMENTATION SNAPSHOT (FEBRUARY 26, 2026)

Deployment Transparency Guide

This page documents what BitOSDT requires, where it stores files, what runs during deployment, and where to find troubleshooting data.

Open Interactive Demo Download Beta 2.0

1) Prerequisites

Windows host with local administrator rights for build/deployment actions.
Windows ADK + WinPE optional components installed (BitOSDT checks for required WinPE packages).
Storage for downloaded OS media and workspace artifacts.
Network connectivity only if you choose cloud source, catalogs sync, or package managers.

2) Where BitOSDT Stores Files Locally

BitOSDT uses a user-profile app directory model for app state, plus deployment/runtime paths used during imaging and WinPE sessions.

Path	Purpose
`%USERPROFILE%\.bitosdt\config.json`	App settings and path preferences.
`%USERPROFILE%\.bitosdt\bitosdt.db`	Local metadata database (catalog and image records).
`%USERPROFILE%\.bitosdt\downloads\`	Download cache for source files/catalog content.
`%USERPROFILE%\.bitosdt\workspace\`	Workspace for mounted images, temporary build artifacts, and output preparation.
`C:\BitOSDT\Installers`	Runtime location for embedded Full ISO custom installer payloads.
`C:\BitOSDT\Tasks`	Task sequence scripts directory in generated task settings model.
`C:\BitOSDT\Logs`	Task/app/update logging destination inside deployed Windows.
`X:\BitOSDT\Scripts\|Config\|Logs\|State`	WinPE runtime scripts, deployment config, status, and logs.

3) Exactly What Runs During Deployment (Execution Order)

Phase	Execution Order
WinPE start (Full ISO)	`startnet.cmd` -> shell launcher -> `Deploy-FullIso.ps1` -> disk prep -> DISM apply -> BCDBoot -> reboot.
First boot in Windows	`SetupComplete.cmd` runs and calls `task-runner.ps1`.
Task execution	Enabled tasks execute in order (apps, updates, custom scripts) with per-task continue-on-error behavior.
Deferred actions	If applicable, deferred scripts register RunOnce entries and execute at first admin logon.

4) Optional / Conditional Actions Matrix

Action	Runs By Default?	Condition
Winget installs	No	Only when winget packages are selected.
Chocolatey installs	No	Only when chocolatey packages are selected.
Custom installers	No	Only when custom installers are selected (payload execution applies to Full ISO).
Deferred network installers	No	Only when network-directory installers are configured.
RunOnce: `BitOSDTWingetInstallers`	No	Only when winget deferral is needed (e.g., LocalSystem context).
RunOnce: `BitOSDTNetworkInstallers`	No	Only when deferred network installers are configured.
Autopilot profile file	No	Only when Autopilot is enabled in wizard.
Windows Update task	Not always	Only when update categories are enabled.

5) Logs and Troubleshooting Paths

Path	What It Captures
`C:\BitOSDT\Logs\setup-complete.log`	SetupComplete execution log in deployed Windows.
`C:\BitOSDT\Logs\task-runner.log`	Main post-install task sequence log.
`C:\BitOSDT\Logs\app-install.log`	Primary application install task log.
`C:\BitOSDT\Logs\app-install-winget-deferred.log`	Deferred winget install log (RunOnce path).
`C:\BitOSDT\Logs\app-install-network.log`	Deferred network-directory installer log.
`C:\BitOSDT\Logs\windows-update.log`	Windows update task output.
`X:\BitOSDT\Logs\startnet.log`	WinPE startnet launcher trace.
`X:\BitOSDT\Logs\deploy.log`	WinPE deployment/bootstrap runtime log.
`X:\BitOSDT\State\deploy-status.json`	WinPE progress/state payload.

6) "No Bloatware" Transparency Statement

BitOSDT does not silently install random software by default. Package installs and custom installer actions are driven by explicit wizard selections.

No hidden app list is preloaded into deployment by default.
Optional actions are conditional and documented above.
Generated scripts and logs are available for inspection.

Implementation note: task settings model references C:\BitOSDT\Tasks, while SetupComplete currently executes generated scripts from Windows\Setup\Scripts in deployed images.