• 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

Messages - ronmanp


We publish the Microsoft Teams (x64) application with PatchMyPC Publishing Service which works fine. The installation succeeds but unfortunately it isn't actually available until the user reopens his Windows session.
I understand that the machine installation of Teams is just an installer in ProgramFiles that is triggered for each user that logs into the machine. The problem we experience is that when users install the application from Software Center they expect to have access to the application once the install completes and not have to log off/on. I assume you use the parameter OPTIONS="noAutoStart=true" ?
Is there a way to override that? Would it even work when installed as system? Would I run into trouble I if tried that?


It appears OBS Studio is available in the free catalog but I can't find it in ours which is Enterprise.

We are still using SCUP if it makes any difference.

Thank you,
Hi both x64 and x86 versions are failing with.
PublishItem: --- Digest verification failed on content for software update 'Google Chrome 72.0.3626.96 (x86) (UpdateId:'809deecf-a119-4325-aa92-2d276c4b1075' Vendor:'Patch My PC' Product:'SCUP Updates')'.
PublishItem: --- Digest verification failed on content for software update 'Google Chrome 72.0.3626.96 (x64) (UpdateId:'7cb81314-cf66-4ef0-9952-03cea8c2b250' Vendor:'Patch My PC' Product:'SCUP Updates')'.

I assume it's because 72.0.3626.109 just came out?


Starting with Notepad++ 7.5.7 x86 is no longer being updated on x64 computers.
We are seeing users that were running Notepad++ 7.5.6 x86 version get updated to Notepad++ 7.5.7 x64 which works but during the transition all plugins and cached tabs are lost...
Is this expected?

I also noticed that now the Notepad++ updates have the vendor set to PatchMyPC and product set to SCUP Updates instead of the previous Notepad++ Team vendor and Notepad++ product.
We had to add the new vendor and product into our SUP to get it into SCCM which made us waste a bit of time before figuring out where the problem was coming from. Was that change announced?
This makes sense. The updates I published as PatchMyPC (PowerBI) were all expired.
WSUS shouldn't just completely fail to sync if it doesn't find updates from a product that "no longer exists" but that's not on you.
WSUS is just acting as you would expect... Very badly. 

Consider this resolved!

WSUS wouldn't sync yesterday so I was unable to get the patch Tuesday updates into SCCM.
I checked the log file below and found out this error about PatchMyPC.

Successfully connected to local WSUS server   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:04:34   11548 (0x2D1C)
Successfully refreshed categories from WSUS server   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:12   11548 (0x2D1C)
Attempting connection to local WSUS server   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:12   11548 (0x2D1C)
Successfully connected to local WSUS server   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:12   11548 (0x2D1C)
Category Company:f3135976-b9d1-263d-917d-2e2eb43ff40a (Patch My PC) not found on WSUS   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:12   11548 (0x2D1C)
Subscription contains categories unknown to WSUS.   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:13   11548 (0x2D1C)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error   SMS_WSUS_CONFIGURATION_MANAGER   11/04/2018 21:06:13   11548 (0x2D1C)

After going through the SCCM SUP Product List I unchecked PatchMyPC and now it started syncing again.
We have been using PatchMyPC for quite some time so I'm unsure why this problem occurred yesterday...

I just deployed 7-Zip 18.01 (x64) and unfortunately I lost all file type associations. Could you make it so that it retains these settings after an upgrade?
I understand that it may be challenging considering the upgrade runs as SYSTEM while the file type association is user based...

Thank you,
Could this be re-evaluated? We'd greatly benefit from being able to support JDK through your catalog.

Thank you,
Archived Feature and Product Request / Slack Client
October 19, 2017, 08:02:15 AM
Hi, would it be possible to provide updates for this application?

It's becoming more and more common in enterprises.

Thank you,
Following up on my question.
Hi, I deployed version 7.3.1 (x86) to update from version 7.2.2 but the update would fail to install unless I closed notepad++.
Would it be possible to support a /kill switch as does your Greenshot update?

Seems this -2147287037 error is common with installers running as SYSTEM.

I was able to upgrade this way with version 2014. I will try it again tomorrow.
msiexec /i "p4vinst64.msi" /q /norestart /l+* "%TEMP%\PerforceMSI.log" REINSTALL=ALL REINSTALLMODE=vomus IS_MAJOR_UPGRADE=1

Thanks again
That's unfortunate. What kind of error codes does it return?