這是歷史版本頁面 — 看 Java Runtime Environment (32-bit) 最新版本

Java Runtime Environment 是做什麼的?為什麼有些軟體一定要裝它

Java Runtime Environment (32-bit) 軟體圖示 Java Runtime Environment (32-bit) 141 (32-bit) 資料更新 2017-07-19 閱讀約 6 分鐘

打開某個老遊戲、公司內部系統、或是某個下載來的程式,畫面跳出一串「需要 Java」的提示,但你根本不知道那是什麼。裝了怕佔空間,不裝又跑不動,卡在「到底要不要裝」的猶豫裡。這種情況通常發生在你想開一個特定程式或網站,卻被一個沒聽過的執行環境擋在門外。

一般人遇到這種提示,直覺是上網找「Java 下載」,裝完發現問題解決了,但過一陣子又跳出「需要更新」,然後開始擔心是不是裝到病毒。這類執行環境工具的本質,是提供一個讓 Java 程式能跑的底層平台——它不是應用程式本身,而是程式賴以運作的基礎設施。理解它負責什麼、什麼時候需要、什麼時候可以不理它,比盲目安裝或刪除都更重要。

01Java Runtime Environment 是做什麼的?為什麼有些軟體一定要裝它?

它提供 Java 程式執行時需要的虛擬機器、核心函式庫和相關元件。很多網站、遊戲和企業內部系統是用 Java 寫的,這些程式在執行時會呼叫 Java 的函式庫,沒有這套環境就無法啟動。你可以把它想成程式的「翻譯官」,負責把 Java 寫好的指令轉換成你的電腦能理解的動作。官方說明指出,許多跨平台應用程式都需要 Java 才能正常運作。

02它跟 Java Development Kit 有什麼不同?

這套軟體是「執行環境」,只負責讓 Java 程式跑起來,不包含編譯器或除錯器等開發工具。如果你只是要使用別人寫好的 Java 程式,裝這個就夠了。但如果你要自己寫 Java 程式、編譯原始碼,就需要另外安裝 Java Development Kit(JDK),它內含完整的開發工具,也包含這套執行環境。官方文件明確說明 JRE 不包含開發工具。

03裝了它之後,哪些東西可以跑起來?

主要能跑三類東西:網頁瀏覽器裡的 Java 小程式(applet)、透過 Java Web Start 啟動的獨立應用程式,以及一般 Java 應用程式。官方說明提到,Java Plug-in 讓小程式能在瀏覽器中執行,Web Start 則能從網路部署獨立程式。此外,很多跨平台應用程式也需要它才能運作。實際能跑什麼,取決於你手上的程式是用 Java 寫的,而且版本要相容。

04它會自己更新嗎?還是要手動裝新版?

官方說明建議升級到最新版本,因為新版包含效能、穩定性和安全性的增強。但這套軟體本身不會自動更新,你需要自行到官方網站下載新版安裝。從版本紀錄來看,它持續有更新,近一年內有多次新版本釋出。如果你長期使用舊版,可能會有安全風險,建議定期檢查是否有新版本。

05瀏覽器現在還需要它嗎?

現代主流瀏覽器大多已停止支援 Java Plug-in,官方說明中提到的「在瀏覽器中執行小程式」功能,在目前的瀏覽器環境下已經很少能派上用場。不過,Java Web Start 技術仍可用來啟動獨立應用程式。如果你只是為了開瀏覽器裡的 Java 內容,可能要確認你的瀏覽器是否還支援;如果是為了跑桌面應用程式,那它仍然有用。

06我只是想玩某個老遊戲,需要裝它嗎?

如果那個老遊戲是用 Java 寫的,就需要。很多早期網頁遊戲和單機小遊戲是用 Java 開發的,沒有這套環境就無法啟動。你可以先確認遊戲的系統需求或說明文件,看是否提到需要 Java。要注意的是,老遊戲可能需要特定版本的 Java,裝了最新版不一定能跑,可能需要找舊版來搭配。

07我是寫程式的,裝這個夠用嗎?

