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.

Fork this repo.

Go back to the repo you just forked and click Actions to allow Workflows to run in your forked repo.

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.

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.

Using secrets can help you hide license information.

Fork this repo.

Go back to the repo you just forked and click Actions to allow Workflows to run in your forked repo.

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 Name	Explanation
TEXT1	Your Name
TEXT2	Your License Name
PWD	7-Zip Password

Once created, you will see it.

Go to Actions and select WinRAR Keygen with secrets to run workflow manually.

For the difference of license encoding, please refer to 3.1 Encoding.

After running successfully, open the corresponding task and select rarreg_file to download.

File retained for 1 day only.

Extract rarreg_file.zip to get rarreg.7z, unzip it with the password to get rarreg.key, then drag and drop 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.

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 page to get winrar-keygen.exe.

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 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:

   $ 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.

   $ vcpkg integrate install

1. Open this project in Visual Studio.

2. Select Release configuration.

3. Select Build > Build Solution.

You will see executable files in bin/ directory.

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:

Usage:
        winrar-keygen.exe <Username> <License Name>

Example:

        winrar-keygen.exe "Github" "Single PC usage license"

  or:
        winrar-keygen.exe "Github" "Github.com" | Out-File -Encoding ASCII rarreg.key

Now you can see the newly generated file.

RAR registration data
Github
Single PC usage license
UID=3a3d02329a32b63da7d8
6412212250a7d8753c5e7037d83011171578c57042fa30c506caae
9954e4853d415ec594e46017cb3db740bc4b32e47aea25db62f350
9f22065a27da4f8216d2938e1050b6e3347501a3767d1fdd7ee130
dd4ab952600ba16a99236d910bfa995d5f60651ec451f462511507
95b3722d059f2d5303a231e396cf21f17098edeec0b6e3347501a3
767d1fdd7ee45388769767642338ee8a63178f3458b71de5609b18
5eede7ed46566b10bf033daa6384062b259194b1acbd0378116064

Save the generated information in ANSI encoding as rarreg.key.

Execute the following code in the terminal and configure two paramet

When using ANSI encoding, you can only use characters from the country or region where your operating system is located. ANSI encoding is supported from Powershell 7.4 onwards, and you will also need to upgrade your Powershell.

Generate multi-language licenses in ANSI encoding.

winrar-keygen.exe "简体中文" "license" | Out-File -Encoding ansi rarreg.key

winrar-keygen.exe "繁體中文" "license" | Out-File -Encoding ansi rarreg.key

winrar-keygen.exe "Deutsch" "license" | Out-File -Encoding ansi rarreg.key

winrar-keygen.exe "Français" "license" | Out-File -Encoding ansi rarreg.key

winrar-keygen.exe "日本語" "license" | Out-File -Encoding ansi rarreg.key

winrar-keygen.exe "한국어" "license" | Out-File -Encoding ansi rarreg.key

When generating utf-8 licenses, you may need to check Use Beta:Use Unicode UTF-8 for global language support in Control Panel > Clock and Regions > Regions > Administration > Change System Region Settings in order to process the data correctly. However, it is not recommended that you do this, which may cause many software to not work properly, and it is recommended to use Github Actions.

Generate multi-language licenses with UTF-8 encoding.

utf8: is to ensure constant character representation in WinRAR across languages.

winrar-keygen.exe "utf8:简体中文" "license" | Out-File -Encoding utf8 rarreg.key

winrar-keygen.exe "utf8:繁體中文" "license" | Out-File -Encoding utf8 rarreg.key

winrar-keygen.exe "utf8:Deutsch" "license" | Out-File -Encoding utf8 rarreg.key

winrar-keygen.exe "utf8:Français" "license" | Out-File -Encoding utf8 rarreg.key

winrar-keygen.exe "utf8:日本語" "license" | Out-File -Encoding utf8 rarreg.key

winrar-keygen.exe "utf8:한국어" "license" | Out-File -Encoding utf8 rarreg.key