WinRAR Keygen
Principle of WinRAR key generation
1. What is WinRAR?
WinRAR is a trialware file archiver utility for Windows, developed by Eugene Roshal of win.rar GmbH.
It can create and view archives in RAR or ZIP file formats and unpack numerous archive file formats.
WinRAR is not a free software. If you want to use it, you should pay to RARLAB and then you will get a license file named rarreg.key.
This repository will tell you how WinRAR license file "rarreg.key" is generated.
2. How is "rarreg.key" generated?
See here.
3. How to use?
There are several ways to use it.
3.1 Encoding
WinRAR Keygen supports ASCII, ANSI and UTF-8 encoding types, the corresponding supported characters are listed in the table below.
[!NOTE] The default is
utf8, but you can specify the encoding asasciioransi.
| Encoding | Supported Characters | Character Examples |
|---|---|---|
| ascii | Only full ASCII characters are supported. |   |
| ansi | There is no one fixed ANSI code, usually Windows-1252, but other local codes are also possible. |   |
| utf8 | Support full UTF-8 encoded characters. | ASCII characters, English, 简体中文, 繁體中文, Deutsch, Français, Русский, Italiano, 日本語, 한국어, Lengua española, Ελληνική γλώσσα, et al. |
3.2 License type
There are two types of WinRAR licenses, rarreg.key and rarkey.rar, which differ only in their import.
| rarreg.key | rarkey.rar |
|---|---|
 |
 |
| Drag to import or place in a location | Double-click to run automatic import |
If you are unable to drag, you can try to put the rarreg.key in the following directory.
C:\Users\yourname\AppData\Roaming\WinRAR\rarreg.keyYou can also compress rarreg.key into rarkey.rar and double-click it to run it, and the license import will take place automatically.
4. Use Github Actions
Click to expand
The new workflow can easily help you generate a license, you just need to follow these steps. > Your `Username` and `License Name` will appear in the actions log, if you don't want to give out this information, see [5. Using Github Actions with secrets](#5-Use-Github-Actions-with-secrets). ### 4.1 Fork **Fork** this repo.   ### 4.2 Allow fork repo to run workflows Go back to the repo you just forked and click **Actions** to allow Workflows to run in your forked repo.   ### 4.3 Run workflow After allowing the workflow, go to **Actions > WinRAR Keygen > Run workflow** and fill in the information to start generating. > For the difference of license encoding, please refer to [3.1 Encoding](#31-Encoding).   After running successfully, open the corresponding task and select **rarreg_file** to download. > File retention 90 days.   Extract rarreg_file.zip to get `rarreg.key` and drag to import into WinRAR. You can also compress `rarreg.key` into `rarkey.rar`, then double-click it to run it, and the license import will be done automatically. If you get an invalid key, please check [the specific solution](#7-invalid-key).5. Use Github Actions with secrets
Click to expand
Using [secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) can help you hide license information. ### 5.1 Fork **Fork** this repo.   ### 5.2 Allow fork repo to run workflows Go back to the repo you just forked and click **Actions** to allow Workflows to run in your forked repo.   ### 5.3 Create secrets After allowing the workflow, go to **Settings > Secrets and variables > Actions > New repository secret** to create a secret.   Create three secrets with the names `TEXT1`, `TEXT2` and `PWD` and fill in the relevant values. > The value filled in should be consistent with the type of code you have chosen. | Secrets Name6. Build in Visual Studio
Click to expand
I recommend using the Github Actions, but you can still do your own compilation. If you don't want to compile it yourself, you can also go to the [release](https://github.com/bitcookies/winrar-keygen/releases/) page to get `winrar-keygen.exe`. ### 6.1 Prerequisites 1. Please make sure that you have **Visual Studio 2022**. Because this is a VS2022 project. If you are still using Visual Studio 2019, you can find projects for VS2019 in the [vs2019](https://github.com/bitcookies/winrar-keygen/tree/vs2019) branch, but this branch will no longer be maintained. 2. Please make sure you have installed `vcpkg` and the following libraries: * `mpir:x86-windows-static` * `mpir:x64-windows-static` is installed. You can install them by: ```shell $ vcpkg install mpir:x86-windows-static $ vcpkg install mpir:x64-windows-static ``` 3. Your `vcpkg` has been integrated into your __Visual Studio__, which means you have run successfully. ```shell $ vcpkg integrate install ``` ### 6.2 Build 1. Open this project in __Visual Studio__. 2. Select `Release` configuration. 3. Select __Build > Build Solution__. You will see executable files in `bin/` directory. ### 6.3 How to use? Execute the following code in the terminal and configure two parameters to generate `rarreg.key`. Here is an example of ASCII encoding for `Github` and `Single PC usage license`: ```shell Usage: winrar-keygen.exe7. Invalid key
Why is my rarreg.key invalid?
7.1 Character encoding
TEXT1 and TEXT2 are required to fulfill corresponding coding requirements.
winrar-keygen.exe <TEXT1> <TEXT2>You can refer to: Generation of "rarreg.key"
7.2 Text encoding
If you use the following command:
winrar-keygen.exe "Github" "Single PC usage license" > rarreg.keyIn the newer Windows 10, PowerShell will export in UTF16-LE format by default, which will cause the error.
Please use the following command:
winrar-keygen.exe "Github" "Github.com" | Out-File -Encoding ascii rarreg.key
winrar-keygen.exe "Github" "Github.com" | Out-File -Encoding ansi rarreg.key
winrar-keygen.exe "utf8:Github" "Github.com" | Out-File -Encoding utf8 rarreg.key8. Contributing
8.1 Suggestion
If you encounter some problems, you can report on the Issues page. There will be many enthusiastic developers or Github users to help you.
This project welcomes contributions and suggestions. You can make suggestions in Issues, or submit a pull request 😄
8.2 Thanks
Thank you very much to some enthusiastic developers for helping answer some questions in Issues.
🏆 Special Thanks @Sonic-The-Hedgehog-LNK1123
9. License
The code is available under the MIT license