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.

Messages - MadsB

Pages: [1]
Figured it out collecting the requested log files.

In PatchMyPC-ScriptRunner.log the PLTHub.exe process was found and then the installation is aborted...

So, no need to create a support ticket.

Now is there any elegant way to warn the user before killing the process?

I will become very unpopular with the users if I simply kill the process when they are in an online meeting, but if that is the only option, then so be it.

Maybe this is an idea for a future feature request? To display a nag screen before killing the app process?

We have 19K clients that are running MEMCM CB 2006.

The clients has no problem applying updates for Acrobat Reader DC, Notepad++ and a number of others 3rd party product updates so the client and site setup appear to be working correctly.

PmPC has been a big timesaver patching a lot of apps, but for some reason the updates for the Plantronics / Poly Hub refuses to install, returning error 0x80070643 in the SW center.

I have read somewhere that it might be a problem if the app was installed with the .msi installer and the patch were using the .exe update, but I have tried to install both and the result is the same.

WUAHandler.log list "Installation job encountered some failures. Job Result = 0x80240022." and WindowsUpdate.log lists "Handler         Command line install completed. Return code = 0x00000652, Result = Failed, Reboot required = false"

This has been a problem for at least 3 or 4 updates of Plantronics hub, so something weird is going on.

I have found several suggestions of just wiping the content of C:\Windows\SoftwareDistribution, but before trying that, I would like to hear if someone has a less heavy-handed solution to this?

Any feedback would be appreciated.

Thank you.

Yes, I understand it's a vendor CDN issue, and I'm not blaming PmPC.

Thanks for the link.

Best regards,
Mads Borlund

We still get this error, and the link above has expired.

Any idea when the issue will be solved and if not could you possible re-post the link?

Thank you,
Mads Borlund

Pages: [1]