> 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/4.0/whats-new-and-upgrades/release-notes.md).

# Release Notes

{% hint style="danger" %}
**Configuration Manager compatibility**

2PXE Server 4.0 is not currently compatible with Microsoft Configuration Manager (ConfigMgr). If you use ConfigMgr, please remain on the previous version of 2PXE Server.
{% endhint %}

{% hint style="danger" %}
**Upgrade requirements**

Direct upgrades from previous 2PXE Server versions to version 4.0 are not supported. For upgrade and migration instructions, see [Upgrading to 2PXE Server 4.0](/2pxe-server/4.0/whats-new-and-upgrades/upgrading-to-2pxe-server-4.0.md).
{% endhint %}

{% updates format="full" %}
{% update date="2026-11-06" %}

## 2PXE 4.0.2645.631

Initial public release.

#### New features and functionality

* Rebuilt on .NET 10, with a new Windows Installer package. In-place upgrades from 2PXE Server 3.x are not supported; see [Upgrading to 2PXE Server 4.0](/2pxe-server/4.0/whats-new-and-upgrades/upgrading-to-2pxe-server-4.0.md).
* Settings are stored in the registry and managed with the new **Configure 2PXE** configuration editor, replacing the `2Pint.2PXE.Service.exe.config` file. Settings can be exported to a `.2psimport` file for unattended installations.
* New DeployR request handler for booting DeployR Windows PE and Linux boot images.
* Support for ARM64 UEFI devices, and for UEFI HTTP Boot on x64 and ARM64 devices.
* New **iPXE Bootloader binary to use** setting (Default, Native or USB), replacing the separate native driver and USB settings.
* New **Respond to PXE requests** setting, to install and configure 2PXE without it answering PXE requests yet.
* Licensing can come from a license key or from StifleR (see [Licensing](/2pxe-server/4.0/configuration/2pxe-config-file.md#licensing)).
* Certificates are now issued by the 2Pint Software CA through 2Pint Software Online Services (see Certificate Considerations). HTTPS certificates can also be selected by subject name, and renewed certificates are used without a service restart.
* Logging now uses Windows event logs, including a new audit log of PXE decisions (see Logs and events).
* New boot media tools: the iPXE Anywhere Boot Media Generator (BootGen) and iPXEIdentifier.
* Updated iPXE binaries and wimboot 2.9.

#### Removed

* The `2Pint.2PXE.Service.exe.config` file, the file-based debug log, the bundled OpenSSL certificate authority, and custom menu items (`CustomMenuItems`).
  {% 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/4.0/whats-new-and-upgrades/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.