Run KMS_VL_ALL.cmd as admin. It will take care of the rest. Activates Win 8.1 and 2013. Don't know about WMC though (I prefer VLC instead )
1) What happens after 180 days? will Windows stop working? Is it just a matter of re-activating again? 2) It will be interesting to see what MS puts on Service Pack 1 on how to disable the activator...I guess it's all offline!! How can MS stop this going forward is my main concern?
1. It nags and nags and nags and nags some more. It works, but gets annoying after a while, and no, you cannot "get used to it" (you will either buy an original key or go the pirate way. Or uninstall). 2. Well, they surely aren't gonna call off KMS activation altogether. The activator is all offline, yes. That's why M$ has no way of keeping track of VL editions. The most they can do is make the KMS protocol even stricter. But reverse engineers are always a step ahead. Funny how M$ bravely say "You seem to be a victim of software piracy" when you try to activate using a blacklisted key. Aren't M$ the real victims of piracy? EDIT: 1. Yes, just reactivate when you want to, and you're good to go for another 180 days 2. Main concern? Now you're scaring me IMHO, they can't stop this going forward unless they make it open source and stop charging people for it (Kinda defeats their entire purpose but still)
Sweet. I remember speaking to Daz with the Windows 7 loader years ago - it was a masterpiece with what he had inbuilt into the loader. It looks like the KMS will also be fault/MS proof.
'You ppl' - Did you ever consider that quite a few us may well be retail activated, be comfortable with backing up and restoring our activations etc, etc. And that we may just have a genuine interest in this stuff, enjoy experimenting with it and comment and post our results for the coders developing all this stuff? This is how we learn, and can in turn assist others with smaller problems they may encounter. You ppl = bad attitude IMO.
Tested and it worked for me while disconnected, however I'm not sure about the silent bit, personal, preference I guess but I'd like to see something on screen advising that something is in progress. Saw the temporary Tap adpater being created and removed and became activated but as mentioned I'd prefer to see something on screen. Or am I missing the point, this sfx is intended to be used in other ways?
Yes, this SFX is nice for auto-activation on a new setup. Murphy78, this is too weird, I was just setting up a nice clean install to do some testing on your $oem$ folder, and was just about to create a new post here, when I saw this latest offering from you! Thanks!! Literally at the same minute! So now I'll test this latest version, of course and let you know how it goes (I'll edit this message, or create a new one, depends on the activity here, sometimes it seems there's not that much interest in "silent" activation procedures like these, I can't understand why!!?) Edit1: I'm testing on an older laptop, and your previous $oem$ version didn't work for me (yet), some strange stuff going on there, but it looks like something's just not finished in time there, I can't figure out what exactly causes it (I did a lot of proclist etc, to see if some process had to finish before slmgr /ato was succesful).
abbodi1406 already made the verbose version. the whole point of this is to be able to run it as a task without spam screens.
Your post has enlightened me, thank you. As you will see I asked... Now I see it's usefulness, cheers. Cheers for your reply too.
Well, it doesn't work on my test laptop (yet), but that's OK, I'm looking forward to testing the heck out of it, I'm sure I'll find the problem somewhere. As I said, the laptop's not the top of the line, but I use it all the time with all Windows versions, so there should not be anything fundamental why it wouldn't work. I also used your $oem$ folder on W8 for as long as it's available, so I have a pretty good understanding of what's going on. I will try to figure out what the problem is, if anybody has some pointers on what to check, please let me know! I will also test it on a faster PC to see if that makes a difference (if not, we can rule out the "slowness" altogether and the problem must be elsewhere). EDIT: Hmmm, starting the SFX a *second* time resulted in a successful activation!!!!! This looks like more evidence that "something" is waiting for "something" "somewhere" in the process?! I'll restore my TI backup and try again (and again, ...), see if this little problem is reproducible. As you know, right after a clean setup, the system can still be "extra busy" for a while, so it's possible that some processes in relation to activation can take a bit longer...
Since i don't have issue and the script is working for me while internet is off, could you test this script? just extract it to the same folder "KMS_VL_ALL" and run
Is there a way to setup a server like it was with KMS.Server.Service.Config - A KMS Service and Emulator Maintenance Script forums.mydigitallife.net/threads/44717-KMS-Server-Service-Config-A-KMS-Service-and-Emulator-Maintenance-Script#a5 I would like to setup a new KMS server on a 2012 R2, without VM. Current projects work great but seem to be intended for local host usage. (KMS pico and micro) I'm looking for something to run as a service.
Quick feedback A friend of mine has faced same problem as Nucleus (No KMS Server can be contacted when offline) but this one works perfectly for him. Don't have a PC right now so I can't mess up with the new script to see the actual 'fix'.
First off, sorry for the delay, been busy. And thanks for your support with this, as you can see by now it's become the fave of quite a few - well done. Anyway my feedback... Connection Disabled - Added KMS_VL_ALL_verbose4.cmd to the 6.0.2 release and ran as admin, gravy all the way, everything fine, Tap adapter created, Server started, Win 8.1 and Office 2013 activated, Tap adapter removed - perfect. You changed something in the script? Don't know whether this is relevant - you'll know if it is or not. Still disconnected - If I run KMS_VL_ALL_verbose4.cmd a second time it fails 'No KMS Server can be contacted' - something (temporary) being left behind from the first run? But if I reboot and run it again - gravy all the way. This may be right I don't know, as mentioned you'll have to advise. Should it work if run repeatedly - testing of course? Can/does your pal verify the above scenario? Run it a second time and 'No KMS sever can be contacted'? Edit: @abbodi1406 - Resolved the running it multiple times thing myself - yes you should be able to? Disconnected - Tested with v6.0.1, ran both scripts several times and they worked flawlessly every time.
Further to my initial comment about the silent operation... Once the penny dropped and I realised how useful this may prove - I now see the good of it. Thank you.