Support Forum: Get Support for Patch My PC Products and Services

Commercial Products: Support for Our Enterprise Product for Microsoft ConfigMgr and Intune => Commercial/Paid Products: Support and General Questions (ConfigMgr and Intune) => Topic started by: [email protected] on January 19, 2024, 08:48:59 AM

Title: Java JRE Pre Uninstall Script Not Working
Post by: [email protected] on January 19, 2024, 08:48:59 AM
We have been having issues with the last two JRE versions (8.391 and the recently released 8.401). In the past we have had no issues with pushing this update to our environment. Now it seems that the PatchMyPC pre-script that uninstalls Java (PatchMyPC-Remove-JRE8-64bit-Only.ps1) is not working. The WUAHandler log shows successful. However the log for the removal script shows that it is failing and I am not sure why. The error code line from the uninstall of 8.391 is:

CustomAction isSameFamilyinstalledAndLocked returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Title: Re: Java JRE Pre Uninstall Script Not Working
Post by: Spencer (Patch My PC) on January 19, 2024, 09:57:08 AM
Hey there!

Thanks for reaching out on the forum!

For this error we'll want to take a look at some of the client side log files! Can you please collection the following and email them over to [email protected] with a description of the issue and we can investigate further!

When troubleshooting update installation errors on a client, we will need the following client logs:

%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%WinDir%\CCM\Logs\ScanAgent*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\WUAHandler*.log
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

Can you also run the following script and send over the outputted CSV file:

https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCInstalledSoftware.ps1

Thanks,

Spencer Cruz
Title: Re: Java JRE Pre Uninstall Script Not Working
Post by: stevo on August 20, 2024, 02:23:20 PM
Ive had this issue since 401 I think PmPC aside, now moving to 421 and still same issue. i think its cos some people have a java exe open, perhaps javaw.exe or the like. one user I tested with was using Edge with java running, can't remember exactly but when I got them to totally close out the upgrade managed to uninstall 401 and upgrade to 411.

hope someone sorts this out soon, it usually stays in that error state until the yser has totally closed out of java which could be weeks.

Im using PSADT, If I could find out which exe is causing this then I could propmt user to close it.

CustomAction isSameFamilyinstalledAndLocked returned actual error code 1603
Title: Re: Java JRE Pre Uninstall Script Not Working
Post by: stevo on August 26, 2024, 04:49:14 PM
in my case I think it was cos jp2launcher.exe was still running
Title: Re: Java JRE Pre Uninstall Script Not Working
Post by: JoeG NHS on August 29, 2024, 05:57:43 AM
This months Java update has an issue, its not a PMPC issue really

see reddit and also a clever guy made a fix NOT THAT IM SAYING USE THIS FIX but it just shows what the issue may be

https://www.reddit.com/r/SCCM/comments/1ea1fxh/cant_install_java_8_u_421_1603/

https://eddiejackson.net/lab/2024/07/23/java-client-8-update-421-failing-install-error-1603/

because of this issue, we had some devices upgrading nicely, and others would end up with no java, this is due to PMPC (correctly) removing java then installing newer java. but it uninstalls java fine, but then cannot install new java (error 1603) and then nothing else is done, and devices are left with no java!