JDK 11 removed the Java Plug-in, Java Web Start, the Java Control Panel and Java Auto Update, so the deployment log folders and `jusched.log` apply to Java 8 and earlier. `hs_err_pid` crash logs apply to every HotSpot JVM.
Where Java keeps its logs
Java logs to %TEMP%\jreMSI.log on Windows. 6 other Windows log locations are recorded below.
Java logs to /var/log/install.log on macOS. 1 other macOS log location is recorded below.
Java logs to ~/.java/deployment/log/ on Linux. 1 other Linux log location is recorded below.
Paths are printed exactly as Java writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.
Java Update Scheduler log%TEMP%\jusched.log- Java 8 and earlier only; JDK 11 removed the deployment stack.
Plug-in, Web Start and Control Panel trace and log files%USERPROFILE%\AppData\LocalLow\Sun\Java\Deployment\log\- Java 8 and earlier only; JDK 11 removed the deployment stack.
JVM fatal error log%TMP%\hs_err_pid<pid>.log- Written to the process working directory first; %TMP% (else %TEMP%) only when that fails
Installer log/var/log/install.log- Shared macOS log; take only the Java installer entries
Plug-in, Web Start and Control Panel trace and log files~/Library/Application Support/Oracle/Java/Deployment/log/- Java 8 and earlier only; JDK 11 removed the deployment stack.