> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/password-protection/home/change-log.md).

# Change log

{% updates format="full" %}
{% update date="2026-07-04" tags="maintenance" %}

## v1.1.120

Bug fix release

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue where the Sync-PasswordsFromHibp cmdlet throws an error due to a missing dependency

### Downloads

* **Service** — [x64](https://packages.lithnet.io/win/password-protection/v1.1/x64/LithnetPasswordProtection-1.1.120.exe)
  {% endupdate %}

{% update date="2026-03-01" tags="maintenance" %}

## v1.1.62

Fixes Test-IsAdPasswordCompromised on 2025 DCs and improves HIBP sync performance

### Service

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue with the Test-IsAdPasswordCompromised cmdlet when running on 2025 domain controllers with 32k page size enabled
* Improves performance of the Sync-HashesFromHibp cmdlet and allows increased hash counts
  {% endupdate %}

{% update date="2024-12-13" tags="maintenance" %}

## v1.1.57

Fixes invalid access to memory location error when changing passwords via AD Users and Computers

### Service

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue where an "invalid access to memory location" error may occur when changing a password using the AD users and computers console
  {% endupdate %}

{% update date="2024-11-19" tags="feature" %}

## v1.1.55

Adds HTTP proxy support for HIBP sync

### Service

<i class="fa-sparkles">:sparkles:</i> **New**

* Adds support for specifying a HTTP proxy on the Sync-HashesFromHibp cmdlet with a new -ProxyAddress parameter
  {% endupdate %}

{% update date="2023-05-07" tags="maintenance" %}

## v1.1.53

Fixes NullReferenceException when changing store path via PowerShell

### Service

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue where a NullReferenceException occurs using the PowerShell module to change the store path
  {% endupdate %}

{% update date="2023-04-30" tags="maintenance" %}

## v1.1.51

Fixes unsigned PowerShell scripts in installer

### Service

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue where some of the PowerShell scripts in the installer were not signed
  {% endupdate %}

{% update date="2023-03-18" tags="feature" %}

## v1.1.48

Fixes unsigned installer scripts and adds new PowerShell cmdlets for HIBP sync, config, and policy management

### Service

<i class="fa-sparkles">:sparkles:</i> **New**

* Add several new cmdlets

<i class="fa-wrench">:wrench:</i> **Fixed**

* Fixes an issue where some of the PowerShell scripts in the installer were not signed
  {% 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://docs.lithnet.io/password-protection/home/change-log.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.