Messages

We do supersede updates. Versions 15, 17, 20 and 21 are major versions which are still in support by Adobe.

If you no longer want these updates, deselect them from the Publisher and decline them in WSUS. Note: deselecting products in the publish does not remove existing updates from your environment, you still need to decline them.

Hey FabinaR

You can decline updates in WSUS using the Run Wizard tool in the Publisher: https://patchmypc.com/modify-published-third-party-updates-wizard

Declining updates in WSUS and syncing your SUP will show those updates as expired in the ConfigMgr console.

Hi David

As far as we know, no. If you encounter any which need to be added to the list, let us know and we can review / update the page.

It looks like there's a new version available, too.

I've contacted the vendor seeking support on the issue, once we get a reply we should be able to fix: https://forums.spybot.info/showthread.php?77585-Fail-to-install-silently-Failed-to-proceed-to-next-wizard-page-aborting&p=485891#post485891

Hi PMPC,

We have similar concerns over the auto update of the apps which we want to test before rolling it out to production. Is there any article or guide that we can refer to for cases like this?

Appreciate any help provided. We are now running the trial version of PMPC - 1 week old

What information do you need specifically? This section here on this article details the right click option: https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#disable-updates

Hi, you can read more about the software on the vendor's website here: https://www.iobit.com/en/driver-booster.php

Hello

For 0x80070643 / 1603, you can refer to this article: https://patchmypc.com/installation-fails-with-error-code-1603

For the others, please collect these log files from each example failing client and share them: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs-intune

Thanks
Adam

Hello

Could you share WCM.log, wsyncmgr.log and WSUSCtrl.log please? You might prefer emailing these to [email protected] as they will contain hostnames or IP addresses.

Thanks
Adam

No problem, reach out if there's more we can do.

The new version (15.0.18384.0) was released yesterday by Microsoft so it should be in our next catalogue release.

That error code resolves to 1603 which is unfortunately generic and usually a client-side issue. Generally there's more detail in the vendor install log files or if you launch the installer GUI on the problem device. We have an article which discusses that here some more: https://patchmypc.com/installation-fails-with-error-code-1603

[J:\WSUS]

I looked at the KB for this issue as well as followed the video but I'm confused.  I've never stood up a separate software update point as the video suggests as a possible cause.

The registry entry cites J:\WSUS, which is the SQLTempDB volume.  I've absolutely no idea how it got there.  It's also got nothing in it beyond two folders WsusContent and UpdateServicesPackages.   
The SQL query cites G:\WSUS, which I think is where it's supposed to be.  That's the Content Source volume, and it's definitely got lots of contents, clocking in at three quarters of a terabyte.
The IIS Basic Settings cite C:\Program Files\Update Services\WebServices\Root as the physical path.

When I run the wsusutil.exe to specify G:\WSUS, it tells me:

Content location is being moved. Please do not stop this program.
Content move failed. Please refer to the log file for more details.
Fatal Error: The new content file location is the same as the old location: G:\WSUS
Parameter name: newContentPath

Should I move it somewhere else?

It sounds like you've got a bit of a mismatch as to where the registry, IIS (specifically the path for the virtual directory "Content") and the database thinks your content path actually is. I can help you get this fixed up but it might just be simpler over the phone.

The registry value, shared folder paths and IIS Content virtual directory path described here are the things we will all want to match with what SQL is referencing. Use this link to book a 60 minute call with me so we can take a look at this.

[not installable]

Hi Adam,

Sorry for the late reply, i tought i send a reply on wednesday, but probably forgot to press Post 

Thx for the tip,
I have changed the Runtime to 60 min, but no luck, it give the error after about 3 to 5 min of running.

What is also strange is that last week i uninstalled the SSMS on my pc, and then installed it with the new version, everything was ok, until Wednesday then the patch was again on my pc and failing with the same error.
When i looked in the SCCM console my pc went from Installed to required again

In the console i do see a lot of pc's that require the patch and if i look at the inventory the version is correct
"Microsoft SQL Server Management Studio - 18.8   {29fdeb7a-f6e5-40c3-a203-e306837e95a4}      Microsoft Corporation   15.0.18369.0"
My assumtion is that there is something wrong with the detection rule for this patch

Hi Frank

I've just updated SSMS v18 15.0.18358.0 to v18 15.0.18369.0 with no issue. Update evaluated as installed after the install completed.

Below are the applicability rules for SSMS v18 15.0.18369.0. Are you able to discern any reason why your clients are evaluating as not installable (i.e. not required)?

IsInstallable

Code Select Expand

<lar:And>
  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio\18" Value="Version" />
  <bar:RegSzToVersion Comparison="LessThan" Data="15.0.18369.0" Value="Version" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio\18" />
</lar:And>

IsInstalled

Code Select Expand

<lar:And>
  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio\18" Value="Version" />
  <bar:RegSzToVersion Comparison="GreaterThanOrEqualTo" Data="15.0.18369.0" Value="Version" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio\18" />
</lar:And>

More info on finding applicability rules here: View Applicability Rules and Troubleshoot Detection States for Third-Party Updates

Hi,
why was 11.2.5.26209 expired and previous version re-enabled?
We have experienced some problems with version 11.2.5.26209 and noticed the update is no longer available so wondering whether there is any relation?

Hi

Yes, we received notifications there was an issue with it caused by the vendor, so we pulled it from our catalogue.

Thanks
Adam

We checked the Adobe Acrobat Reader 2020 Classic in the "Updates" Tab.
But after running the sync no update was downloaded.
I used the button "Show package info: title, command-line- download URL, etc." and the window is empty.
Seems to be not fully implemented.

Could somebody from Patch-My-PC check, please?
Thanks!

Hi sw-deploy!

We have removed Adobe Acrobat Reader 2020 Classic from our catalogue as it is not supported at this time. We are working on it and hopefully it will be in there soon.

Thanks!
Adam

[All software updates]

Hi Adam,

Thx for the quick reply.
It is localy on my workstation and on several other workstations.

The error 0x87D00668 also means: "Software update still detected as actionable after being applied"

things i already tried
1. repair dot net, no succes
2. repair windows update, no succes
3. uninstall the management studio and install it again with the new version, fixed the issue, but is not what i'm looking for

Hi Frank

What is the update's max run time? Right click on the software update within the All software updates node of the ConfigMgr console, choose Properties and look in the Maximum Run Time tab. If it's 10 minutes, perhaps try setting it to 60 minutes as a test and see if the update needs longer on your devices to install.

Thanks
Adam