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

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 - Andrew Jimenez (Patch My PC)

#256
This should have actually been fixed by Microsoft with KB4557957
#257
Thanks, and thank you for working with us!

If anyone else is running into this issue, we found that an old migration update for Firefox to Firefox ESR was still showing for this user. This update had been expired previously, but somehow wasn't expired in this case. We will be re-adding the expired update to the catalog to ensure that it is truly expired for all users.

The workaround until we publish a new catalog update is to decline the updates using our Modify Updates Wizard.
#258
Hello,

Could you please get us the logs, through our technical support email would probably be the best: https://patchmypc.com/technical-support

I did a quick check on the applicability rules and installers for those updates, and everything seems to check out right now, so I'd like to see the logs showing what is going on. Thanks!
#259
Thanks for testing. This should be resolved in today's catalog update, please let us know if you continue to experience this issue tomorrow.
#260
Can you try toggling that application off and on in the publisher, click "apply" then right click, republish then resync?
We added a new script to the application to block norton from installing and I am thinking it is not being enabled correctly. Toggling the app off and on should set the settings correctly and allow a republish.
#261
We'll definitely keep an eye out, and if you are able to determine how to block updates, please let us know and we will add it to the product. Thanks!
#262
I just did some additional searching and it does not seem that Amazon has added this feature. I did notice multiple complaints about this same issue on their boards however.
#263
SCCM uses WSUS for it's update deployments, so that part should be just fine.

Your method should still work, and if you are on the Basic license, I believe that is how you have to manage things generally. We do have more automated methods available on the Enterprise plan if you are interested.

I have seen iTunes act odd before, but always have a hard time replicating and determining what the actual issue is. I haven't heard anything about Dropbox updates causing problems though.

Thanks for reporting, we'll keep an eye out for additional issues!
#265
I was unable to repro in our test environment. SCCM 2003 TP and Windows 10 2004.

#266
This is excellent, we will work to reproduce the issue and try to get it on Microsoft's radar. Thanks again for bringing it to our attention!
#267
Hello,

We're not currently tracking this issue, but will set up a Windows 10 2004 system in our lab and see if we can reproduce. We'll keep you updated on what we find.
#268
Quote from: rweigand on April 03, 2020, 12:15:20 AM
Quote from: Andrew Jimenez on April 02, 2020, 02:30:55 PM
Turning out to be trickier than expected... We'll keep investigating!

Thnx a bunch for your trouble!
Btw, why not switch to detection by file version? Chrome on a x64 system always gets installed to "C:\Program Files (x86)\Google\Chrome\Application", and on a x86 system to "C:\Program Files\Google\Chrome\Application", right?

You would think so, but that isn't always the case. We do use file version, but rely on the path provided by that registry value to get the Google Chrome path. Literally the only difference between the Google Chrome and Beta installer is where they are installed, which is why we haven't been able to differentiate between the two.

An alternative for you for now could be to set a CI or Group Policy to set the reg key "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe\Path" to the path where Google Chrome <non-beta> is installed such as C:\Program Files (x86)\Google\Chrome\Application
#269
Turning out to be trickier than expected... We'll keep investigating!
#270
We're looking at this now. I think we found a good alternate path to look for that wont pull the beta.