bitcookies/winrar-keygen

Principle of WinRAR key generation.

WinRAR Keygen

Principle of WinRAR key generation

简体中文 | English

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:

• Use Github Actions with Secrets <⭐ Recommend>
• Use Github Actions with Push
• Build in Visual Studio

4. Use Github Actions with Secrets

Click to expand

Use Secrets you don't need to commits to the repository, so you can fetch upstream without conflicts. So I recommend using this method.

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 Creating Secrets

After allowing Workflows, go to Settings > Secrets and variables > Actions > New repository secret.

Create two Secrets named text1 and text2 and fill in values.

Once created, you will see:

4.4 Run Workflow

Go to Actions and select WinRAR Keygen Secrets to run Workflow manually.

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

After extract rarreg_file.zip, you will get rarreg.key, just drag and drop it into WinRAR. You can also compress rarreg.key into rarkey.rar and double-click it to run it, and the license import will take place automatically.

If you get an invalid key, please check the specific solution.

5. Use Github Actions with Push

Click to expand

Using push for key generation is very simple and convenient, but when there are updates to fetch upstream, you need to manually merge conflicts. So I would recommend Use Github Actions with Secrets, but you can still use the push action.

5.1 Fork

Fork this repo.

If you've forked before and I've committed new code, but you don't know how to merge the new content into your repository, then you can delete the current fork and fork again.

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 Edit info.json

Open your forked repository, and go to keygen/info.json and click on the edit button to edit the file.

You can see:

{
    "text1": "Github",
    "text2": "Github.com"
}

You can modify the values corresponding to text1 and text2:

{
    "text1": "Your Name",
    "text2": "Your License"
}

It is important to note that test1 and test2 are ANSI-encoded string, space are now supported.

Once you have finished making changes, click the Commit changes button and Github Actions will start automatically.

5.4 Download Key

Go to Actions and select WinRAR Keygen to see the status of the program.

Green means it ran successfully, yellow means it is running, red means it failed. After running successfully, open the corresponding task and select rarreg_file to download.

After extract rarreg_file.zip, you will get rarreg.key, just drag and drop it into WinRAR. You can also compress rarreg.key into rarkey.rar and double-click it to run it, and the license import will take place automatically.

If you get an invalid key, please check the specific solution.

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

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 use Github and Github.com:

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

Example:

        winrar-keygen.exe "Github" "Github.com"
  or:
        winrar-keygen.exe "Github" "Github.com" > rarreg.key
  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
Github.com
UID=3a3d02329a32b63da7d8
6412212250a7d8753c5e7037d83011171578c57042fa30c506caae
9954e4853d415ec594e46076cc9a65338309b66c50453ba72158c0
656de97acb2f2a48cf3b75329283544c3e1b366a5062b85d0022f6
de3cdc56b311475b484e80b48157a0c3af60ca4f7f9c75d49bc50d
6bad616c1c58caa922d3ed0cd19771e8191522a586544c3e1b366a
5062b85d29db066f02e777ad78100865f2c31f2dd3a86998609b18
5eede7ed46566b10bf033daa6384062b259194b1acbd1443042646

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

7. Invalid Key

Why is my rarreg.key invalid?

7.1 ANSI Encoded

test1 and test2 are ANSI-encoded string, space are now supported Issues #5.

winrar-keygen.exe <text1> <text2>

You can refer to: Generation of "rarreg.key"

7.2 TXT Encoding

If you use the following command:

winrar-keygen.exe "Github" "Github.com" > rarreg.key

In 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

7.3 Location of Key

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

You can also compress rarreg.key into rarkey.rar and double-click it to run it, and the license import will take place automatically.

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

winrar-keygen's Issues

it doesnt put RAR registration data in on the top of the rarreg.key

Hello I was using your keygen which was very nice but it doesn't put RAR registration data on top of the rarreg.key file which dont let it be usable

Format string causes undefined behavior

The format string "60%060s%060s" at:

winrar-keygen/WinRarKeygen.hpp

Line 214 in fbc4fb2

RegInfo.Items[1] = HelperStringFormat("60%060s%060s", LicenseTypeSignatureS.c_str(), LicenseTypeSignatureR.c_str());

and

winrar-keygen/WinRarKeygen.hpp

Line 242 in fbc4fb2

RegInfo.Items[2] = HelperStringFormat("60%060s%060s", UserNameSignatureS.c_str(), UserNameSignatureR.c_str());

is not valid, the "0" flag cannot be combined with the "s" specifier.

The string should be replaced with "60%s%s" like this:

winrar-keygen/WinRarKeygen.hpp

Line 214 in fbc4fb2

RegInfo.Items[1] = HelperStringFormat("60%060s%060s", LicenseTypeSignatureS.c_str(), LicenseTypeSignatureR.c_str());

should be replaced by:

RegInfo.Items[1] = HelperStringFormat("60%s%s", LicenseTypeSignatureS.c_str(), LicenseTypeSignatureR.c_str());

and

winrar-keygen/WinRarKeygen.hpp

Line 242 in fbc4fb2

RegInfo.Items[2] = HelperStringFormat("60%060s%060s", UserNameSignatureS.c_str(), UserNameSignatureR.c_str());

should be replaced by:

RegInfo.Items[2] = HelperStringFormat("60%s%s", UserNameSignatureS.c_str(), UserNameSignatureR.c_str()); 

The changes introduced in #6 already ensure the strings to be formatted are exactly 60 chars.

关于简中注册仍有广告的解决办法

考虑到PR太麻烦，这里就提个 issue 啰嗦一下吧，以下正题：

首先，WINRAR的简中个人版，不管有没有注册都有广告。

这里是简中版去广告的四种方式。

