Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesjsound.dll is a Java native library used by Java Sound on Windows. If jsound.dll is missing or cannot be loaded, repair the Java application or bundled Java runtime that owns it rather than downloading a replacement DLL.
The file is not a Windows system component. It historically ships with Oracle or Sun Java Runtime Environment and JDK installations, and may also be inside a program’s private Java runtime. The correct repair depends on the application, Java version, and whether the program is 32-bit or 64-bit.
Identify the jsound.dll copy
| What to check | What it tells you |
|---|---|
jsound.dll location |
Which Java installation or application owns the file |
| Application architecture | Whether the program needs 32-bit or 64-bit Java |
| Java distribution | Whether the program uses Oracle Java, OpenJDK, or a bundled JRE |
| File signature | Whether the file came from a legitimate installation |
| Error timing | Whether an uninstall, update, quarantine, or file move caused the problem |
Common legitimate locations include:
C:Program FilesJavajre...binjsound.dll
C:Program Files (x86)Javajre...binjsound.dll
An older application may instead contain a path similar to:
C:Program FilesExampleAppjrebinjsound.dll
C:Program Files (x86)ExampleAppjrebinjsound.dll
The exact version, size, path, and metadata vary by Java release and application packaging. Modern Java distributions may not expose the file in exactly the same way as older Java 6, 7, or 8 installations.
Check the application first
Before changing Java globally, note the name of the program showing the error.
- Right-click the program’s shortcut and select Properties.
- Open the Shortcut tab.
- Check Target and Start in for a Java path,
jrefolder, launcher, or application directory. - Open the program’s installation folder.
- Look for
jre,runtime,java,bin, or a launcher folder. - Search that application folder for
jsound.dll.
If the file exists under the application’s own jrebin directory, that program probably does not use the Java installation listed in Windows settings. Repair or reinstall the application instead of copying a system Java DLL into its folder.
Check the file’s path and signature
If Windows can find a copy of the file:
- Press Windows key, type
jsound.dll, and select Open file location if offered. - Right-click the file and select Properties.
- Review the General tab for its location.
- Open Details and review the product and file description.
- Open Digital Signatures, if present.
- Select the signature and choose Details.
- Confirm that Windows reports the signature as valid and that the file is located inside the expected Java or application directory.
A copy in a temporary folder, Downloads, or an unrelated user-profile directory deserves extra scrutiny. Do not assume that every file with this name is safe.
What the error means
You may see wording such as:
The program can't start because jsound.dll is missing from your computer.
or:
jsound.dll was not found.
Other messages can include:
Error loading jsound.dll.
The procedure entry point could not be located in jsound.dll.
jsound.dll is either not designed to run on Windows or it contains an error.
The precise wording depends on Windows, the Java launcher, and the application. A missing-file message usually means the runtime is incomplete, the program is looking in the wrong directory, or security software removed the file.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11An entry-point or “not designed to run on Windows” message more often indicates a wrong-architecture file, corruption, an incompatible Java build, incomplete extraction, or a tampered binary.
Fix 1: Repair or reinstall the affected application
This is the safest first repair when only one program reports the error.
- Close the affected program.
- Press Windows key + I to open Settings.
- Select Apps and then Installed apps.
- Find the affected application.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair and wait for Windows to finish.
- Start the application again.
If Repair is not available or does not help:
- Return to Installed apps.
- Select the application’s three-dot menu.
- Choose Uninstall.
- Restart Windows.
- Download the complete installer from the application’s developer or vendor.
- Install it to its normal location.
- Start the program and test the operation that previously failed.
Some older applications provide their own Repair, Verify files, or Repair installation option in the Start menu or launcher. Use that option when available. It can restore the application’s private JRE and its matching Java libraries together.
Rank #2
If reinstalling reveals a different missing DLL, the Java runtime is likely still incomplete or mismatched. Continue with the Java checks below rather than replacing DLLs individually.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix 2: Restore the matching Java runtime
Use this step when the program depends on system Java or the vendor specifically instructs you to install Java.
- Open Settings with Windows key + I.
- Select Apps and Installed apps.
- Search for Java, JDK, OpenJDK, or a vendor-specific runtime.
- Note whether the installed runtime is 32-bit or 64-bit where Windows displays that information.
- Check the application’s documentation or installer requirements for its supported Java major version.
- Download the required runtime from Oracle’s official Java download or archive pages, or from the application vendor’s official support channel.
- Choose the architecture required by the application.
- Close all Java applications.
- Install the runtime.
- Restart Windows and test the affected program.
Do not assume that the newest JDK will repair an older application. Java 6, 7, and 8-era programs may require a particular runtime or may have been tested only with a bundled JRE. If the vendor supplied Java with the application, use that installer first.
A 32-bit application needs a 32-bit Java runtime even on 64-bit Windows. A 64-bit Java installation does not generally satisfy a 32-bit Java application. If your office software includes both older 32-bit programs and newer 64-bit programs, separate Java installations may be necessary.
Fix 3: Repair a damaged private JRE
A bundled runtime can be damaged when someone deletes application files, moves the program folder, runs disk cleanup, or interrupts an update.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Open File Explorer.
- Browse to the application’s installation directory.
- Look for
jre,runtime, or a similar private Java folder. - Confirm whether
jsound.dllshould be under that folder’sbindirectory. - Do not copy a DLL from another Java installation into it.
- Run the application’s original installer.
- Select Repair, if offered.
- If repair is unavailable, uninstall the application and reinstall it from the complete official installer.
- If the program has a launcher with Verify or Repair files, run that process.
- Start the program again.
This approach restores related Java files with compatible versions and dependencies. A manually copied jsound.dll can leave the runtime internally mismatched.
Fix 4: Check antivirus quarantine
Security software can quarantine a damaged, modified, or incorrectly identified Java file.
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Choose Protection history.
- Look for an entry involving
jsound.dll, Java, or the affected application. - Check the file path shown in the alert.
- Restore the file only if the path belongs to the legitimate application or Java installation and you trust its source.
- Do not restore a copy from a temporary folder, download directory, or unknown program.
- Repair or reinstall the complete Java runtime after restoring the file.
- Run Virus & threat protection and select Scan options.
- Run a Full scan.
If the file has an unexpected path or an invalid signature, leave it quarantined and perform a full scan. Reinstall the application from its official installer rather than restoring the suspicious binary.
Fix 5: Check Windows DLL loading and dependencies
A file can exist but still fail to load. Windows searches application and system locations in a defined order, so the application may be loading another copy or may be unable to find a dependent library.
- Open the application’s installation folder.
- Check its own
binorjrebindirectory first. - Check the Java installation directory used by the application.
- Do not place
jsound.dllinC:WindowsSystem32orC:WindowsSysWOW64. - Remove only an obviously misplaced duplicate if you know which program installed it and have a backup.
- Restart the application.
If the file exists in System32 but the program still fails, it is probably not the copy the application needs. The application’s directory and its private runtime take priority in many launch scenarios.
An error naming another DLL after Java is reinstalled is evidence of a broader incomplete runtime. Repair the application or reinstall its complete Java package.
Fix 6: Check architecture and compatibility
Wrong architecture is a common cause of loader errors.
- Open Settings.
- Select System and then About.
- Note the Windows System type.
- Open Task Manager with Ctrl + Shift + Esc.
- Select the Details tab.
- Right-click a column heading and choose Select columns.
- Enable Platform, where available.
- Identify whether the running application is 32-bit or 64-bit.
- Install the matching Java architecture.
- Re-run the application.
The process architecture must match the Java runtime and native libraries it loads. If the application is too old to document its architecture, reinstalling the vendor-supplied runtime is safer than guessing.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Fix 7: Update drivers only when Java Sound is affected broadly
jsound.dll belongs to Java Sound, so audio driver problems can become relevant when multiple Java applications fail during playback or recording. A driver update will not normally restore a missing Java file.
Rank #4
- Right-click the Start button and select Device Manager.
- Expand Sound, video and game controllers.
- Right-click the audio device.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart Windows if a driver is installed.
- Test the affected application.
If Windows finds nothing, obtain the driver from the computer or sound-device manufacturer. Do not change drivers merely because one application has a missing jsound.dll.
Outbyte Driver Updater can reduce the manual work of hunting through several hardware pages: its free scan identifies outdated drivers, while the full version performs the driver installation. It is optional, and reinstalling the Java application remains the definitive fix for an application-owned jsound.dll.
Fix 8: Repair Windows components only when other symptoms exist
SFC and DISM normally repair Windows components, not Java-owned files. Use them when several unrelated Windows features are failing, system files are damaged, or Windows updates and other applications show corruption.
- Open Start and type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Select Yes at the User Account Control prompt.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Then run:
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Test the application again.
Microsoft recommends running DISM before SFC. If SFC reports that it found no integrity violations, Windows itself is less likely to be the cause. Return to repairing the Java application or matching runtime.
If repeating these commands is becoming guesswork, Outbyte PC Repair can provide a scan that shows what it detects; its full version performs the repair. It is optional, and it does not replace reinstalling the application that owns jsound.dll.
What not to do
Do not download jsound.dll from a DLL website
An isolated DLL may contain malware, belong to the wrong Java update, use the wrong architecture, or require other missing files. It also does not repair a damaged private JRE or a broken application installation.
Use the application vendor’s complete installer or the official Java distribution required by that application. Do not publish or rely on a universal hash, size, or “latest” version because no single copy applies to every Java release.
Recommended Free Tools
Do not register it with regsvr32
regsvr32 is for DLLs that expose registration entry points such as DllRegisterServer. jsound.dll is a Java native runtime library loaded by the JVM, not a COM or ActiveX component.
Running this command is not a valid general repair:
Best Value
regsvr32 jsound.dll
It may produce an entry-point error and does not install the Java runtime that the application needs.
Do not copy a file from another computer
Two computers may have different Java architectures, update levels, dependencies, signatures, or application layouts. Copying the file can replace one error with an incompatible-binary error.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →When to use System Restore
Use System Restore only when the failure clearly began after a recent software or system change and application repair is unavailable.
- Open Start and search for Create a restore point.
- Open the matching Control Panel result.
- Select System Restore.
- Choose a restore point created before the error began.
- Review the affected programs.
- Select Next, then Finish.
- Allow Windows to restart and complete the process.
System Restore is a fallback, not a file-specific method for restoring a Java library.
FAQ
Is jsound.dll part of Windows?
No. It is associated with Java Sound and normally belongs to a Java runtime or an application that bundles one.
Should I install Java 8?
Only if the affected application requires it or was built and tested for it. Use the application vendor’s supported runtime where possible, and match 32-bit or 64-bit architecture.
Why does the file exist but Windows still say it is missing?
The application may be loading a different copy, the file may be in the wrong directory, a dependency may be missing, or the binary may not match the process architecture.
Can SFC restore jsound.dll?
Normally no. SFC repairs protected Windows components. A Java-owned file should generally be restored by repairing or reinstalling Java or the application that supplied it.
What if several applications report Java errors?
Check whether they share a Java installation, security-software event, PATH change, or damaged runtime. Reinstall the common runtime using the correct architecture and supported Java version.
When should I suspect malware?
Treat the file as suspicious when it is in a temporary or random profile directory, has an invalid signature, appeared without a legitimate installation, or is repeatedly replaced by security software. Quarantine it, scan the system, and reinstall the application from its official source.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