不夠。這套軟體只提供執行環境,沒有編譯器、除錯器這些開發工具。官方文件明確指出,要進行 Java 開發,需要的是 Java Development Kit(JDK),它包含 JRE 以及編譯、除錯、打包應用程式的額外工具。如果你只是要執行別人寫好的 Java 程式,裝這個可以;但如果你要自己寫程式,請改裝 JDK。

08公司內部系統一直叫我裝 Java,這是正常的嗎?

正常。官方說明提到,Java 是企業內部應用程式和電子商務解決方案的基礎,很多公司內部系統是用 Java 開發的。如果你的公司系統要求安裝,通常是因為那些系統的後端或前端元件需要 Java 才能運作。建議依照公司 IT 部門的指示安裝,並確認版本是否符合系統需求。

09我的電腦是 Windows 11,可以裝嗎?

官方支援清單只列到 Windows 7、Windows 8 和 Windows 10,沒有提到 Windows 11。這不代表它一定不能裝,但官方沒有保證相容性。如果你用的是 Windows 11,建議先到官方網站確認是否有對應的版本,或直接安裝試試看,但要有心理準備可能遇到相容性問題。

10它只有英文介面,看不懂怎麼辦?

這套軟體的介面是英文,但安裝過程和日常使用其實不太需要看介面——它安裝完之後多半在背景執行,你不太會直接跟它的介面互動。真正需要英文的地方是安裝精靈的按鈕,通常就是「Next」「Agree」這類基本單字。如果你完全不熟悉英文,可以找網路上安裝教學文,照著步驟點即可。

11網路上有人說 Java 有安全問題,還該裝嗎?

官方說明強調這套軟體具備安全功能,包括安全管理器、沙箱環境、數位簽章和加密機制,用來防範惡意行為。但任何軟體都有潛在風險,重點是保持更新——官方建議安裝最新版本以獲得安全性增強。如果你不需要跑 Java 程式,不裝也無妨;如果需要,請從官方網站下載,並定期更新。

12我已經有 .NET Framework 了,還需要它嗎?

需要。.NET Framework 和 Java Runtime Environment 是兩套完全不同的執行環境,各自負責不同程式語言寫成的應用程式。.NET Framework 是給 .NET 程式用的,Java 程式無法靠它執行。如果你要跑的程式是用 Java 寫的,就算裝了 .NET Framework 也沒用,還是需要這套軟體。兩者可以並存,不會互相干擾。

下載與官方連結

前往官方網站 下載 Java Runtime Environment (32-bit)

jre-8u141-windows-i586.exe · 54.56 MB · 連結指向軟體原廠

版本紀錄

再看 5 筆

看完整版本清單

這一版改了什麼

What's new in this version:

IANA DATA 2017b:
- JDK 8u141 contains IANA time zone data version 2017b

CERTIFICATE CHANGES:
- Let's Encrypt certificates added to root CAs. One new root certificate has been added

NEW FEATURES:
security-libs/java.security. Improved algorithm constraints checking:
- With the need to restrict weak algorithms usage in situations where they are most vulnerable, additional features have been added when configuring the jdk.certpath.disabledAlgorithms and jdk.jar.disabledAlgorithms security properties in the java.security file.
- jdk.certpath.disabledAlgorithms: The certpath property has seen the most change. Previously it was limited to two Constraint types; either a full disabling of an algorithm by name or a full disabling of an algorithm by the key size when checking certificates, certificate chains, and certificate signatures. This creates configurations that are absolute and lack flexibility in their usage. Three new Constraints were added to give more flexibility in allowing and rejecting certificates.
- "jdkCA" examines the certificate chain termination with regard to the cacerts file. In the case of "SHA1 jdkCA". SHA1's usage is checked through the certificate chain, but the chain must terminate at a marked trust anchor in the cacerts keystore to be rejected. This is useful for organizations that have their own private CA that trust using SHA1 with their trust anchor, but want to block certificate chains anchored by a public CA from using SHA1.
- "denyAfter" checks if the given date is before the current date or the PKIXParameter date. In the case of "SHA1 denyAfter 2018-01-01", before 2018 a certificate with SHA1 can be used, but after that date, the certificate is rejected. This can be used for a policy across an organization that is phasing out an algorithm with a drop-dead date. For signed JAR files, the date is compared against the TSA timestamp. The date is specified in GMT.

