I wonder if there is a service that's on a delayed start, or auto, that is causing problems. It would explain why having the network panel open would solve the issue. Perhaps we can do a net start for it... Could someone that has this issue try to find out what service is being started when you open the network connections panel?
Sorry, I don't know what is update.exe, maybe is part of another application and has nothing to do with your activation with KMSAuto Easy, just mere coincidence. Look carefully and you will find download links for EN and ES versions (english and spanish), they are solidfiles and rghost links.
nucleus @ post 2400 thanx a lot nucleus. So in simple terms, i need to run KMS_VL_ALL once in 6 months and KMS server service just once until i re-install windows, right ?
I have already done a lot of testing to check exactly this point, but could not find anything. Leaving the network connections panel open is not an option for me (has to be silent), so what works for me at this point is set MediaStatus=1 plus reboot. EDIT: I guess I should rephrase that a bit to be clear: After I set MediaStatus and reboot, service-based activation always works for me, after setting it once, I never have to set it again, it works on every reboot. I've built it into my PostInstall.exe (which silently installs all my stuff on a new install, and needs a reboot anyway). So that's Murphy/Abbodi's KMS_VL_ALL $oem$ on clean install (once), service-based activation on PostInstall. Works for me, awaiting new findings from CodyQX4 (and others).
Request: Please use the 'Thanks' button (at the bottom left corner of each post), or we do not know who you are thanking
I just spent the last hour reading 40 or 50 pages back from this particular post, and I still haven't found the answer I am looking for. I've decided to just save myself some time and publicly humiliate myself and ask what many of you will likely consider to be a "Stupid Question". Here goes: As many of you may recall, a little over a year ago it became possible to build an actual full blown KMS Server (from scratch) that would automagically activate all modern versions of Windows and Office connected to the same network. Still to this day it amazes me that a full year later it still works like it did that day that I built it. Anyway, as I understand it, the KMS protocols have changed considerably in Windows 8.1 and Server 2012 R2. Since the file posted in the quote above is only 158.50 KB, I'm sure this is NOT what I'm looking for. The answer I seek is - has anyone devised a "Build your own KMS Server from scratch" that will activate 8.1, 2012 R2 (and older), Office, etc. YET? Thanks in advance. . .
1) Install Windows Server 2012 R2 in a Virtual Machine (VM or HYPER-V) 2) Run the service only script from: KMS.Server.Service.v6 3) Check firewall port 1688 4) You have a full blown KMS Host server that wil activate almost everything... 5) 1 issue: the KMS host is not activated yet: I have activated mine by setting slgmr /skms myexternal-ip and slgmr /ato (note: WAN router must support this and port 1688 must be open) Now my KMS HOST is also activated... IMHO this is the most clean install of a KMS HOST in a windows environment.
Old school KMS Server from scratch vs. New KMS Server Service I gather from your explanation above, I could literally shutdown my existing KMS Virtual Machine (built in 2012), run this "KMS Server Service" on the same machine that I am currently using as a hypervisor, change the _VLMCS DNS Service Location (SRV record) from the IP address of the former KMS VM to the IP Address of the hypervisor itself, and have exactly the same functionality in addition to being able to activate 8.1 and 2012R2 ?!?!? Oh don't worry, I will
Old school KMS Server from scratch vs. New KMS Server Service Can I assume that step (1) listed above could also be Windows Server 2012 vice R2 or must the OS be 2012 R2 ? Thank you for the suggestion. It sounds quite elegant indeed. Any PROs or CONs with comparison to Murphy78's method?