• 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 - wokkeltje

We notice that the update of Git is failing because of running processes. However the update is marked to kill the processes.

See attach for the logs.
I noticed that not all my machines are picking up the Visual C++ 2015-2019 redistributable updates. attached is a client (server 2016) that does not get the x64 update, but I think I have situations where x86 is not picked up.

The update of last week is not yet approved for deployment, but detection is the same.

If you can tell me the detection method (or where I can find myself) I can check the machine why it is missing this 1 update.
The Docker Desktop updates are already 2 versions behind


version and are not in the db, last version is already 20 days old

This is probably an issue of the software itselve, but on their website they write the following about how to upgrade
2.8 WhatÔÇÖs the best way to upgrade?

ThatÔÇÖs a matter of taste. For most people the best thing to do is to uninstall R (see the previous Q), install the new version, copy any installed packages to the library folder in the new installation, run update.packages(checkBuilt=TRUE, ask=FALSE) in the new R and then delete anything left of the old installation. Different versions of R are quite deliberately installed in parallel folders so you can keep old versions around if you wish.

For those with a personal library (folder R\win-library\x.y of your home directory, R\win64-library\x.y on 64-bit builds), you will need to update that too when the minor version of R changes (e.g. from 3.0.2 to 3.1.0). A simple way to do so is to copy (say) R\win-library\3.0 to R\win-library\3.1 before running update.packages(checkBuilt=TRUE, ask=FALSE).

It would be nice to have a possibility to uninstall previous versions during update.
I noticed that the disable self updater function is not working for the Java update. The Update tab is still visible and scheduled to notify before download after the update.

We use the following to completely disable the update (we extract the msi from the exe installer)
msiexec /i jre1.8.0_171.msi JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q
This command also hides the update tab.

I can't find a solution to patch the Visual C++ redistributable tools installed on every PC.
In Software Update Management or WSUS I don't seem to find a category I can use to enable them.

Can Patch My PC integrate them?

Especially version 2017 would be nice.
Older versions (I think pre 2013) don't upgrade but install a newer version next to the older one. so this is most likely not what we want. newer versions correctly upgrade (version 2015 upgrades to version 2017)

PDFSam installer has the following possible options during install

Can these be added to the catalog?

This tool is not detected when not installed on the default location on the C drive.
We install SQL server on a separate drive.

MS has released the same update on 15/12/2018 and this one is detecting our installations correctly.
We receive an error when installing the TeamViewer 13 update. Any idea what can be the reason? Other updates are working OK.

<![LOG[Successfully completed synchronous searching of updates.]LOG]!><time="09:02:00.837-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="1376" file="cwuahandler.cpp:980">
<![LOG[1. Update: 0d6bb41c-cfd5-474f-99a3-9b0c48e581c5, 2   BundledUpdates: 0]LOG]!><time="09:02:01.054-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="1376" file="cwuahandler.cpp:1698">
<![LOG[1. Update (Missing): TeamViewer 13.2.26558 (0d6bb41c-cfd5-474f-99a3-9b0c48e581c5, 2)]LOG]!><time="09:02:01.054-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="1376" file="cwuahandler.cpp:1820">
<![LOG[Async installation of updates started.]LOG]!><time="09:02:01.639-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="1376" file="cwuahandler.cpp:2273">
<![LOG[Update 1 (0d6bb41c-cfd5-474f-99a3-9b0c48e581c5) finished installing (0x80070002), Reboot Required? No]LOG]!><time="09:02:03.073-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="10632" file="cwuahandler.cpp:2451">
<![LOG[Async install completed.]LOG]!><time="09:02:03.073-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="10632" file="cwuahandler.cpp:2478">
<![LOG[Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001.]LOG]!><time="09:02:03.074-60" date="01-04-2019" component="WUAHandler" context="" type="2" thread="1376" file="cwuahandler.cpp:4351">
<![LOG[Installation of updates completed.]LOG]!><time="09:02:03.074-60" date="01-04-2019" component="WUAHandler" context="" type="1" thread="1376" file="cwuahandler.cpp:4742">
Is there a possibility to use native SCCM patching and still use Pre/post installation scripts and kill processes feature?

An example:
* Citrix HDX RealTime Media Engine can't be installed if wfica32.exe is running. currently the update is failing since our users are constantly working in a Citrix session, so the process is running the whole day.
* Oracle Java update does not disable update feature when installing the new version, how can we add the following install parameters? JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1

When trying to publish an Adobe Acrobat Reader DC update I receive the following error in the "SMS_ISVUPDATES_SYNCAGENT"

Failed to publish content for update "49f95540-6b94-443a-966e-0c386ce2c209" because the content signing certificate "CN="Adobe Systems, Incorporated", OU=Acrobat DC, O="Adobe Systems, Incorporated", L=San Jose, S=California, C=US, PostalCode=95110, STREET=345 Park Ave, SERIALNUMBER=2748129, OID., OID., OID.2.5" has not been approved.

Solution: Review and approve the content signing certificate from the Certificate node and try again.
Previous Adobe update had same issue.

Other updates are published without an issue. This seems to be Adobe issue.
We use native SCCM 3rd party patching without the Publishing Service
Notepad++ 7.6.0 (x86) is not detected to update in native SCCM Third Party patching when not installed in default location.

x64 version on a different machine and installed in defaul location is detected OK

So I am not sure if it is related to the not default location or if it is related to x86 version
I notice an issue with the patch catalog (since the order is still pending in our administration, I use the Trial Catalog to get used with the system, so excuse me if the issue is only related to the Trial catalog).

Let me explain: we deploy patches once a month, and only once a month except some urgent emergency reason (day after MS Patch Tuesday) all the approved patches follow a couple of stages (available on test machines for 5 days, accept machines the 7 days after test phase and another week later, all our production machines)

Now with 3rd party patching using the PatchMyPC catalog we experience that the patches in the catalog not contain superseed info. For example the moment a new Google Chrome update becomes available and SCCM did the sync of the catalog, the previous update immediately expires. This means that our production machines never receive the Chrome update since the available time of the approved update is past the expire date.

I know that you should always deploy the latest version, but since we use Chrome in a production environment, a new version need to pass the test/accept stage.The same for Java updates and so.

Can the catalog be expanded with the superseding info the same way MS is providing their patches? Chrome version 70 superseeds verion 69.
In SCCM you can define the time before a superseeded update gets expired to get rid of old versions.

thanks in advance
Since Citrix Receiver and Citrix Wokplace are available in the catalog, the extra client component HDX RealTime Media Engine can't be absent.