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

# Release Notes

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

Direct upgrades from previous iPXE Anywhere Web Service versions (3.x) to version 4.0 are not supported. You must uninstall the existing version before installing 4.0, or perform a fresh installation on a new server. See Upgrading to iPXE Anywhere Web Service 4.0.
{% endhint %}

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

2PXE Server 4.0 is not currently compatible with Microsoft Configuration Manager (ConfigMgr, formerly SCCM). The release of iPXE Anywhere Web Service 4.0 does not restore native Configuration Manager PXE integration. If your deployment relies on that integration, do not upgrade 2PXE Server to version 4.0.
{% endhint %}

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

## iPXE Anywhere WS 4.0.2645.212

Initial public release.

#### New features and functionality

* Rebuilt on .NET 10 (see prerequisites). Scripts run in PowerShell 7.6.
* Settings are stored in the registry and managed with the new **Configure iPXE WS** configuration editor, replacing the `iPXEAnywhere.Service.exe.config` file (see Configuring the iPXE Web Service). Settings can be exported to a `.2psimport` file for unattended installations.
* The installer no longer connects to SQL Server. The database connection is set in the configuration editor (by SQL Server instance and database name, or with a full connection string), and the service creates the database when it starts (see Permissions).
* HTTPS is turned on by default. The host certificate is issued through 2Pint Software Online Services using the license key, unless a thumbprint or subject name is specified, and renewed certificates are used without a service restart.
* Logging now uses Windows event logs (see Troubleshooting).
* Scripts run with an execution policy of Bypass, and can import PowerShell modules (see How the scripts run). The default scripts are installed in a **Templates** folder and copied to the **Scripts** folder when the service first starts, so your changes are not overwritten.
* New **Deploy with label** setting for the name shown in the boot menu.
* Integration with 2PXE no longer requires a StifleR server.

#### Improvements/Bug Fixes

* Database errors are now logged as errors instead of informational events.

#### Removed

* The `iPXEAnywhere.Service.exe.config` file, the file-based debug log, the bundled OpenSSL certificate authority, and customer-specific scripts.
* The unimplemented QR code and user name and password options in the default device authentication menu.
  {% endupdate %}
  {% endupdates %}

For upgrade, configuration and database setup guidance, see [Upgrading to iPXE Anywhere Web Service 4.0](/ipxe-ws/4.0/whats-new-and-upgrades/upgrading-to-ipxe-ws-4.0.md), [Configuring the iPXE Web Service](/ipxe-ws/4.0/configuration/configuring-the-ipxe-web-service.md), and [Permissions](/ipxe-ws/4.0/planning/permissions.md).


---

# 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/ipxe-ws/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.
