Resolving RegUtils error per-machine when deploying Java via SCCM

I’ve previously discussed how to deploy Java via SCCM 2007. The most common reason for this deployment to fail in our environment is “Internal Error 2753. regutils.dll”. It looks like this error is typically caused by having a browser or Java itself running when you try to update it. Here’s what we do to resolve it (with JavaRa and JavaMSIFix on network shares, this whole process takes less than a minute per client):

1. Open SCCM Client Center and connect to the PC in question
2. In the Inventory Actions section, select the AddRemove Programs tab and click Get Installed Software.
3. If Java is listed, remote onto their machine and go to in IE. Click Do I have Java?. You should get a message that Java is installed, or maybe one saying your version of Java is out of date. This is good (unless your environment should have the latest version of Java). You’re done!
4. If Java is not listed, remote into their machine and close out of all web browsers. Run JavaRA as Admin. Select Remove Older Versions. Once that’s complete, you should get a text file logging the progress. Close out of that.
5. Run JavaMSIFix.exe (also as Admin). It’s pretty self-explanatory.
6. Go back to the SCCM Client Center, and rerun the appropriate Java advertisement.
7. Check to make sure Java is now correctly installed by pulling up Add/Remove Programs. If it’s listed there, you’re all set!

2 thoughts on “Resolving RegUtils error per-machine when deploying Java via SCCM

  1. Garrett

    We were getting a high number of reports of Java not being recognized in IE after updating to Java 7 Update 11. Note: We were targeting PC’s with Java 7, Update 7. After a bunch of trouble shooting, we figured out that if Internet Explorer was open will installing this via SCCM, it was causing the problem. For problem PC’s. we had to remove Java, reboot and then install Java only if IE was closed. For future installs, we had to make sure IE was closed before updating Java.

  2. Mark Swift

    Have repaired this viz:
    Admin Edit the Registry – search for “java” – in the HKCR hive will be several entries under the hashed GUID for java. The major entity is the HKCR\Installer\Features\ key – listed there are all the installed MSI Features for java. Deleting this hive should enable the subsequent install. There are 2 more similar keys in HKCR which I cleaned up at same time. I had also pre-run msizap for the java version, although this did not remove the UpgradeCode key – manually deleted that – this may be a skippable step. That should be sufficient to eliminate the 2753.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please do some math to prove you\'re a human: * Time limit is exhausted. Please reload the CAPTCHA.