Problem Description:
Some users running Pharos Cloud Print Scout on Windows 11 have reported the following symptoms after applying the recent Microsoft Windows update KB5066835.
- The Print Scout system tray icon repeatedly displays a “Re-configuring” toast notification, and/or
- Print Scout status remains stuck in “Service isn’t ready”, preventing normal operation.
Note: Uninstalling KB5066835 has been shown to restore expected Print Scout functionality in affected environments.
Impacted Products:
Pharos Cloud Print Scout.
Windows 24H2 and greater Operating Systems.
Log Analysis Result:
In the Print Scout Log folder ".\Logs\printscout-ui\[user@computername].log you may see the below errors.
Error: connect ECONNREFUSED 127.0.0.1:8182
[info] failed to connect service, start timer to connect service again in 1000 ms at C:\Program Files (x86)\HP\PrintScout\printscout-ui\resources\app.asar\lib\app-shared-object\app-shared-object.js:37:11
[verbose] Request error: GET http://127.0.0.1:8182/SecurePrintService/LocalServiceState Error: connect ECONNREFUSED 127.0.0.1:8182
[info] failed to connect service, start timer to connect service again in 1000 ms at C:\Program Files (x86)\HP\PrintScout\printscout-ui\resources\app.asar\lib\app-shared-object\app-shared-object.js:37:11
[verbose] Request error: GET http://127.0.0.1:8182/SecurePrintService/LocalServiceState Error: connect ECONNREFUSED 127.0.0.1:8182
Side Note: The Print Scout uses HTTP://127.0.0.1:8182 for connections to itself on TCP 8182 and the are seen to fail with the WINSOCK Error ECONNREFUSED (10061). This HTTP request is done utilizing the Microsoft HTTP.sys core DLL for the Operating System.
*This is the reference to MS Windows WINSOCK Errors: https://learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2WINSOCK
Current Findings:
- Pharos has identified that uninstalling KB5066835 restores the Print Scouts functionality.
- Our internal validation using a clean installation of Windows 11 Pro 24H2 with update KB5066835 did not reproduce the issue, which may indicate:
- The problem is specific to KB5066835.
- It may occur more frequently on upgraded systems rather than clean installations.
*Community reports also suggest that similar Windows updates have affected local service communication (e.g., localhost/HTTP2 issues).
Known Issue:
This is a Microsoft Forum post around this problem:
https://learn.microsoft.com/en-us/answers/questions/5585563/localhost-not-working-anymore-after-2025-10-cumula?page=5
Resolution Steps:
These are the steps that have been provided by Microsoft to rectify this challenge.
https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#3592msgdesc
If you have further questions about this KB Article please contact Pharos Support and include:
- Windows version and update history
- Whether the system was clean-installed or upgraded
- Number of affected machines