Hi,
Recently I'm not able anymore to make PMPC updates visible in WSUS. When I select updates and activate the command "Show in WSUS" through the PMPC publisher tool no errors are thrown, but still I'm not able to see the updates in the WSUS console. When I run an SQL query I can see the flag IsLocallyPublished is still 1 and hasn't been changed to 0, so it seems the PMPC publisher tool doesn't successfully change this, despite saying the operation has succeeded.
As far as I can see this has changed with publisher 2.1.53.0, 2.1.60.0 or 2.1.78.0. It did work before however.
Anyone else experiencing this? What's the solution? Is this a bug?
Thanks!
Regards,
Pedro
Hi Pedro,
Please open a support case for this by filling out the form here: https://patchmypc.com/technical-support/. One of our customer engineers will then get back to you to investigate this further. Thanks!
Hi
Did you get this to work so you see the updates in wsus?
I have the same issue
Do you have the applications as Full Content or Metadata?
@niclas2874 We haven't gotten confirmation yet, but in this case, the issue seemed to be caused by insufficient permissions. For more information, please visit:
Configuring Standalone WSUS Mode: SQL permissions required to publish update information to the database (https://patchmypc.com/kb/standalone-wsus-mode/#h-sql-permissions-required-to-publish-update-information-to-the-database)
Hi,
I can confirm Michiel's solution.
Earlier we had already executed the SQL query referred to, so it seems these permissions were removed somehow in our environments. Executing the query again has solved the issue: the manual way as well as the automatic way.
The permission removal was almost certainly caused by the installation of an OOB update for WSUS at the end of October 2025, i.e. OOB CU KB5070884 (23 oktober 2025 - KB5070884 (OS-build 20348.4297) Out-of-band - Microsoft Ondersteuning) from CVE CVE-2025-59287 (CVE-2025-59287 - Security Update Guide - Microsoft - Windows Server Update Service (WSUS) Remote Code Execution Vulnerability). This update contains WSUS changes and was recommended to install ASAP by our Microsoft TAM. It was installed in our test and production environment, introducing the "PMPC issue" in both environments around the same time.
@niclas2874 , in our case we download full content (so not metadata only) in WSUS, but this has nothing to do with the issue (at least not in our case).
Grtz,
Pedro
What is the best practice when to use fill content vs medatada?
@niclas2874 In most cases, we'd recommend publishing updates to WSUS with Full Content. For more information, please visit:
- Publishing with Full-content or Metadata Only (https://patchmypc.com/kb/right-click-options-available-updates/#h-publishing-with-full-content-or-metadata-only)
- What Are Metadata-Only Updates and How to Download and Deploy Metadata-Only Updates? (Blue Icons) (https://patchmypc.com/kb/what-are-metadata-only-updates/)