UNSOLVED

FlippyFF

updated

2 years ago

F

FlippyFF

1 Rookie

•

22 Posts

•

3 Points

0

1852

May 28th, 2024 16:23

3.4.4 to 3.4.5 upgrade fails on Windows due to unsecure Java?

I'm currently running DRM 3.4.4 and it's prompting me to download and install 3.4.5. The download is successful but when the installer runs, it fails and reports "The JVM used for this installs seems to have been installed in a unsecured location (non-admin user folder. Installer would now exit. Please reach out to your vendor for more details."

The only copies of JVM.dll I have are in:

C:\Program Files\Dell\Dell Repository Manager\jre_11\bin\client

C:\Program Files\Dell\Dell Repository Manager\jre_11\bin\server

C:\Program Files (x86)\Dell EMC\Unity\ConnectionUtility\jre\bin\server

C:\Program Files (x86)\Dell EMC\Unity\Unisphere CLI\jre\bin\server

and java.exe in:

C:\Program Files\Dell\Dell Repository Manager\jre_11\bin

C:\Program Files (x86)\Dell EMC\Unity\ConnectionUtility\jre\bin

C:\Program Files (x86)\Dell EMC\Unity\Unisphere CLI\jre\bin

I tried uninstalling v3.4.4, downloading 3.4.5 from here and then running that but I get the same error.

I then re-installed v3.4.4 with no issues whatsoever.

Please advise?

Thanks, Simon.

  • DELL-Young E

    Moderator

    •

    5421 Posts

    •

    37 Points

    0

    0

    Posted May 29th, 2024 02:57

    Hello, thanks for choosing Dell and welcome to our community.

     

    "The error message you’re seeing indicates that the Java Virtual Machine (JVM) used for the installation is in an unsecured location."

     

    I think we are seeing the answer here. According to this, could we double check on the JAVA installation path? 

     

    Respectfully,

     

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • FlippyFF

    1 Rookie

    •

    22 Posts

    •

    3 Points

    0

    1

    Posted May 30th, 2024 09:32

    I don't have Java installed as a 'stand-alone' installation, the only copies of it that exist on my machine are what DRM and other Dell apps have installed.

    It doesn't exist on my Start menu, nor in Control Panel, nor Add/Remove Programs. If I open a command prompt anywhere and try to run java.exe I just get "'java.exe' is not recognized as an internal or external command, operable program or batch file." as a response.

    I've just tried running the installer from a command prompt and got a slightly more helpful error message... 

    "D:\Repo\>DRMInstaller_3.4.5.938.exe
    company: Eclipse Adoptium

    Security Error! The JVM C:\Users\<username>\AppData\Local\Temp\I1717060817\Windows\resource\jre\bin\java.exe used for this installer seems to have been installed in a unsecured location (non-admin user folder). Installer would now exit. Please reach out to your vendor for more details."

    This temp folder "I1717060817" is created when I launch the installer.

    Simon

  • Dell-Martin S

    Moderator

    •

    3883 Posts

    •

    25810 Points

    0

    0

    Posted May 30th, 2024 13:15

    Hi,

     

    the issue you are facing with the Dell Repository Manager (DRM) 3.4.4 to 3.4.5 upgrade failing on Windows due to an "unsecure Java" error is likely caused by the Java Runtime Environment (JRE) being installed in a non-standard location or by a non-administrator user.[4]

    To resolve this issue, you can try the following steps:

    1. Uninstall the existing version of DRM (3.4.4) completely.

    2. Download the latest version of Java JRE from the official Oracle website (https://dell.to/3yNZVcG) and install it as an administrator.

    3. After installing the JRE, download the DRM 3.4.5 installer from the Dell website and run it as an administrator.

    If the issue persists, you may need to call Dell Software support for further assistance, as they may have specific instructions or workarounds for this particular issue with the DRM upgrade on Windows.[4]

    Citations:
    [1] https://dell.to/4aFXUNg
    [2] https://dell.to/3VlV1g8
    [3] https://dell.to/4aFYWZw
    [4] https://dell.to/4aBa8Xi
    [5] https://dell.to/3V1qSRU

    with kind regards Martin/ Liebe Grüße Martin

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

    DELL-Martin S

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell


  • N_An

    1 Rookie

    •

    1 Message

    •

    2 Points

    0

    2

    Posted June 11th, 2024 13:37

    I came across the same issue, thankully it was an easy fix for me.

    The PC that Dell Repository Manager was installed on was domain joined (AD), the error was happening for AD users.  I Shift and Right clicked the exe, used "Run as a different user" and chose the local PC's "Administrator" user, and the issue was no longer there, it ran and updated the install.  Hopefully this will work for others.

    (edited)

  • TerabyteNet

    1 Rookie

    •

    10 Posts

    0

    2

    Posted June 18th, 2024 18:50

    @DELL-Young E​ Maybe the real question is why does Dell continue to use Java for this?  There are far superior tools without all the overhead and security risks Java introduces.

  • MrCEwald

    1 Rookie

    •

    2 Posts

    •

    2 Points

    0

    0

    Posted August 30th, 2024 09:58

    Removed my profile and logged in again with a fresh one but got the same error complaining on unsecured location of jvm.

  • MrCEwald

    1 Rookie

    •

    2 Posts

    •

    2 Points

    0

    0

    Posted August 30th, 2024 11:53

    Did as TerabyteNet but logged on as local administrator and installation completed successfully

  • Ovesney

    1 Rookie

    •

    1 Message

    0

    0

    Posted January 24th, 2025 15:55

    Can I ask, how is it even possible, that enterprise software, in 2025, have to be installed under local administrator account? I'm not even going to start about Java. The issue is present since 3.4.5 up until now. I have to have an non domain joined VM in isolated network, just to build ISOs for Dell. Ridiculous.

  • DELL-Young E

    Moderator

    •

    5421 Posts

    •

    37 Points

    0

    0

    Posted February 18th, 2025 12:01

    Hello,

     

     From the previous reply above,

    "@DELL-Young E Maybe the real question is why does Dell continue to use Java for this?  There are far superior tools without all the overhead and security risks Java introduces."

     

    We have OME and update plugin manager for that.

    https://dell.to/4i4Zigv

     

    Based on what other members already suggested they fixed it by running with admin rights.

     

    If you are not happy with the legacy product, I think you can use OME appliance + UMP in my humble opinion.

     

    There are customers who still needs/like DRM because they simply do not like changes,

    however we do have a new alternative, the link above Dell OpenManage Enterprise Update Manager Plug-in is that.

     

    Respectfully,

    (edited)

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • TerabyteNet

    1 Rookie

    •

    10 Posts

    0

    1

    Posted February 21st, 2025 14:11

    @DELL-Young E​ The problem is DRM pulls all updates, drivers included.  OME only pulls firmware.  The latest DRM also creates a NASTY update process when it creates an SUU where, by default, it enables firmware downgrades.  Since Dell can't seem to settle on one location for its catalog, if one has updated to the latest firmware available via an iDRAC or OME then creates an SUU that will include drivers, it will often automatically check the box to downgrade firmware since even if the SUU was built using the most recent version of the catalog available to DRM it may not contain the most recent updates.  This has the real potential to damage systems or preventing them from booting as downgrading a BIOS often resets to defaults which may not be the ones required to use the system.  Dell needs ONE catalog for ALL its management tools.

    It just feels like there are too many chefs in the kitchen.  Too many tools.  Too many variations.  No coherent plan for all of them.  They need to be reigned in and put under one umbrella with one chef deciding all the behaviours.  Until then customers and MSPs will continue to have these types of issues.