Personally, I'm feeding the files into @Hotbird64's License Manager, to broaden its horizon, so to speak. pkeyconfigs are essentially the foundation for the key checkers, to understand the new and changed key types. So, you can even teach old dogs like the Ultimate key checker (with internal databases up to 8.1 only) how to read the new keys correctly.
Thank you . I read what Enthusiast said and took it to mean ...... ' Your getting close keep trying ' ...... so i replaced the two files in system32 and syswow64 ...... it restarted OK with the two replaced files ...... then i tryed to use the key to activate it ...... but it didnt work ....... so i was planning to do a clean install and try again ........ and then if that didnt work a clean install with those two files already in the install.wim ...... just to see what happens Had a look for @Hotbird64's License Manager and Ultimate key checker here and google but couldnt find them and play with them ...... yet ...... will try again ' later ' at the moment i have an info and ideas flood = TILT
Are you trying to use it for activation purposes? Why not just use KMS_VL_ALL or google for "Massgravel" for the HWID tool.
>Are you trying to use it for activation purposes? Yes . But permanently . With XP and win 7 it was ' easy peasy pudin and pie ' . >Why not just use KMS_VL_ALL or google for "Massgravel" for the HWID tool. I did it with KMS_VL_ALL and it activates it but not permanently ...... also playing with **************.mk6.v62.01 , KMS_Suite_8.7_EN , Multi-OEM_Retail Project , pidgen.v1.2.0.606 and just replacing a / the $OEM$ file Had a look at ' Massgravel ' ( MAS_1.3_AIO_CRC32_6F6382D8.cmd ? ) but couldnt get it to work for me ....... will try again with a clean operating system install . Checking OS Info [Windows 10 Pro for Workstations | 18363 | x64] Checking Internet Connection [Connected] Checking ClipSVC [Service Status -Stopped] [Startup Type -Demand] Checking wlidsvc [Service Status -Stopped] [Startup Type -Demand] Checking sppsvc [Service Status -Running] [Startup Type -Delayed-Auto] Checking wuauserv [Service Status -Stopped] [Startup Type -Demand] Changing services Startup Type to [ wuauserv-Auto ] [Successful] Starting services [ ClipSVC wlidsvc wuauserv ] [Successful] Installing Generic Product Key [xxxxxxxxxxxxxxxxxx] [Retail] [Successful] Extracting Required Files to Temp [C:\Windows\Temp\_Ticket_Work\] [Successful] Creating modified gatherosstate [Successful] Generating GenuineTicket.xml [Successful] Installing GenuineTicket.xml [Unsuccessful] Aborting... Changing wu Startup Type back to [Demand] [Successful] Cleaning Temp Files [Successful]
And ...... yes i know its not Windows 10 Insider Preview Build 19624.1000 (PC) [FAST - rs_prerelease] ........ I've got that on my other machine ....... and at the moment i'm just playing ....... will try again later with Windows 10 Insider Preview Build 19624.1000 (PC) [FAST - rs_prerelease] on this machine
Doesn't activate by itself, only when there is a MSDM, SLIC or PID.TXT with a working key is inserted and the correct settings are set. pkeyconfig is not meant or usable for activation. KMS_VL_ALL with autorenewal set is as permanent as can be, as long as the AV doesn't f**k it up. The tool from massgravel is a simple cmd to run.
This build is frustrating, I tried to download it from uupdump and have it convert to iso, then extract it and run setup.exe but it never loads the setup. Anybody get this working?
Yes I have done that with 7zip v19.00x64 and it extracts just fine, I just run the setup.exe and see a blue circle on the mouse pointer briefly and then it never opens, if I go into Windows.BT it has SetupHost.exe with the correct date and time but when I try and open it it does nothing Modern Setup Host Description Faulting Application Path: C:\$WINDOWS.~BT\Sources\SetupHost.exe Creation Time: 5/7/2020 11:02:59 PM Problem: Stopped working Status: Report sent Problem signature Problem Event Name: BEX64 Application Name: SetupHost.exe Application Version: 10.0.19624.1000 Application Timestamp: d612098b Fault Module Name: SetupPlatform.dll Fault Module Version: 1.60.19624.1000 Fault Module Timestamp: 7b96acc7 Exception Offset: 00000000000010d3 Exception Code: c0000409 Exception Data: 0000000000000005 Extra information about the problem Bucket ID: ce9afd43627caf3a6a4f6775fcf0c330 (1895847724598739760)
I've never encountered this before I can't run this no matter what I try, uninstalling GPU drivers, etc. I keep getting the same 0xc0000409 error through Windows Update or through the SetupHost.exe Edit: I just downloaded 19619 and ran the 19619 setup.exe from the extracted 19619 ISO file and it opened without a problem. It in-place installed and then when I got back to the Desktop I immediately ran 19624 exe extracted from uupdump ISO and that opened immediately. I was able to update to 19624 this way.
I installed 19619 in Hyper-V, and then immediately upgraded to 19624 using setup.exe from the ISO. It took maybe ½ hour, though I am not sure. I wasn't paying that much attention to it, and all of a sudden it was done.
ok, thanks for confirming, I didn't try out this yet, on 20H1 currently, hopefully, MS finally rolled it out publicly with 20H2.
If I upgrade 19041.208 to this build. Will I be able to upgrade to the final build of this when it is released?
If you're asking that whether you can upgrade to this 196xx build from 19041 (AKA 20H1), then the answer is yes, by joining the Insider Programme. If reverse, i.e. from 196xx to 19041 final public build (GA) when released, then no
I already updated 20H1 to this preview build. But I don’t really know if that was a good move. The build that will be released at the end of may is for 19041 (20H1)? I used whatever127‘s OfflineInsiderEnroll to update to 19041 and to this preview.