> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-roi-tool/release-notes.md).

# Release notes for the Patch My PC Return on Investment Tool

*Applies to: Patch My PC Return on Investment Tool*

## 1.9.0 - 2025-04-28

* Pressing Ctrl+D will now enable debug mode and output a log at your %TEMP% directory.
* Fixed an issue where a single null entry in SMS\_G\_System\_INSTALLED\_SOFTWARE class prevented fallback to the add/remove program classes during ConfigMgr Scan.
* Updated dependencies.

## 1.8.0 - 2025-02-19

* Improved device count query
* Updated dependencies

## 1.7.0 - 2025-01-02

* Change to quote calculation
* Updated dependencies

## 1.6.0 - 2024-11-12

* Now displays environment device count
* Small clarification on scan results
* Updated dependencies

## 1.5.0 - 2024-10-18

* Export now supports csv
* Duplicates removed from scan results
* Updated dependencies

## 1.4.0 - 2024-06-11

* Now targeting .NET 4.6.2 for better compatibility
* Updated dependencies

## 1.3.0 - 2024-05-13

* UI stays responsive while scanning
* Minor bug fix where manual stats wont update after a failed ConfigMgr Scan
* Window is now resizable
* More data in the PDF report

## 1.2.1 - 2024-04-08

* Fixed breaking change to device count Graph API query

## 1.2.0 - 2024-02-26

* PDF export option added

## 1.1.0 - 2024-01-29

* Fixed Intune device count bug
* Added tool-tips

## 1.0.4 - 2023-12-06

* Improved Intune scan reliability

## 1.0.3 - 2023-11-28

* Bug fix for null ARP DisplayName Entries.

## 1.0.2 - 2023-11-24

* Bug fix for handling null data returned in Intune scan.

## 1.0.1 - 2023-11-13

* Initial release


---

# 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.patchmypc.com/patch-my-pc-roi-tool/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.