• Resolve #56
• Resolve issue where Server Security Updates are not published in the atom update feed and thus these may be returned as the latest release due to having a date of "N/A". The issue has been worked around by hardcoding any unknown updates with a date of '0000-00-00'. Microsoft need to publish these in the atom update feed to fully resolve the issue.

If you have found this project useful please Sponsor to help fund the renewal of the code signing certificate.

• New code signing certificate.
• Support for Windows Server 2025 hotpatch. Atom feed issue resolved #51.
• Resolve issues reported in #53 - April Update Preview Incorrectly Categorized.
• Resolve issues where duplicate updates for the same version were returned on Windows 11 24H2. See discussion on #53.
• Support for security updates published for Hotpatch capable OS.
• Resolve issue where KB source article for KB5063673 was being returned due to Microsoft typo in atom feed. Code has been improved to workaround this and future mistakes where release information is obtained from Microsoft release note webpages.

• The code signing certificate is due to expire next month (2025-04-11). If you have found this project useful please ❤️Sponsor to help fund the renewal of the code signing certificate.
• Resolve issue where Server 2022 hotpatch was not returning the correct build number due to typo in the webpage, function which parses the raw HTML will account for missing ")" in the data so it works now and in the future.
• Resolve issue where Server 2022 was not returning catalog URL.
• Resolve issue where Hotpatch baselines were not being returned due to name change to from "Hotpatch basline" to "Baseline".
• Updated 'Convert-ParsedArray' function and introduced new function 'Get-ReleaseNotes' to resolve issue supporting new hotpatch operating systems as the source webpage now has multiple OS. It will now filter correctly based upon defined OS. #49
• Public Preview updates included for Server 2022 hotpatch.
• Support for Windows 11 Hotpatch.
• Support for Windows Server 2025.
• Support for Windows Server 2025 hotpatch is not possible due to Microsoft not having a Atom feed available #51. A further release will follow when they publish this, but the code to support it is done.
• Update HtmlAgilityPack library to 1.12.0.0.
• Update CI tests to make tests more robust and include Support for Windows Server 2025 and Windows 11 Hotpatch.

• BREAKING CHANGE - Update Get-LatestOSBuild function. Hotpatch on Windows Server 2022 Azure Edition 'Server2022Hotpatch' must manually be specified in the 'OSName' parameter otherwise it will default to non-hotpatch. This is because the official detection method (presence of an installed KB) is not sufficient to determine if hotpatches are actually being applied.
• Update Get-CurrentOSBuild function to correctly handle Hotpatch on Windows Server 2022 Azure Edition by checking if latest installed update is from hotpatch version or not. This is because updates from the traditional version can still be installed.
• Resolves issue with Windows 11 versions not returning correct results due to newly released Windows 11 24H2 which is now fully supported.
• Improved CI Tests to be more robust including new test for Windows 11 24H2.

• Resolve issue where hotpatch on Windows Server 2022 Azure edition may trigger Akamai CDN DoS protection due to the method of obtaining hotpatch baseline information, this is now obtained from the Windows Server 2022 atom feed. Additionally, this has significantly decreased execution time.
• Updated to remove workaround code for hotpatch on Windows Server 2022 Azure edition where OS builds were incorrectly listed as 20346.x instead of 20348.x because it has now been corrected by Microsoft.
• Updated to also include source KB article for baseline updates on hotpatch on Windows Server 2022 Azure edition. These are presented as ' KBXXXXXXX / KBXXXXXXX'
• Updated to include catalog URL for baseline updates on hotpatch on Windows Server 2022 Azure edition.
• Updated CI tests to restore testing of all releases for hotpatch on Windows Server 2022 Azure edition. This is due to the new method of obtaining hotpatch baseline information and removing sleep between tests as code changes have now mitigated triggering Akamai CDN DoS protection.
• Updated to use latest release of HTML Agility Pack v.1.11.65.0

• Removed UserAgent spoofing as this was causing problems from some destinations such as from Microsoft Azure and not convinced the it made a difference preventing Akamai CDN DoS protection.

• Resolve issue where 'Get-ChromeUserAgent' function was not working.
• Updated CI tests to prevent issue where Server 2022 hotpatch testing was triggering appveyor frequent failure due to triggering Akamai CDN DoS protection when running extensive testing. Test for Server 2022 has been reduced to check the last patch only.

• Alleviate issue where Akamai CDN DoS protection has recently starting triggering frequently preventing the module from working. Changed to an efficient method of obtaining preview and out-of-band status of updates via a single web request. A Google Chrome user agent is now presented for all web requests which may also help prevent temporary blocks.
• Expanded Akamai CDN DoS protection detection for all web requests.
• Module now correctly throws a descriptive error when Akamai CDN DoS protection is triggered.
• Resolve issue where servicing option may return 'â¢' instead of '•' in Windows Terminal - #39
• Updated to use latest release of HTML Agility Pack v.1.11.61.0
• Updated CI tests to help prevent Akamai CDN DoS protection triggering when testing.
• Updated CI tests for #39

• Project is now code signed. Thanks to @jmuellerffn for your support #36 . Please consider supporting this project by sponsoring to help fund next year's certificate.
• Updated CI tests for code signing.

• Updated to use latest release of HTML Agility Pack v1.11.59.0.
• Updated functions to support hotpatch on Windows Server 2022 Azure edition - #35. This introduces a new property called 'Hotpatch'. True means the update is a Hotpatch while false means it is a baseline update.
• Updated help in functions.
• Updated CI tests.