ummmm OK well I don't have that line at all but i can give you this Spoiler: KMS ===== !!! KMS-host Service is found in system !!! ====== The executable file: C:\ProgramData\KMSAuto\bin\KMSSS.exe Port : 1688 Windows PID : RandomKMSPID Office 2010 PID : RandomKMSPID Office 2013 PID : RandomKMSPID Office 2016 PID : RandomKMSPID Activation Interval : 43200 Renewal Interval : 43200 DebugMode : Disabled Log File : Enabled Hwid : by default ========================== === Your system is activated . === and this Spoiler: KMS Windows Info ========================== === Your system is activated . === = Products Status: Windows == Windows(R), Professional edition Product Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel Partial Product Key: T83GX License Status: Licensed KMS-host Machine: <default>:1688 KMS-host PID: 06401-00206-512-235947-03-1031-9600.0000-2572016 Expiration Date/Time: 23-November-2018 15:21 ( 179 d 16 h 11 min ) Activation Interval: 30 d 0 h 0 min Renewal Interval: 30 d 0 h 0 min ==========================
I have no knowledge about ratiboris' tools, maybe somebody can give us insight? It's weird that there is no license reason code mentioned on your saved report.
ummmm just to be clear I didn't upgrade yet I am still on 1709 and how does kmsauto net activate well I have no idea all I know is that it has something to do with organizations volume activation or something like that or using a kms server to emulate activation or something but can you direct me to a thread talking about HWID activation ??
and if you are talking about the iso file I used to install the current windows 10 pro It's long gone by now and can't remember its name but it came with a KMS R@1n service which I stopped and deleted then used KMSAuto net to activate and that was over a year ago and the name of the esd that I have now is 17134.1.180410-1804.rs4_release_clientconsumer_ret_x64fre_en-us_e698e1f0c2e6022982a48e299e06936f84d83a74.esd
KMS r@in probably uses REMOVEWAT too, it's the most bogus/fake activator ever released, after that is used, the install can't be trusted anymore, there probably are corrupted system files..
never heard of it before and I just tried and made a "17134.1.180410-1804.RS4_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO" using (esd-decrypter-wimlib-37) and holllllllllllllllllly Sh*t it worked OH MY GOD it worked I can't believe myself I was doing it only to rule out this option but it worked !!!!!!! DDDDD
thanks so much @SAM-R for mentioning the CLIENTPRO and thank you @Enthousiast so much for giving me some of your time to try and help me
With your conditions it should have worked with all consumer iso's, MVS or made from ESD. But glad this miracle worked
Yesterday I decide to do clean installation from Win7 Ultimate to Win10Pro Final 1803 that I got from here back in May 6th, then using esd-decrypter-wimlib-37 to covert to ISO. My Win7 bios was modded to inject slic2.1. I generated genuineticket.xml. Clean install Win10Pro and it did not activated no matter what I did. Unplug Ethernet, copy genuineticket.xml %ProgramData%\Microsoft\Windows\ClipSVC\GenuineTicket, reboot then plug ethernet back - still not activated. Was it because during the installation process my ethernet wire was plugged? I read this https://forums.mydigitallife.net/threads/solved-upgrade-from-windows-7-oem-to-windows-10.77183/ and they used Final 1709. So I did the same and it's activated. Finally I can do a clean installation on 1803 and it automatically activated. . Anyone had activation problem with 1803 when doing clean installation?
Maybe it's the BUSINESS part? HWID being OEMRET.... so, actually you only would have to enter the 3V66T key to get the hwid on that upgrade.
I was unable to activate with the ClipSVC method using an SLP activation with an SLIC 2.4 BIOS. I successfully activated Win7 Ultimate, then upgraded to Windows 10. It was unsuccessful. I then installed from fresh and copied GenuineTicket, that was unsuccessful. The error I got was 0xC004C003. Things I tried: 1) Run WGA tool, got validation result 0. 2) Installed the WGA update KB in Win7 before running gatherosstate 3) Run WGA online (can't, microsoft removed this page) 4) Tried to download the ISO straight from MS with the tool, instead of ESD to ISO conversion What I haven't tried is installing all the drivers in Windows 7 before upgrading to Windows 10. I read a while ago that this is a necessity but I can't be bothered. I also haven't tried running DAZ instead of legit SLIC activation in Windows 7. Someone mentioned that you need Pro Single Language for this to work... Honestly, the only place I see any mention of pro single language is the products.ini dump. Interestingly enough, the serial for it ends in 8M8K9 while my Pro install shows as 3V66T, so maybe there's something to it. I also suspect that the SLIC 2.4 may have something to do with it (I've seen two differing opinions on whether it is safe to use an SLIC higher than 2.1 for activation in Win7 -- so maybe Win10 is picking up on that -- but I doubt it). Anyways, I'm tired of fiddling with this, I'm just going to spend $5 for a grey market key and be done with it. I've never had this problem before.
Nobody from MDL would ever advised to use CSL or PSL, what upgrade path would coresinglelanguage or professionalsinglelanguage have from 7? From Homebasic and premium > 10 HOME, from pro and ultimate it's 10 Pro to upgrade to. Afaik, ProfessionalSingleLanguage (PSL) can't be activated in any way. Most people for whom this doesn't seem to work did something wrong along the way. As long as the windows 7 SP1 shows activated you should be ok (not when REMOVEWAT or any of the older activators is used, only DAZ Loader, key and genuine (modded bios) SLIC/CERT/OEMSLP activation will work). 1. Make sure 7 SP1 is properly activated 2. Make sure there are no exclamation or question marks in devicemanager, and the (W)LAN drivers are installed (when you can go online it should be OK) 3. Create genuineticket.xml, save it on usb 4. Clean install the appropriate windows 10 sku (clientconsumer) 5. run this command in an elevated cmd: Code: clipup -v -o -altto x:\ x:\ being the folder/drive in which the genuineticket.xml is saved in. 6. Run this command in an elevated cmd: Code: cscript /nologo slmgr.vbs -ato 7. Run this command in an elevated cmd: Code: cscript /nologo slmgr.vbs -dlv This last command is to verify all.