v1.3.1

I just changed my name on GitHub, so I updated the copyright notice.

Full Changelog: 1.3.0...v1.3.1

1.3.0

Update 4: Security Updates

Starting with update 1.3-beta-1, Security Updates have been created. This system will notify you if a security breach has occurred in MSActivate or it's dependencies. This is a great step in preventing a hack simular to xz-utils or another sort of sophisticated, planned attack. Any version above 1.3.0-beta-1 (1.3.0-beta-1) will get the error.

What's Changed

• Security update system, the major point of 1.3 release is done by @bendaws in #3

What's being worked on

• Improving this system. I have recently got a new PC so I will be resuming development very shortly.

Full Changelog: 1.2.0...1.3.0

1.3.0-beta-1

Update 3 (Milestone 1): Security Updates (Summary)

Note

Changes for this release are not found in master. Please see 1.3 for the source code for this beta release.

This is another great step towards making MSActivate better software. Starting with 1.3.1-beta-1, Security Update notices in case of a breach in MSActivate (or its dependencies) will automatically give off a warning. These are skippable, but they launch before any application uses these dependencies.

What's changed?

• This commit added in a security system.
• Updates to documentation about the Security Policy (SECURITY.md) and README.md.

What's being worked on?

• .NET dependency breaches. In this case, MSActivate will give an error and delete itself from the system.

Full changelog

Find it here: 1.2.0...1.3.1-beta-1

1.2.0

Update 3: Office Activation Support (Summary)

Office activation support is complete! You can now select

What's Changed

Pulls:

• Office Activation is complete (1.2.0 update) by @bendaws in #2

Changelog:

• Backend improvements, Office activation saves the command list to a temporary .BAT file to avoid spawning multiple instances
• Office activation exists
• Refreshed start page, that directs to Windows or Office activation
• Simple activation has been removed, and Advanced is now the default way to activate Windows

What's being worked on

Update 3 will add an overhaul on the backend for Windows activation to make it much more efficient.
It will also be the start of security updates for versions starting from 1.3.0 and above, and it will automatically
upgrade in case of a security vulnerability in any of MSActivate's dependencies:

• .NET Framework 4
• MSGuides.com KMS Servers

Full Changelog: 1.1.0...1.2.0

1.1.0

Update 2: Advanced Activation (Summary)

1.1.0 includes an advanced activator, letting you select the KMS server as well as a custom product key. If your version is not officially supported, this feature will let you use the custom product key to activate your Windows. See:

• Windows 11 keys: Full list (msguides.com)
• Windows 10 keys: Full list (msguides.com)

If your version is supported, you can autofill the product key using the buttons shown on the screen. You can also choose whether to start activation immediately or wait until later to do it yourself.

What's changed?

• Advanced activation window by @bendaws in #1

What's being worked on?

• I am currently working on support for activating Office 2021 using a simple menu.

New contributors

• @bendaws made their first contribution in #1 (My first pull request with fixed credentials, for some reason my pull requests were being signed by another random GitHub account. See the readme.)

Full Changelog: 1.0.0...1.1.0

1.0.0

Supports:

• Windows 11 (Home, Pro, Enterprise)
• Windows 10 (Home, Pro, Enterprise)

Activator is built with .NET 8.0, however it is self-contained and does not need to be installed for activator.exe to work.

This is a visual rendition of this websites KMS servers. This will automatically find your product key based on a selected version and install it, as well as set the KMS servers and activate Windows.

Note

You may need to restart your PC to activate Windows.