Forum Discussion
PowerShell DSC Pullserver stops working with SQL database
This appears to be a regression in the newer Microsoft.PowerShell.DesiredStateConfiguration.Service.dll. The Pull Server starts and the endpoint remains available, but no SQL connection is attempted. Database initialization does not occur, tables are not created or updated, and node registration fails.
Replacing only the updated DLL with the previous version immediately restores normal SQL connectivity and Pull Server operation. This strongly indicates that the issue is introduced by the newer DLL and occurs before the SQL connection stage.
The recommended next step is to open a Microsoft support case and include the Windows Server build, installed KB, both DLL versions, and relevant DSC, IIS, and Application logs. The older DLL can be used as a temporary workaround.
Thank you for the feedback.
We have performed additional testing and were able to narrow the issue down further.
The problem occurs with Microsoft.PowerShell.DesiredStateConfiguration.Service.dll version 10.0.26100.5074, which was installed by KB5087051 on Windows Server 2025.
In comparison, the same DSC Pull Server configuration works correctly with Microsoft.PowerShell.DesiredStateConfiguration.Service.dll version 10.0.26100.1 from KB5044030.
When using the newer DLL version, the Pull Server service starts successfully and the endpoint remains accessible, however DSC client registration fails and no SQL database activity is observed. The only error returned during registration is:
Error registering the DSC agent with Agent ID a3ed4889-f77f-11f0-a0f1-00155d646b1c. The underlying error is: "The registration of the DSC Agent with Agent ID = a3ed4889-f77f-11f0-a0f1-00155d646b1c failed. The underlying error is 'UnexpectedError'."
No additional errors are logged in the DSC logs, IIS logs, or Windows Application logs.
As a validation step, we replaced only Microsoft.PowerShell.DesiredStateConfiguration.Service.dll version 10.0.26100.5074 with the previous version 10.0.26100.1 while keeping the rest of the environment unchanged. After doing so, SQL connectivity was immediately restored and DSC client registration succeeded.
We have reproduced this behavior in multiple environments. Based on these results, this appears to be a regression introduced between KB5044030 and KB5087051 affecting SQL-backed DSC Pull Server deployments.
Has anyone else observed similar behavior, or is Microsoft already tracking this as a known issue?