> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/reference/supported-versions.md). # Supported versions ## Application and boot media updates Updating Foundry OSD does not rewrite media already distributed. [Bootstrap](/reference/bootstrap.md#cache-and-connectivity) can obtain newer release runtimes during startup, so existing media may run a newer Deploy application without being rebuilt. Check the running application version; an older or debug-provisioned runtime does not gain release support from a catalog update alone. Recreate ISO media or [update an existing USB drive](/foundry-osd/media/update-usb.md) when you need to refresh embedded Bootstrap, configuration, or bundled assets. Test runtime and media updates before production use. ## Administrator workstation * Windows 10 or Windows 11. * Windows ADK `10.1.26100.9457`. * Windows PE Add-on `10.1.26100.9457`. {% hint style="warning" %} Do not substitute another ADK or Windows PE Add-on version. Use `10.1.26100.9457` for both components. {% endhint %} ## Windows deployment media Available Windows releases, languages, editions, architectures, and license channels depend on the current [operating-system catalog](/reference/catalog.md), the running Deploy version, and any restrictions configured during media authoring. The catalog can update independently of the application. {% hint style="info" %} **Supported Windows releases** Foundry supports Windows 11 24H2, 25H2, and 26H2 for catalog deployments, with 26H2 as the default. Microsoft's servicing dates differ by edition, as listed in [Windows 11 release information](https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information). Existing media needs a Deploy runtime that supports 26H2 to select it. When an older profile allows only releases that are no longer available, Deploy automatically falls back to supported catalog releases for the deployment architecture. If any allowed release remains available, that restriction stays in effect. See [Select Windows](/foundry-deploy/operating-system.md). {% endhint %} ## Hardware Network, storage, and platform support depends on Windows PE compatibility and available driver packages. Validate deployment media on representative hardware before production use. ## Custom WIMs The [custom image workflow](/foundry-osd/customization/custom-windows-images.md) accepts readable WIM metadata without a Windows version, edition, or architecture allowlist. This is not a support guarantee for every image. Deployment tools, firmware, drivers, and selected customizations still have their own requirements. ## PostInstall runtime compatibility [Post-installation](/foundry-osd/customization/post-installation.md) supports x64 and ARM64 targets. Bootstrap prepares PostInstall for the boot media architecture; you do not need to install .NET on the target. Use boot media matching the target Windows architecture. Deploy checks runtime compatibility before preparing the disk. Keep deployment media and its package content together, and choose scripts and installers compatible with the target Windows image and architecture. Test the complete workflow on representative hardware before rollout. ## Domain Join [Domain Join](/foundry-osd/domain-join.md) is available on x64 and ARM64 for Windows editions that can join a domain. Use media that matches the architecture of the computer, and test the complete workflow before a rollout. Pro, Education and Enterprise editions, including their N variants, can join a domain. Home editions (`Core`, `CoreN`, `CoreSingleLanguage`, `CoreCountrySpecific`) cannot: Foundry skips the join with a warning and the installation continues. For an edition Foundry does not recognize, the decision is made from the applied image. Installed Windows must reach the domain's DNS and a writable domain controller, and the join account must be allowed to join computers, reuse existing computer accounts and place computers in the listed OUs. Custom answer files and custom images must meet the [Domain Join requirements](/troubleshooting/domain-join.md#media-is-not-ready-or-input-is-rejected). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.foundryosd.com/reference/supported-versions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.