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

#91
How long ago was this app created? We actually fixed this issue in a recent publisher release but the app would need to be deleted and recreated in Intune. Could you try to do that and let me know if the recreated app is able to detect right?
#92
Hi,

Is this in Intune or ConfigMgr or WSUS/ConfigMgr Updates? The issue here is that is not a valid version string, but I think we can work around it.
#93
Hi Dominik,

We are actually testing every app in our catalog over the next week. I'll take a look at this one and make sure it is installing correctly and let you know.
#94
I believe you will see the Scheduled Task if you run Task Scheduler as Admin. The task may not be visible to a non-Admin User. The task that Patch My PC creates does indeed run as SYSTEM.

#96
Interesting. In C:\Windows\Temp there should be a log for PatchMyPC-Detection, can you check that log and see if the detection script ran and found anything? It also might be helpful to check PatchMyPC-Scriptrunner in the ccm\logs folder.

If you'd like, you can also submit a case and attach the log files here: https://patchmypc.com/technical-support
#97
Hi,

This is a common issue because we use PowerShell scripts as our detection method. Can you please try the fixes documented here: https://patchmypc.com/applications-fail-to-install-during-osd-in-sccm-with-error-authorizationmanager-check-failed-0x87d00327 and let me know if they help?
#98
Yeah, it seems like the installer is generating some sort of "advertisement" shortcut for users instead of just a shortcut to the install.
#99
Hi there, I think we have determined that PowerToys is actually just making a bad shortcut in the start menu.
We've tested this a bit, but before we make this the standard for this app, could we get a few testers to use this as a post-install script for this app and confirm it fixes the problem?

$PowerToys = "{0}\PowerToys\PowerToys.exe" -f $env:ProgramFiles
$ShortCut = "{0}\Microsoft\Windows\Start Menu\Programs\PowerToys (Preview).lnk" -f $env:ProgramData

if (Test-Path $PowerToys) {
    if (Test-Path $ShortCut) {
        Remove-Item $ShortCut -ErrorAction "Stop"
    }
    $shell = New-Object -ComObject WScript.Shell -ErrorAction "Stop"
    $shortcut = $shell.CreateShortcut($ShortCut)
    $shortcut.TargetPath = $PowerToys
    $shortcut.Save()
}
#100
We will typically post a notification in our release notes, although we didn't do that for this release. We are discussing internally the best way to notify customers for these types of things without becoming too spammy... The last thing we want to do is give our customers notification fatigue.
#101
You are welcome! Sorry for any issues that this may have caused!
#102
When we first released the umbrella client, we were unaware that they provided pre-release versions on their site as well as production versions. We have since moved to only releasing the production versions that they provide on their site, so the version we have in the catalog today is 2.2.580.
#103
None that we are aware of at this time.
#104
We are aware of this issue and was hoping that there would be a release to resolve it from the PowerToys team fairly quickly... That does not seem to be the case. It seems PowerToys does not install correctly as SYSTEM at the moment.
#105
We are currently working on a notification feature for just this scenario. More info here: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-438