> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.3/release-notes.md). # Release notes {% updates format="full" %} {% update date="2026-06-23" %} ## DeployR 1.3.2626.2093 * This is the initial DeployR 1.3 release, for both DeployR Enterprise and DeployR Community. For DeployR Enterprise, StifleR 3.1 is required. (DeployR Community installs all dependencies automatically.) * Moved to .NET 10.0.9 and PowerShell 7.6.3. For existing DeployR Enterprise installations, these need to be installed manually before installing DeployR 1.3. * Updated DeployR Community to use StifleR 3.1.2626.580 and 2PXE 4.0.2626.404. * Added support for suspending a task sequence in the full OS when using AutoLogon. This can be used by adding the "Suspend task sequence" step. Resume the task sequence by executing the created desktop shortcut. (This is not supported when using any other continuation method.) * Added an "Unlock BitLocker" task sequence step that can be used to retrieve the BitLocker recovery password from either Active Directory or Entra ID to unlock the current OS drive. This is useful in repair situations where the OS is no longer functional and needs to be fixed when already encrypted. (Note that there are specific security delegation requirements to grant the DeployR server rights to retrieve recovery passwords.) * Added support for specifying a BitLocker TPM + PIN protector, as an alternative to the default TPM-only setup. * Added a new "Configure Linux for Entra ID" step that configures Ubuntu 26.04 to log in locally using Entra ID credentials (using the Entra device code flow as implemented by the Linux authd package). * Fixed an issue that could prevent the DeployR task sequence from completing or restarting when in the full OS if an application started a process that did not end; these processes will now be termined so that the task sequence engine shutdown can continue. * Added support for "Windows" or "Linux" tags so that task sequences will be download only in the appropriate boot images. * Added support for a "Hidden" tag that prevents a task sequence from appearing. It can still be used as a nested task sequence or selected through non-UI methods (e.g. Bootstrap.json). * Fixed a bug that caused the Log Viewer application to crash when trying to open a file in Windows PE. * Fixed a bug that caused the progress UI log viewing to not notice when the log file moved from X: to S: during the task sequence execution. * Fixed a bug that could cause an error when trying to duplicate a task sequence. * Fixed issues that could prevent the automatic backup of BitLocker recovery passwords when using the "Enable BitLocker" step. * Fixed a bug that could cause the "Register Autopilot" process to fail when using Autopilot v2 and trying to register the device from Windows PE. * Fixed an issue that could prevent Windows updates from installing when using WSUS due to an 80244010 error. * Fixed a variety of issues in the DeployR Community installer: * DeployR Community 1.2 could not be uninstalled. * PowerShell 7 was not detected correctly, causing it to be redownloaded and reinstalled even if already present. * .NET 10 components were not detected correctly, causing them to be redownloaded and reinstalled even if already present. * Fixed an issue that required the DeployRCommunity installer to be manually elevated; it will now elevate automatically when needed. * Fixed an issue that caused the /layout switch (to pre-download needed content) from working. * Fixed downgrade detection logic. * Ensure that you regenerate boot images and media after upgrading to DeployR 1.3 to get the latest .NET and PowerShell dependencies. {% endupdate %} {% endupdates %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.2pintsoftware.com/deployr/1.3/release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.