Select a version
The current version is displayed by default, but you can seelect from the list below to view changes in earlier versions:
5.71, 5.70, 5.61, 5.60, 5.50, 5.40, 5.31, 5.30, 5.21, 5.20, 5.11, 5.10, 5.01, 5.00, 4.20, 4.11, 4.10, 4.01, 4.00, 3.93, 3.92, 3.91, 3.90, 3.80, 3.71, 3.70, 3.62, 3.61, 3.60, 3.51, 3.50, 3.42, 3.41, 3.40, 3.30, 3.20, 3.11, 3.10, 3.00
Changes in version 5.10
|1.||Added extraction support for ZIP and ZIPX archives using BZIP2, LZMA and PPMd compression.|
|2.||Added extraction support for 7z split archives (.7z.001, .7z.002, ...)|
|3.||Added support for AES-NI CPU instructions allowing to improve RAR encryption and decryption performance|
|4.||Environment variables can be used in "Files to add" field of archiving dialog|
|5.||Default theme images are scaled up with better quality in high DPI display mode|
|6.||Switch -ai can be used when creating RAR archive, so predefined values, typical for file and folder, are stored instead of actual attributes.
Previously this switch could be used only when extracting.
|7.||More efficient implementation of "Keep broken files" extraction option (-kb switch in command line mode). Now it allows to recover more data from file split between RAR volumes if next volume is missing.|
a) "Create recovery volumes" command on "Options" page of archive information dialog was inaccessible if "Merge volume contents" option was enabled in WinRAR settings;
b) if wrong password was entered for RAR archive with encrypted file names, previous beta applied such wrong password automatically, when opening the same archive again.
c) when processing nested archives, WinRAR could attempt to open inner archive as self-extracting instead of opening an outer archive. It happened if inner archive was stored without compression and outer archive name had non-standard extension;
d) Unix RAR could not decompress hard links stored by WinRAR if link source name included path separator characters.
e) beta 3 failed to decompress multivolume encrypted RAR archives;
f) "Update" command ("u" in command line mode) could update even files with same modification time;
g) under rare conditions x86 version working in multithreaded mode on SSE2 enabled CPU could erroneously issue checksum error message for first file in valid RAR5 archive with BLAKE2sp checksums.