- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
Recent posts
#61
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Notepad++ Sources During C...
Last post by sundi712 - February 18, 2026, 04:04:41 PMQuote from: mconwell on February 06, 2026, 04:03:53 PMThe Notepad++ team indicated on 2/5 that the MSI allows to disable the AutoUpdater using: msiexec /i npp.8.9.1.Installer.x64.msi NOUPDATER=1
https://notepad-plus-plus.org/news/clarification-security-incident/
When I look in the Patch My PC publisher, I see installs for the EXE version but none for the MSI version. Because of this, I have been pushing out the EXE version and not using the MSI version (since it shows ZERO installations).
Should we switch from the EXE update to the MSI update? Will it apply? Can the AutoUpdater be disabled using the EXE version?
NOTE: I'm using the Publisher and publishing updates to both ConfigMgr and to Intune.
There's a switch available for the exe installer (/noUpdater). I just tested this by customizing the exe package in PMPC Publisher and it worked. I see that PMPC also has a MSI installer available now, but this is easier than moving 30+ deployments over
https://npp-user-manual.org/docs/command-prompt/#installer-options
#62
Home Updater: Report Detection Issues or Installation Issues / MultiCommander detection issue...
Last post by BOBofBORG - February 18, 2026, 08:29:44 AMHello, I've been using the Patch My PC for a over a year now and ever since I've used this, I've had an issue with MultiCommander where if you use the internal MultiCommander updater, the Patch My PC does not recognize the latest version. I even tested this on a brand new setup with an MC install and when the update occurred Patch did not see the new version.
I'm not sure where the MultiCommander is reading the version info, but both the MC about page along with the MultiCommander.exe file property is updated with the newest version. The only area I found the old version being referenced was in the MC Uninstall registry key.
I'm not sure where the MultiCommander is reading the version info, but both the MC about page along with the MultiCommander.exe file property is updated with the newest version. The only area I found the old version being referenced was in the MC Uninstall registry key.
#63
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Nvidia App
Last post by niclas2874 - February 10, 2026, 05:19:21 AMWe cant install Nvidia App from Company Portal
Tried on newly installed windows 11 25H2 computer
It looks like it doesn't work as System installation
Anyone have same issue or a fix?
Tried on newly installed windows 11 25H2 computer
It looks like it doesn't work as System installation
Anyone have same issue or a fix?
#64
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Problem with Advanced Insight ...
Last post by mconwell - February 09, 2026, 03:15:33 PMI've attempted to install the 2.5.4 release of Advanced Insights and have found that (at least for me) the installer appears to hang after installing the ASP.Net Core Hosting Bundle 8.0.23. The screen says success, but it never proceeds beyond this screen. See the attached screenshot.
The task bar item on my server where this is running has the icon colored green. Not sure what that might mean.
Running on Windows Server 2016 with Admin rights.
Any ideas?
The task bar item on my server where this is running has the icon colored green. Not sure what that might mean.
Running on Windows Server 2016 with Admin rights.
Any ideas?
#65
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Notepad++ Sources During C...
Last post by mconwell - February 06, 2026, 04:03:53 PMThe Notepad++ team indicated on 2/5 that the MSI allows to disable the AutoUpdater using: msiexec /i npp.8.9.1.Installer.x64.msi NOUPDATER=1
https://notepad-plus-plus.org/news/clarification-security-incident/
When I look in the Patch My PC publisher, I see installs for the EXE version but none for the MSI version. Because of this, I have been pushing out the EXE version and not using the MSI version (since it shows ZERO installations).
Should we switch from the EXE update to the MSI update? Will it apply? Can the AutoUpdater be disabled using the EXE version?
NOTE: I'm using the Publisher and publishing updates to both ConfigMgr and to Intune.
https://notepad-plus-plus.org/news/clarification-security-incident/
When I look in the Patch My PC publisher, I see installs for the EXE version but none for the MSI version. Because of this, I have been pushing out the EXE version and not using the MSI version (since it shows ZERO installations).
Should we switch from the EXE update to the MSI update? Will it apply? Can the AutoUpdater be disabled using the EXE version?
NOTE: I'm using the Publisher and publishing updates to both ConfigMgr and to Intune.
#66
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Manual edits of Package.xm...
Last post by Andrew Jimenez (Patch My PC) - February 06, 2026, 08:42:15 AMYou definitely need to keep the ÿ it is used as a separator for all the values passed to scriptrunner.
You should be able to manually modify package.xml, as long as it gets all of the values it expects it should work fine.
You should be able to manually modify package.xml, as long as it gets all of the values it expects it should work fine.
#67
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Error 615 during TS Instal...
Last post by snukkel - February 06, 2026, 07:54:31 AMI republished all the managed pmp apps now the error in the TS is gone and apps install again.
#68
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Error 615 during TS Instal...
Last post by snukkel - February 06, 2026, 06:15:35 AMCould you share that link? I have got the same issue
#69
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: ESP Slow, Update Applicati...
Last post by steadybird - February 05, 2026, 06:09:37 PMQuote from: MassDeployment on January 28, 2026, 09:47:56 PMI am experiencing this issue now. I pre-provision my devices and I only have 8 apps required in there. The pre-provisioning is fine, computer Reseals then I give it to the user. The problem is that when the user logs in and it does the ESP Device setup section, the Apps (Identifying) takes like 10 minutes, then it says (None Applicable) or something like that.
I checked the AppWorkLoad.log and I can see that's evaluating all my "Update for <app>" packages because they are marked as Required to All Devices.
Lets say I have the VLC Media Player package created, I mark it as Available for All Devices that way people can download from Company Portal. I also create the Update for VLC Media Player package and mark it as Required for All Devices, assuming that that way when an update gets released those who installed the software will get the update.
My AppWorkLoad.log is processing around 45 packages.
What can I do so I can make this better?
Same recommendation was given above I would suggest.
Remove the UPDATES from ESP entirely. It's not necessary to have them there.
They will still evaluate separately based on the Standard InTune evaluation cycles after ESP completes and the device is online.
Keep the ESP list restrained to only the most critical core requires apps. Everything else shouldnt be in ESP.
#70
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Manual edits of Package.xml po...
Last post by steadybird - February 05, 2026, 05:59:05 PMHi Team,
I am looking to grab copies of our PMPC deployed items and throw them at some servers with custom login scripts. Unfortunately the CIO veto'd my idea to implement WSUS and we don't have the budget for SCCM... So I am having to perform alternatives.
I wanted to make some customisations to the deployment and thought I could do so via amendments to the Package.xml. Reviewing the file it seems straight forward enough but I am wondering around the "ÿ" I see at the end of each argument.
This looks to be something that doesn't render natively in utf-8 so I worry if I make edits to the file will the PMPC scriptrunner still understand Package.xml.
What happens if I remove the "ÿ"?
What happens if in an existing Package.xml that does not include a specific argument, I manually insert a copy sourced from another file and abide by the syntax?
I am looking to grab copies of our PMPC deployed items and throw them at some servers with custom login scripts. Unfortunately the CIO veto'd my idea to implement WSUS and we don't have the budget for SCCM... So I am having to perform alternatives.
I wanted to make some customisations to the deployment and thought I could do so via amendments to the Package.xml. Reviewing the file it seems straight forward enough but I am wondering around the "ÿ" I see at the end of each argument.
This looks to be something that doesn't render natively in utf-8 so I worry if I make edits to the file will the PMPC scriptrunner still understand Package.xml.
What happens if I remove the "ÿ"?
What happens if in an existing Package.xml that does not include a specific argument, I manually insert a copy sourced from another file and abide by the syntax?