Welcome to nsane.forums

Welcome to nsane.forums, like most online communities you need to register to view parts of our community or to make contributions, but don't worry: this is a free and simple process that requires minimal information. Be a part of nsane.forums by signing in or creating an account.

  • Access special members only forums
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates

Sign in to follow this  
Followers 0
alienvi

Microsoft Toolkit.2.4.8 crashes on Windows 8.1 for office 2013 volume activation

10 posts in this topic

I have installed and activated - W 8.1 x86 Retail Key

I installed Office 2013 volume edition on W8.1

When I use Microsoft Toolkit.2.4.8 for Office 2013 Volume activation, it crashes....

So is it conflict between

OS - w8.1 being Retail version

and

Office 2013 being Volume version

OR

any other reason?

Share this post


Link to post
Share on other sites

wait for new release that support windows 8.1

Share this post


Link to post
Share on other sites

Well since any kms server does not support windows 8.1 at all it wont work

1 person liked / thanked this

Share this post


Link to post
Share on other sites

Windows 8.1 uses KMS protocol v6, which is currently unsupported by Microsoft Toolkit and has yet to be successfully cracked and emulated. Windows 8 uses KMS protocol v5, which is currently supported by Microsoft Toolkit. Microsoft Office 2013 VL uses whichever KMS protocol the operating system is using. Because you are using Windows 8.1, Microsoft Office 2013 is also using KMS v6, which is currently unsupported.

You are going to have to wait for a solution to KMS protocol v6 (could be weeks, months, years, or never), use the solution above, buy Office 2013, or downgrade to Office 2010 (which uses KMS v4 no matter what the OS is).

Edit: With regard to how long it might take to reverse-engineer KMS protocol v6, it took around 6 months to reverse engineer KMS protocol v5. It might be that KMS v6 is so similar to KMS v5 that it will be reverse-engineered much earlier. It also might be that new security measures will make it more difficult to reverse-engineer. Only time will tell.

Edited by Lacius

Share this post


Link to post
Share on other sites

Windows 8.1 uses KMS protocol v6, which is currently unsupported by Microsoft Toolkit and has yet to be successfully cracked and emulated. Windows 8 uses KMS protocol v5, which is currently supported by Microsoft Toolkit. Microsoft Office 2013 VL uses whichever KMS protocol the operating system is using. Because you are using Windows 8.1, Microsoft Office 2013 is also using KMS v6, which is currently unsupported.

You are going to have to wait for a solution to KMS protocol v6 (could be weeks, months, years, or never), use the solution above, buy Office 2013, or downgrade to Office 2010 (which uses KMS v4 no matter what the OS is).

Edit: With regard to how long it might take to reverse-engineer KMS protocol v6, it took around 6 months to reverse engineer KMS protocol v5. It might be that KMS v6 is so similar to KMS v5 that it will be reverse-engineered much earlier. It also might be that new security measures will make it more difficult to reverse-engineer. Only time will tell.

Yeah you are completely wrong about this let me message you to clarify and correct a few things about this...

Message sent :) I hope this clarifies more about kms v6

Edited by AR_Alex

Share this post


Link to post
Share on other sites

Yeah you are completely wrong about this let me message you to clarify and correct a few things about this...

Message sent :) I hope this clarifies more about kms v6

You don't seem to understand how KMS emulation works or the difference between KMS emulation and other forms of KMS activation. I sent you a PM correcting your misinformation. What I posted pertaining to Microsoft Toolkit is accurate.

Share this post


Link to post
Share on other sites

I have a 2.4.9 build that fixes the crash, but have not released it yet.

It crashes due to the KMS Server code someone at MDL (jm287) made for .NET throwing an Exception when it gets KMS V6.

I fixed this and will make 8.1 License Backups possible. Restore would be untested, but the option to at least make the Backup would be there.

The new build will not activate anything but Office 2010 (not 2013), when dealing with Windows 8.1 (because Office 2013 marries itself to Windows 8.X, but 2010 uses OSPPSVC, independent licensing).

It is likely someone will dump a KMS Server VM like last time, because MS is making MAK/CSVLK available slowly (I am not aware of any leaking).

4 people liked / thanked this

Share this post


Link to post
Share on other sites

Thank you CODY we will now at least have a license backup. :showoff: without having to copy folders

Share this post


Link to post
Share on other sites

Thank you CODY we will now at least have a license backup. :showoff: without having to copy folders

As far as i am aware backup and restore function disable with Microsoft Toolkit since the compatible version of Windows 8.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0