求助：部分Windows设备启动应用时提示无法找到jvm.dll库

I’ve run into nearly identical issues with Java-based apps on older Windows 10 builds, so let’s break down the troubleshooting steps and fixes that worked for me—especially since you’ve already tried targeting the JDK-8191176 bug without luck:

1. Verify DLL Loading Path Priority #

Windows uses a specific search order for DLLs, and even if jvm.dll exists in your expected directory, it might be getting overlooked:

• Double-check your app’s startup script or configuration to ensure JAVA_HOME or PATH explicitly points to the JRE directory containing jvm.dll (typically C:\Program Files\Java\jre1.8.0_xxx\bin\server for 64-bit systems)
• Temporarily move the bin\server directory to the top of your system PATH to eliminate conflicts with other potentially mislocated DLLs
• Use Process Monitor (a Sysinternals tool) to trace your app’s DLL loading behavior—this will show exactly which paths Windows checks for jvm.dll, and if there are permission or path typos causing failures

2. Test a More Compatible JDK/JRE Build #

Windows 10 1703 and 1709 are legacy builds, and some mid-cycle JDK 8u versions have subtle compatibility gaps. Even though you tried 8u162 and 8u172 preview:

• Switch to JDK 8u202—it’s a stable release with better backported fixes for older Windows 10 builds, and I’ve seen it resolve this exact error in similar cases
• If your app bundles a JRE, confirm it’s a 64-bit build (matching your x64 devices) — 32-bit JREs store jvm.dll in bin\client instead of bin\server, which can break path references

3. Rule Out Permission & UAC Issues #

UAC and restricted system directory permissions can block DLL access even when the file exists:

• Right-click your app’s executable and select Run as administrator to test if elevated permissions fix the problem
• Check the permissions on the directory containing jvm.dll—ensure the current user has Read & Execute access
• Try installing the app to a non-system drive (like D:) to avoid strict system folder restrictions

4. Dig Deeper on JDK-8191176 Edge Cases #

The JDK-8191176 bug can trigger under specific conditions that might not be fixed by just upgrading the JDK:

• Confirm your app isn’t modifying the PATH environment variable at startup, which could overwrite or break the JRE path reference
• If you’re using JNI to initialize the JVM, check for hardcoded path errors (especially spaces in paths like Program Files) or incorrect architecture targeting

5. Repair System-Level Corruption #

Older Windows 10 builds sometimes have system file corruption that disrupts DLL loading:

• Open an elevated Command Prompt and run:

  sfc /scannow
  

• If that doesn’t resolve it, run the DISM repair command:

  DISM /Online /Cleanup-Image /RestoreHealth
  

内容的提问来源于stack exchange，提问作者Pablo Fernandez