KMS Activate Windows 8.1 (En & Pro) and Office 2013

Yes & tap1 is enabled network bridge is on. Can it be from the version or something I'm using MICROSOFT.WINDOWS.8.1.PROFESSIONAL.RTM.X86.VOLUME.WITH.ROLLUP-1.ENGLISH.DVD-WZT

 

I successfully used KMSmicro to reactivate Win 8.1 64 RTM Pro that I originally activated with KMSpico about four days ago. I know that KMSmicro is only supposed to activate VL versions but I believe that KMSpico converts the RTM key to VL before activating. In my case it showed the 'Blue' edition as activated prior to using KMSmicro.

I'm wondering if KMSmicro will monitor my activation and reactivate before the 180 days is up or do I need to keep an eye on it and do it manually? My understanding is that KMSpico reactivated after each start.

Hope my question is not seen as totally lame. I feel out of my depth amongst such high achievers!

 

You need to login to view this posts content.

 

Try firing up the activator, but then tabbing out and running admin command prompt.
Navigate to your office folder that has the ospp.vbs file and run:

Code:

cscript ospp.vbs /sethst:KMSMICRO-PC
cscript ospp.vbs /setprt:1688
cscript ospp.vbs /act

It's just a suggestion, I don't have much experience with using names instead of ip addresses.

 

Are there possibly any differences between the OEM version released back in August 27, 2013 and the Public version released on October 18, 2013 that may affect activation proccess in some way!? Cause I almost tried everything, following every details described in this thread, in every possible way, yet no luck making KMSMicro 5 to activate my Windows 8.1 Enterprise x64

 

If you installed office in a different location from the default location, try using the method I just listed in the post before this...

 

Here's my instructions on TPB... make sure you've done EVERY step.

Code:

1) Remove any previous activators or helper applications such as KMS keygen
or KMSpico
2) Open KMSmicro.exe
3) Go to settings tab and choose the "Installing TAP" button and follow
the install directions
4) After TAP is installed, go into your network settings and rename the new
TAP connection "tap1"
5) Highligh both your normal connection and the 'tap1' connection and right
click and choose "Bridge Connections" (let it work for a minute)
6) Alt-Tab back to KMSmicro and click the "Run KMSmicro Console" button
7) Wait a few minutes while the VM warms up
8) Choose the "t" option in the VM to syncronize time with the internet and
press enter
9) After fully syncronized, Alt+Tab back to KMSmicro app and Click the
"Activate Windows" or "Activate Office" button depending on your needs

 

Thank you but that's exactly what I did and even more!!!

 

Disable Firewalls and AVS before doing this, Eset is know for blocking KMS

 

Thanks i know this method and in fact it worked, but as i said before

 

Thanks Page 66, I would never find it lol. I was at page 83....

Now, people seem to be running this with a server 2012 R2 VM or so to activate their copies. I'm gonna investigate this but if anyone is willing to share the steps, please do

 

What version of Windows or Office are you trying to activate?

 

You need to login to view this posts content.

 

Not to my knowledge. It doesn't seem to read from the registry to find Office locations like most of the activation scripts do.
If it really bothers you to manually type it out even though there will DEFINITELY be another activator in the next 180 days, you can uninstall Office and Re-Install it in the default location.

 

When yesterday use kms micro 5 didn't make the bridge in network (use only tap1) but windows activate without problems.

 

Do you think it will be available another method to activate KMS? I read that KMS V6 blocks any attempt of activating with local IP address like 127.0.0.*

 

I'm not a noob guys, please do not treat me like one.
I'm already trying this on a freshly installed Windows 8.1 on VMWare.
Not a single software is installed including firewalls, antiviruses, I've also disabled and turned off all security features of Windows itself including Windows Firewall and Windows Defender.

 

Bridging is only needed for time syncing.
Not really needed if times are adjusted accordingly.

 

Thanks, I appreciate the apology.

I agree with you that if Ratiborus set the VM's time zone to UTC+0, he could just ship it like that and use "-rtc base=utc" option, and then noone would have to fiddle with time zone settings.

 

You need to login to view this posts content.