"usage" examines the specified algorithm for a specified usage. This can be used when disabling an algorithm for all usages is not practical. There are three usages that can be specified:
- TLSServer' restricts the algorithm in TLS server certificate chains when server authentication is performed as a client
- TLSClient' restricts the algorithm in TLS client certificate chains when client authentication is performed as a server
- SignedJAR' restricts the algorithms in certificates in signed JAR files. The usage type follows the keyword and more than one usage type can be specified with a whitespace delimiter
- For example, "SHA1 usage TLSServer TLSClient" would disallow SHA1 certificates for TLSServer and TLSClient operations, but SignedJars would be allowed
- All of these constraints can be combined to constrain an algorithm when delimited by '&'. For example, to disable SHA1 certificate chains that terminate at marked trust anchors only for TLSServer operations, the constraint would be "SHA1 jdkCA & usage TLSServer"
- jdk.jar.disabledAlgorithms: One additional constraint was added to this .jar property to restrict JAR manifest algorithms
- "denyAfter" checks algorithm constraints on manifest digest algorithms inside a signed JAR file. The date given in the constraint is compared against the TSA timestamp on the signed JAR file. If there is no timestamp or the timestamp is on or after the specified date, the signed JAR file is treated as unsigned. If the timestamp is before the specified date, the .jar will operate as a signed JAR file. The syntax for restricting SHA1 in JAR files signed after January 1st 2018 is: "SHA1 denyAfter 2018-01-01". The syntax is the same as that for the certpath property, however certificate checking will not be performed by this property

CHANGES:
core-svc/java.lang.management. JMX Diagnostic improvements:
- com.sun.management.HotSpotDiagnostic::dumpHeap API is modified to throw IllegalArgumentException if the supplied file name does not end with “.hprof” suffix. Existing applications which do not provide a file name ending with the “.hprof” extension will fail with IllegalArgumentException. In that case, applications can either choose to handle the exception or restore old behavior by setting system property 'jdk.management.heapdump.allowAnyFileSuffix' to true.

security-libs/javax.net.ssl. Custom HostnameVerifier enables SNI extension:
- Earlier releases of JDK 8 Updates didn't always send the Server Name Indication (SNI) extension in the TLS ClientHello phase if a custom hostname verifier was used. This verifier is set via the setHostnameVerifier(HostnameVerifier v) method in HttpsURLConnection. The fix ensures the Server Name is now sent in the ClientHello body.

xml/jax-ws. Tighter secure checks on processing WSDL files by wsimport tool:

The wsimport tool has been changed to disallow DTDs in Web Service descriptions, specifically:
- DOCTYPE declaration is disallowed in documents
- External general entities are not included by default
- External parameter entities are not included by default
- External DTDs are completely ignored

To restore the previous behavior:
- Set the System property com.sun.xml.internal.ws.disableXmlSecurity to true
- Use the wsimport tool command line option –disableXmlSecurity
- NOTE: JDK 7 and JDK 6 support for this option in wsimport will be provided via a Patch release post July CPU

BUG FIXES:
- JFileChooser with Windows look and feel crashes on win 10
- Race Condition in java.lang.reflect.WeakCache
- java.nio.Bits.unaligned() doesn't return true on ppc
- After updating to Java8u131, the bind to rmiregistry is rejected by registryFilter even though registryFilter is set
- sun.management.LazyCompositeData.isTypeMatched() fail for composite types with items of ArrayType
- SafePointNode::_replaced_nodes breaks with irreducible loops
- NPE when JavaFX loads default stylesheet or font families if CCL is null
- WebEngine.getDocument().getDocumentURI() no longer returns null for loading a String of HTML
- Failed to load RSA private key from pkcs12
- Improved algorithm constraints checking
- Custom HostnameVerifier disables SNI extension