> 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/release-notes.md).

# Release notes

{% updates format="full" %}
{% update date="2026-07-16" %}

## DeployR 1.3.2629.2187

* Fixed an issue that caused driver packs with no tags to be ignored (#20129).
* Fixed an issue that could result in local computer PowerShell write access being denied (#20128).
* Added a new "Boot" option to the New-DeployRMedia PowerShell cmdlet to create a bootable USB key with no other content (#20136).
* Fixed an issue that could cause log files to initially be written to the C: drive before the drive was formatted (#20141).
* Updated DeployR Community to include StifleR 3.1.2629.647, which includes the following improvement:
  * Modified the task sequence editor UI to prevent accidental task sequence deletions (#20137).
* StifleR and StifleR Dashboard 3.1.2629.647 are recommended for DeployR Enterprise.
* Update DeployR boot images and media after upgrading to this build.
  {% endupdate %}

{% update date="2026-07-03" %}

## DeployR 1.3.2627.2141

* Fixed a compatibility issue with Windows Server 2022 that could cause issues extracting WIM files using PowerShell due to a missing -Index parameter (#20069).
* Added logic to write the DISM output from driver injection steps into the DeployR logs folder so that it is captured by the log upload process (#20080).
* Fixed an issue that caused the wrong content purpose (e.g. application instead of driver pack) to be assigned when creating content items via PowerShell (#20047).
* Added logic to ensure that a bad driver in an OEM driver pack does not cause the task sequence to fail. Instead, a warning will be logged and a copy of the setupapi.offline.log will be copied to the DeployR logs folder so that it gets uploaded for troubleshooting (#20082).
  * Note that this has been observed with the Dell QxS1250 driver pack; the included NVidia video driver does not properly specify the location of required files referenced in the .INF file.
* Improved driver pack selection logic to use product IDs (e.g. the four-character IDs used by Dell and Lenovo). When injecting OEM driver packs via "Install drivers from cloud" the product IDs are automatically matched; when injecting driver packs using content items and "Install drivers" the product IDs can be specified as tags (#20090).
* Fixed an issue that caused the Dell driver pack version to be specified twice in the content item name when importing an OEM driver pack (#20046).
* Adjusted the DeployR UI in Windows PE to automatically set the focus to the first text field on various wizard panes (#20077).
* Added the ability to specify full disk encryption (instead of used space only) in the "Enable BitLocker" step (#20089).
* Fixed an issue that resulted in a null SystemAlias value for QEMU VMs; this will now always be set to "QEMU" (#20092).
* Added the "WinPE-Dot3Svc" package to Windows PE by default for convenience when using 802.1x authentication (#20095).
* Fixed an issue that caused content items to not be filtered correctly when selecting items in the task sequence editor. This requires StifleR 3.1.2627.641 (#20062).
* Added support for new Postinit.ps1 and Postauth.ps1 scripts when initializating Windows PE. The existing Preinit.ps1 is called before networking has been initialized; Postinit.ps1 is called after networking has been initialized but before authentication has been performed; Postauth.ps1 is called after authentication is complete (#20096).
* Fixed an issue that could result in an SSL error when attepting to communication with the DeployR server after a period of time (e.g. requesting a driver pack after applying an OS) (#20098).
* Updated the DeployR Community certificate generation and renewal logic to only generate a certificate when needed. This uses the TwoPint.DeployRCommunity.Configure.exe program, which can be used to renew 2Pint-issued certificates that are close to expiration. These certificates have a 90-day lifespan (#20071).
* Updated the DeployR Community installer to include StifleR 3.1.2627.641; upgrading to DeployR Community 1.3.2627.2141 will upgrade StifleR automatically.
  {% endupdate %}

{% 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.
* After installing an updated StifleR Dashboard, press Control-F5 to refresh the web page to ensure it is using the latest version and not a locally-cached copy.
* When upgrading from DeployR 1.1, make sure you select "ServerInstanceAndDb" in the DeployR configuration editor.\
  ![](/files/olJIoYTENcO0TT9FI4ez)
* 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.
* Be sure to check out the [release notes for DeployR 1.2](https://documentation.2pintsoftware.com/deployr/1.2/release-notes) if you have not already reviewed them.
  {% 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, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/deployr/release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
