> 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/2pxe-server/introduction/release-notes.md).

# Release Notes

{% updates format="full" %}
{% update date="2025-12-22" %}

## Release build version

2PXE server: 3.7.11206.1534

#### New features and functionality

* Allow the length of the host certificate to be controlled in config (19292)

#### Improvements/Bug Fixes

* Loading WinPE fails with error 0xc000000f on devices that has no secure boot revocation list present (19291)
* Networking setup takes long in WinPE and sometimes hangs when booted via iPXE (19069)
  {% endupdate %}

{% update date="2025-06-04" %}

## Release build version

2PXE Server: 3.7.10522.2204

#### New features and functionality <a href="#new-features-and-functionality" id="new-features-and-functionality"></a>

* Support for Configuration Manager 2503

#### Improvements/Bug Fixes <a href="#improvements-bug-fixes" id="improvements-bug-fixes"></a>

* Changed to import certificates after networking has been initialized
* Modified variable data download so that it writes the correct number of bytes from the last packet
* Added logic to check the file version of TSPXE.DLL (>5.9135)
* Added logic to send new PXEIP (DHCP-assigned client address) and CMVersion (form TSPXE.DLL) variables to the iPXE WS
* Logging tweaks
* Added logic to prevent 0x00 (binary zero) bytes in the variable password
* Added a new HTTP get handler for downloading folder/files (required POST before)
* Added logic to change the variable data encryption based on the provided CMVersion
* Modified logic that constructs the response packet options
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/2pxe-server/introduction/release-notes.md?ask=<question>&goal=<user_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.
