I’ve helped troubleshoot this exact issue dozens of times—SQL Server 2017’s installer can be surprisingly picky about recognizing Oracle JRE installations, even if you’ve got the latest version up and running. Let’s break down why this happens and how to fix it:

Root Cause #

SQL Server 2017 components like PolyBase, Master Data Services, or Reporting Services depend specifically on Oracle’s official JRE (not OpenJDK, Adoptium, or other third-party Java distributions). The installer checks specific registry keys and path structures, which newer JRE versions might not populate in the exact format it expects. Custom installation paths can also throw off its automatic detection logic.

Step-by-Step Solutions #

1. Confirm You’re Using Oracle JRE (Not Alternatives) #

First, double-check that you installed the 64-bit Oracle JRE—SQL Server’s installer won’t recognize OpenJDK or other Java variants. If you installed the wrong one, uninstall it and grab the latest 64-bit Oracle JRE (JRE 8 is a safe choice here, since JRE 7 is end-of-life but still compatible with the installer’s check).

2. Manually Specify the JRE Path #

If the installer still doesn’t pick up your JRE, force it to use the correct path via command line:

• Locate the setup.exe file in your SQL Server 2017 installation media (or extracted ISO folder).
• Open an elevated Command Prompt (Run as Administrator) and navigate to that folder.
• Run this command, replacing C:\Program Files\Java\jre1.8.0_391 with your actual JRE installation path:

  setup.exe /ACTION=INSTALL /JAVAJRELOCATION="C:\Program Files\Java\jre1.8.0_391"
  

This bypasses the installer’s automatic detection and tells it exactly where to find the required JRE.

3. Fix Missing/Corrupted Registry Keys #

Sometimes the JRE installer fails to populate the registry entries SQL Server looks for. Here’s how to check and fix them:

• Open Registry Editor by running regedit as Administrator.
• Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment (this is for 64-bit JRE on 64-bit Windows).
• Ensure there’s a subkey for your installed JRE version (e.g., 1.8 or 17), and the JavaHome string value points directly to your JRE’s root folder (like C:\Program Files\Java\jre1.8.0_391).
• If you accidentally installed a 32-bit JRE on 64-bit Windows, check HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment—but note that 64-bit SQL Server requires a 64-bit JRE, so you’ll want to switch to the correct architecture instead.

4. Repair or Reinstall the JRE #

If the registry looks correct but detection still fails:

• Uninstall the current Oracle JRE via Programs and Features.
• Download the latest 64-bit Oracle JRE again, run the installer, and choose the default installation path (avoid custom folders). This ensures the installer sets up all required registry entries and path variables correctly.

5. Skip the Rule (Last Resort) #

Only use this if you’re certain you don’t need JRE-dependent components like PolyBase:

• Run the installer with the skip rule flag:

  setup.exe /ACTION=INSTALL /SKIPRULES=JavaRuntimeFrameworkCheck
  

⚠️ Warning: Skipping this rule can break functionality for components that rely on JRE, so use this only as a temporary fix.

内容的提问来源于stack exchange，提问作者Tharindu Madushanka