1. 通过Resource Hacker修改及删除了内部的广告程序：全栈程序员站长-WinRAR去广告：只需六步，教你去除WinRAR的广告
2. 阻止其联网：百度经验-如何禁止winrar弹出广告
3. 使用商业版进行注册，winrar商业版提取器：wiflvtx/win-rar-extractor
4. 绕道官网购买(非代理商)，联系WinRAR技术支持：为什么 WinRAR 买了授权还是有广告？ - 小约翰的回答 - 知乎

商业版地址规律：

• rarlab渠道：https://www.win-rar.com/fileadmin/winrar-versions/sc/sc20220317/rrlb/winrar-x64-611sc.exe
• win-rar渠道：https://www.win-rar.com/fileadmin/winrar-versions/sc/sc20220317/wrr/winrar-x64-611sc.exe

YYYYMMDD，年月日；PPP是渠道；XXX，版本号。

https://www.win-rar.com/fileadmin/winrar-versions/sc/scYYYYMMDD/PPP/winrar-x64-XXXsc.exe

综上所述，这些文献资料提供的信息与逻辑，个人想出了一个快速使用的小点子

• #14 (comment)

其他参考资料：

• 知乎问答-为什么 WinRAR 买了授权还是有广告？
• 小白软件库xbrjk-如何下载纯净、无广告的WinRAR（商业许可版）！
• 微信平台-OSS0539-本期来深扒一下WinRAR这款压缩软件

Workflows are not available.

By simply following the tutorial you may hit a roadblock because the workflows are not visible.

This is because they are disabled by default on forked repos.

Could you add a note in the readme to warn noobs like me to press 'that button' to enable them.
I found the button but pushed it before documenting the process.

Found Malware

Just on the Release file executable, I found detection score of 2/74 at VirusTotal. CrowdStrike Falcon and Cynet are claiming that.
Just check and disinfect your executable. Thanks!

dont see workflow in actions (not secret actions)

i forked it
made the text1 text2 secrets with the github in them and then clicked actions and the workflow is no where to be seen
(nvm it was in keygen secrets lol mb)

Hardly see Math formulas in dark mode.

https://github.com/bitcookies/winrar-keygen/blob/master/README.HOW_DOES_IT_WORK.md

I don't know if it's possible to change the font color.

InternalError: The length of register data is not correct.

The error InternalError: The length of register data is not correct. is sometimes returned while generating a key.

After some testing, I discovered that the length checks that should prevent that error in the first place, are incorrect.

first:

winrar-keygen/WinRarKeygen.hpp

Line 196 in 4d7ecf7

if (LicenseTypeSignatureR.length() <= 60 && LicenseTypeSignatureS.length() <= 60) {

Pad with zeros, and <= should be == :

if (LicenseTypeSignatureR.length() < 60) {
    LicenseTypeSignatureR.insert(LicenseTypeSignatureR.begin(), 60 - LicenseTypeSignatureR.size(), '0');
}
if (LicenseTypeSignatureS.length() < 60) {
    LicenseTypeSignatureS.insert(LicenseTypeSignatureS.begin(), 60 - LicenseTypeSignatureS.size(), '0');
}
if (LicenseTypeSignatureR.length() == 60 && LicenseTypeSignatureS.length() == 60) { 

second:

winrar-keygen/WinRarKeygen.hpp

Line 207 in 4d7ecf7

if (UserNameSignatureR.length() <= 60 || UserNameSignatureS.length() <= 60) {

same as above, and || should be &&:

if (UserNameSignatureR.length() < 60) {
    UserNameSignatureR.insert(UserNameSignatureR.begin(), 60 - UserNameSignatureR.size(), '0');
}
if (UserNameSignatureS.length() < 60) {
    UserNameSignatureS.insert(UserNameSignatureS.begin(), 60 - UserNameSignatureS.size(), '0');
}
if (UserNameSignatureR.length() == 60 && UserNameSignatureS.length() == 60) { 

These changes should get rid of that error.

Registration Failed

RAR registration data
Github
Github.com
UID=3a3d02329a32b63da7d8
6412212250a7d8753c5e7037d83011171578c57042fa30c506caae
9954e4853d415ec594e460a7213ad70c9139c941613a53b6798ea8
aa19873a1f107ba38957c31029722ba44f4c88667180de0dd18d35
b59927bfb6c3db0f916a59b707c657bc9360faa4200e4ee2cbd7e2
7ca2797b748eb2edce71ac60b2e8cca23563003c752ba44f4c8866
7180de0dfb4545465f32e0b12aa3bcaf0e9c21b4425f627c609b18
5eede7ed46566b10bf033daa6384062b259194b1acbd3027113380

WinRAR version: 6.0.2

[Request] binary or tutorial for Linux

I would really like to know, if this code is also intended to be used on Linux.
Of course I can use mono or wine . but I would like to run it as binary or a compiled code on linux.

So how do I compile this for linux? :)

Thanks in advance!

(win10) Can't run keygenx64.exe

i do disabled window defense but it didn't seem to work. it just flash open a console like cmd window and close itself immediately

WinRAR keygen may not work anymore soon

Hey, I don't know if this will be a problem in the future, but I still posted this, take a look at the picture

It says that some three features are "deprecated" and will be "disabled" soon
I'm not sure if anyone posted this issue before, but just went with it anyways

Convert rarreg.key to rarreg.rar?

When you purchase WinRAR, you get a rarreg.rar file which can be opened in winrar to activate it.
How can I convert the rarreg.key that this tool generates to a rarreg.rar? Just compressing it doesn't work.

生产的rarreg.key注册失败的解决办法 powershell

可能是编码错误，手动用notepad++把rarreg.key的编码改为utf8保存后再拖进winrar实测注册成功！