• Welcome to Support Forum: Get Support for Patch My PC Products and Services.

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - FabianR

I'm currently distributing the Adobe Acrobat Reader DC update 21.005.20048 to multiple clients.
On my client the update fails. I have version 21.001.20155 installed (the update to this version was installed correctly by PatchMyPC about a month ago).
In Software Center I get the error 0x8024002D.

Is there any way I can find out what the issue is?

Thanks for the help.
Is there a way with the publishing service to auto-suspend older versions of updates?
For example currently in SCCM it shows two different versions of Acrobat Reader, version 20 and 21. Both are not suspended and not expired. But I only want the newest version as an update.
The same happens with Paint.Net and PDF24.

I just realized that when I run the "Modify Published Updates Wizard" and search for an update, let's say Adobe Acrobat Reader DC, the newest one that is shown is version 20.006.20042.
But there is already version 21 out.
It's the same with other products, i.e. VLC.

The publishing service updates every day, last time yesterday 7pm.
What can I do to get the latest updates?


I just tested the update of VLC with the activated option for the desktop shortcut removal. I use the publishing service.
The shortcut was not removed! Is this because I use the EXE? On other software updates it worked when the MSI was used.

Best Regards,


We use Patch My PC together with SCCM. WSUS and SUP together are on a seperate VM.
When a new update is published, the SUP sync can't be triggered automatically. This is what the Patch My PC log says:

<![LOG[Triggering a SUP synchronization]LOG]!><time="13:03:29.362+000" date="04-30-2020" component="SccmHelper" context="" type="1" thread="6" file="">
<![LOG[An error occurred while triggering a SUP synchronization: Generic failure  [-1]]LOG]!><time="13:03:29.377+000" date="04-30-2020" component="SccmHelper" context="" type="3" thread="6" file="">
<![LOG[Failed to triggered a SUP sync]LOG]!><time="13:03:29.377+000" date="04-30-2020" component="ConfigMgrSUPSyncLauncher" context="" type="3" thread="6" file="">

Starting a manual sync in SCCM works fine.

Thanks for the help,