Add release note for PA-3175

https://tickets.puppetlabs.com/browse/PA-3175

Author: clairecadman

source/puppet/5.5/release_notes.markdown

@@ -34,12 +34,13 @@ Released  30 April 2020
 - In macOS 10.15, the `-noidme` flag caused `.dmg` package installation to fail. This release removes the `-noidme` flag with `hdiutil` when using the `pkgdmg` package provider. [PUP-10408](https://tickets.puppetlabs.com/browse/PUP-10408)
 - This release upgrades Ruby to 2.4.10 to address security issues: [CVE-2020-10663](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10663). [PA-3179](https://tickets.puppetlabs.com/browse/PA-3179)
 - An issue where RedHat Subscription Manager updates caused `ensure => latest` to do nothing is now fixed. [PUP-10432](https://tickets.puppetlabs.com/browse/PUP-10432)
-- The `pkgng` provider now supports `install_options`. [PUP-10380](https://tickets.puppetlabs.com/browse/PUP-10380).
+- The `pkgng` provider now supports `install_options`. [PUP-10380](https://tickets.puppetlabs.com/browse/PUP-10380)
 - The `pkgng` provider now correctly parses the latest versions for packages. [PUP-10382](https://tickets.puppetlabs.com/browse/PUP-10382)
 - Previously, 5.5.17 agents were failing on interval runs. There were various paths in a Puppet run that did not explicitly return exit code, leading to a `TypeError` exception. With this release, the `exit` argument from `run_in_fork` is unaffected by these errors. [PUP-10366](https://tickets.puppetlabs.com/browse/PUP-10366).
-- Previously, if an Active Directory user was added as member of a local group and then deleted, Puppet did not manage the respective group members. With this release, Puppet will manage the group by showing SID instead of the account name for non-resolvable users. [PUP-10303](https://tickets.puppetlabs.com/browse/PUP-10303).
-- Previously, Windows pidlock could raise access denied. With this release, you can use `SeDebugPrivilege` on Windows when opening a lockfile PID to determine whether the process is a Puppet process. [PUP-10248](https://tickets.puppetlabs.com/browse/PUP-10248).
-- This version upgrades the OpenSSL version to 1.1.1g on non-fips platforms to address security issues: [CVE-2020-1967](https://www.openssl.org/news/secadv/20200421.txt). [PA-3186](https://tickets.puppetlabs.com/browse/PA-3186).
+- Previously, if an Active Directory user was added as member of a local group and then deleted, Puppet did not manage the respective group members. With this release, Puppet will manage the group by showing SID instead of the account name for non-resolvable users. [PUP-10303](https://tickets.puppetlabs.com/browse/PUP-10303)
+- Previously, Windows pidlock could raise access denied. With this release, you can use `SeDebugPrivilege` on Windows when opening a lockfile PID to determine whether the process is a Puppet process. [PUP-10248](https://tickets.puppetlabs.com/browse/PUP-10248)
+- This version upgrades the OpenSSL version to 1.1.1g on non-fips platforms to address security issues: [CVE-2020-1967](https://www.openssl.org/news/secadv/20200421.txt). [PA-3186](https://tickets.puppetlabs.com/browse/PA-3186)
+- Previously, Windows components (such as DHCP Client) restarted after Puppet agent upgrades. This was a result of nssm.exe being registered as the EventMessageFile, which got loaded and locked into svchost.exe when viewing events raised by pxp-agent. The agent upgrade tried to replace nssm.exe, but failed as it was loaded, and the only way to unload it was to restart. This fix removes the usage of nssm.exe for events and replaces it with EventCreate.exe when generating event messages, so now the EventCreate.exe will get loaded and locked by svchost.exe when viewing Puppet events. This will no longer interfere with the agent upgrade. [PA-3175](https://tickets.puppetlabs.com/browse/PA-3175)
 
 ## Puppet 5.5.19