- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
Recent posts
#11
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Oracle Java Runtime parame...
Last post by Bogdan (Patch My PC) - May 06, 2025, 07:35:23 AMHey there!
We already have that covered — the following is the default we use:
/s REBOOT=ReallySuppress
If your question is about point #3:
WEB_JAVA=1 (which associates .jar files with javaw.exe and .jnlp with jp2launcher.exe) — we don't set any config options for apps.
That said, we totally understand that some folks might want a newer version of Java to be the default file handler, while still keeping Java 8 around for specific apps.You are absolutely free to customize the command line to suit your environment and needs.
Hope that helps! Let us know if you have any other questions.
We already have that covered — the following is the default we use:
/s REBOOT=ReallySuppress
If your question is about point #3:
WEB_JAVA=1 (which associates .jar files with javaw.exe and .jnlp with jp2launcher.exe) — we don't set any config options for apps.
That said, we totally understand that some folks might want a newer version of Java to be the default file handler, while still keeping Java 8 around for specific apps.You are absolutely free to customize the command line to suit your environment and needs.
Hope that helps! Let us know if you have any other questions.
#12
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Oracle Java Runtime remova...
Last post by Antony (Patch My PC) - May 06, 2025, 06:47:51 AMGood Afternoon,
It appears you are using our PatchMyPC-Remove-JRE8-64bit-Only.ps1 script which removes all Java 8's. This is why you are seeing this behaviour in the logs.
Could you please use the script found at the following link instead? https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall-Software
Thank you,
Antony
It appears you are using our PatchMyPC-Remove-JRE8-64bit-Only.ps1 script which removes all Java 8's. This is why you are seeing this behaviour in the logs.
Could you please use the script found at the following link instead? https://github.com/PatchMyPCTeam/Community-Scripts/tree/main/Uninstall/Pre-Uninstall/Uninstall-Software
Thank you,
Antony
#13
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Re: Oracle Java Runtime remova...
Last post by GeoSimos - May 06, 2025, 06:19:02 AMQuote from: GeoSimos on May 06, 2025, 03:39:15 AMHello PMPC Team,Regarding the auto close of the processes, I hadn't enabled the conflicting processes options for the custom apps, that means that if it was enabled, that issue wouldn't happen. However, it doesn't negates the erroneous report in the log file.
Lately, I had to use the custom apps functionality, to create a previous version of Oracle's Java Runtime and target it to a specific group of devices.
As I was working on it, I thought as a good idea to use the removal script you included in the PMPC apps and I did.
However, I saw the following behavior, while the removal script kicked in, it found the newer JRE version and started removing it but, because there were jp2launcher.exe processes running, it was failing with error 1603.
The script though was stating incorrectly:Code SelectStarting log for JRE removal for Patch My PCIn SCCM's monitoring, the failure is reported correctly, also makes me wonder how the installation kicks in, when the jp2launcher.exe process is running.
Now removing Java 8 Update 441 using command {77724AE4-039E-4CA4-87B4-2F32180441F0}
Now building the MSI arguments for start process
Now submitting the following arguments to start-process using MSIExec.exe /x {77724AE4-039E-4CA4-87B4-2F32180441F0} /qn /L*v "C:\Windows\Temp\PatchMyPC-Java 8 Update 441.log" REBOOT=REALLYSUPPRESS
The application was uninstalled with Exit Code: 1603
The application has been succesfully removed
Starting log for JRE removal for Patch My PC
Now removing Java 8 Update 441 using command {77724AE4-039E-4CA4-87B4-2F32180441F0}
Now building the MSI arguments for start process
Now submitting the following arguments to start-process using MSIExec.exe /x {77724AE4-039E-4CA4-87B4-2F32180441F0} /qn /L*v "C:\Windows\Temp\PatchMyPC-Java 8 Update 441.log" REBOOT=REALLYSUPPRESS
The application was uninstalled with Exit Code: 1603
The application has been succesfully removed
#14
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Oracle Java Runtime parameters...
Last post by GeoSimos - May 06, 2025, 06:01:54 AMHello PMPC Team,
We have been dealing with inconsistent behavior of Oracle Java Runtime 8 file associations for some time now, and lately I had to provide a previous version of it for a specific group of devices.
Using custom apps, I had to dig a bit and find the parameters you can pass to the .exe installer, from them I tested the following and they work fine so far:
I have added the parameter #2 in the PMPC Publisher's options for Oracle Java Runtime ConfigMgr Apps and Updates and works fine.
I'm not 100% sure for the AUTO_UPDATE=Disable parameter (it seems to be applied during install), as I saw prompts for update of the older version at users.
Would you consider incorporating #2 in your configuration files for Oracle JRE -could apply to JDK also but I don't do it to avoid creating a mess with file associations-.
Kind regards
We have been dealing with inconsistent behavior of Oracle Java Runtime 8 file associations for some time now, and lately I had to provide a previous version of it for a specific group of devices.
Using custom apps, I had to dig a bit and find the parameters you can pass to the .exe installer, from them I tested the following and they work fine so far:
- /s (Silent Install)
- REBOOT=ReallySuppress (Self explanatory)
- WEB_JAVA=1 (associates .jar files with Javaw.exe and .jnlp with jp2launcher.exe)
- /L C:\Windows\Logs\JRE8421_Install.log (creates a log file of the installation, careful with the syntax there, it doesn't likes environment variables, nor enclosed in quotes paths, you can see in the jusched.log file how the installer constructs them, very handy)
- AUTO_UPDATE=Disable (Self explanatory)
I have added the parameter #2 in the PMPC Publisher's options for Oracle Java Runtime ConfigMgr Apps and Updates and works fine.
I'm not 100% sure for the AUTO_UPDATE=Disable parameter (it seems to be applied during install), as I saw prompts for update of the older version at users.
Would you consider incorporating #2 in your configuration files for Oracle JRE -could apply to JDK also but I don't do it to avoid creating a mess with file associations-.
Kind regards
#15
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Oracle Java Runtime removal sc...
Last post by GeoSimos - May 06, 2025, 03:39:15 AMHello PMPC Team,
Lately, I had to use the custom apps functionality, to create a previous version of Oracle's Java Runtime and target it to a specific group of devices.
As I was working on it, I thought as a good idea to use the removal script you included in the PMPC apps and I did.
However, I saw the following behavior, while the removal script kicked in, it found the newer JRE version and started removing it but, because there were jp2launcher.exe processes running, it was failing with error 1603.
The script though was stating incorrectly:
Lately, I had to use the custom apps functionality, to create a previous version of Oracle's Java Runtime and target it to a specific group of devices.
As I was working on it, I thought as a good idea to use the removal script you included in the PMPC apps and I did.
However, I saw the following behavior, while the removal script kicked in, it found the newer JRE version and started removing it but, because there were jp2launcher.exe processes running, it was failing with error 1603.
The script though was stating incorrectly:
Code Select
Starting log for JRE removal for Patch My PC
Now removing Java 8 Update 441 using command {77724AE4-039E-4CA4-87B4-2F32180441F0}
Now building the MSI arguments for start process
Now submitting the following arguments to start-process using MSIExec.exe /x {77724AE4-039E-4CA4-87B4-2F32180441F0} /qn /L*v "C:\Windows\Temp\PatchMyPC-Java 8 Update 441.log" REBOOT=REALLYSUPPRESS
The application was uninstalled with Exit Code: 1603
The application has been succesfully removed
Starting log for JRE removal for Patch My PC
Now removing Java 8 Update 441 using command {77724AE4-039E-4CA4-87B4-2F32180441F0}
Now building the MSI arguments for start process
Now submitting the following arguments to start-process using MSIExec.exe /x {77724AE4-039E-4CA4-87B4-2F32180441F0} /qn /L*v "C:\Windows\Temp\PatchMyPC-Java 8 Update 441.log" REBOOT=REALLYSUPPRESS
The application was uninstalled with Exit Code: 1603
The application has been succesfully removed
In SCCM's monitoring, the failure is reported correctly, also makes me wonder how the installation kicks in, when the jp2launcher.exe process is running. #16
Home Updater: Report Detection Issues or Installation Issues / Re: 32-bit Installation of Win...
Last post by dking02 - May 06, 2025, 03:24:07 AMQuoteToday, Home Updater v5 only supports 64-bit apps.
Not true. Home Updater v5 supports a number of apps which are only available as 32-bit apps and that it will install and update on 64-bit Windows. For example, I have 49 supported non-portables installed on my machine, of which nine are only available as 32-bit apps: Belarc Advisor, BleachBit, Fan Control, Foxit PDF Reader, GadgetPack, Microsoft Visual C++ 2013 and 2015-2022 Redistributables (x86), NVIDIA PhysX, Resource Hacker.
QuoteOut of curiosity, is there a specific reason you're sticking with the 32-bit version of WinMerge
WinMerge released a 64-bit version with v2.16.0 in Nov 2018. I had already been relying on the existing 32-bit version of WinMerge with an unofficial 32-bit plugin (xdocdiff) to perform comparison of text in two PDFs. It was simpler to stick with older platform which works well rather than risking possible incompatibilities and having to expend unnecessary, additional effort. I have also been sticking with 32-bit versions of IrfanView and Notepad++ both of which use plugins and will now be similarly affected by Home Updater v5 only providing 64-bit updates to these apps. They introduced 64-bit versions in Jul 2015 (v4.40) and Sep 2016 (v7.0), respectively.
In response to this topic, I have taken a look at the current situation with these three programs and have decided to switch to their 64-bit versions. In the case of WinMerge, I am also installing its 32-bit version to support regression testing of other 32-bit software. Since Home Updater v5 only offers 64-bit updates of WinMerge, the additional 32-bit installation will not be affected and the update to the 64-bit version will serve as notification to manually download the 32-bit update from the WinMerge.org website.
References:
Advantages of 64-bit and 32-bit versions of IrfanView
https://www.irfanview.com/64bit.htm
32-bit vs 64-bit versions of WinMerge
https://github.com/WinMerge/winmerge/discussions/2193
#17
Home Updater: Report Detection Issues or Installation Issues / Brave not being detected, but ...
Last post by ExpDeviant - May 05, 2025, 12:52:37 PMGood day,
the installation of Brave does work as such, but is not being detected, after it has been installed.
Best Regards
Exp
the installation of Brave does work as such, but is not being detected, after it has been installed.
Best Regards
Exp
#18
Home Updater: General Support and Troubleshooting / Re: ERROR System.ArgumentExce...
Last post by TerryWood - May 05, 2025, 01:36:41 AMHi Justin
As per my previous post a second Task scheduled update has concluded satisfactorily so I think we can say job done.
Thank to you and your team.
Terry
As per my previous post a second Task scheduled update has concluded satisfactorily so I think we can say job done.
Thank to you and your team.
Terry
#19
Home Updater: General Support and Troubleshooting / Re: ERROR System.ArgumentExce...
Last post by TerryWood - May 04, 2025, 11:13:52 PMHello Justin
I have just upgraded to v5.2.0.1 having set 7Zip to version 19 again (not the latest version) and reset the scheduled time of update to 0600hrs UK time. I can confirm that it has updated as a task.
I am doing the same thing again on a later schedule to be absolutely certain.
If it updates again then thank you to you and all those involved for helping resolving this issue. It is a splendid job.
Terry
I have just upgraded to v5.2.0.1 having set 7Zip to version 19 again (not the latest version) and reset the scheduled time of update to 0600hrs UK time. I can confirm that it has updated as a task.
I am doing the same thing again on a later schedule to be absolutely certain.
If it updates again then thank you to you and all those involved for helping resolving this issue. It is a splendid job.
Terry
#20
Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) / Deprecation of WSUS & Alternat...
Last post by steadybird - May 04, 2025, 07:23:23 PMHi All,
We're currently using the desktop publisher to push apps and updates into Intune and it's working quite well for us. On-prem server patching is a rather manual process for us currently even if we're still using extracted PMPC Intune packages of the same software and running it that way.
Budgeting for System Center was not approved.
I considered WSUS with scanning sources enabled such that the rest of the server updates would come from Windows Updates directly, and only PMPC stuff via WSUS... However, my CIO has veto'd that due to WSUS's deprecated status.
For SMB's... What are the alternatives available to us?
Is PMPC considering options for integrations to help fill in that niche that WSUS will leave? That being those SMB's that can't justify forking out for something as overkill as System Center?
Perhaps using a variation of their personal desktop client as a kind of server-side client "agent", that could interact with a local data store/share of some kind. With PMPC Publisher pushing content into that local store for the agents to use on whatever schedule they're configured for, or manually?
Right now I am half considering trying to emulate the overall PMPC process by using PMPC requirement scripts, packages, and deployed scheduled tasks to run them all. But this is a very manual process for me to design this and then ongoing work to manually extract and transfer all the content into the staging area.
I would love if there was a PMPC native solution so that I could continue to use PMPC Publisher as my primary pane of glass to push content to all of my end points be they Intune MDM devices or on-prem servers.
We're currently using the desktop publisher to push apps and updates into Intune and it's working quite well for us. On-prem server patching is a rather manual process for us currently even if we're still using extracted PMPC Intune packages of the same software and running it that way.
Budgeting for System Center was not approved.
I considered WSUS with scanning sources enabled such that the rest of the server updates would come from Windows Updates directly, and only PMPC stuff via WSUS... However, my CIO has veto'd that due to WSUS's deprecated status.
For SMB's... What are the alternatives available to us?
Is PMPC considering options for integrations to help fill in that niche that WSUS will leave? That being those SMB's that can't justify forking out for something as overkill as System Center?
Perhaps using a variation of their personal desktop client as a kind of server-side client "agent", that could interact with a local data store/share of some kind. With PMPC Publisher pushing content into that local store for the agents to use on whatever schedule they're configured for, or manually?
Right now I am half considering trying to emulate the overall PMPC process by using PMPC requirement scripts, packages, and deployed scheduled tasks to run them all. But this is a very manual process for me to design this and then ongoing work to manually extract and transfer all the content into the staging area.
I would love if there was a PMPC native solution so that I could continue to use PMPC Publisher as my primary pane of glass to push content to all of my end points be they Intune MDM devices or on-prem servers.