[DISCUSSION] Windows 10 Build 10240

Code:

slmgr /xpr

But that is misleading.

Previous Insider Builds showed that too. Most ppl seemed to be basing permanent activation upon the fact that winver now doesn't show an expiry date, and then a few moved their BIOS clocks forward (some by years) and activation remained. It's all way back in the thread somewhere.

 

had this a couple of times in the past.......i found if i restated or shut down and restart it cures it.

 

This activation s**t is brutal! I had 10162 installed but it wouldn't activate (supposedly a known problem), then MS takes down the ISO's and prevents further activation intentionally, and now when my 10162 got the upgrade to 10240, IT DOESN'T ******* ACTIVATE!

 

mine was upgraded within insiders and looks as if it was done with kms..says remaining rearm count: 1001..never seen 1001 before. also shows product id here as .16384 and in the registry as .16387

wth, doing a straight upgrade from retail 8.1 pro..let's see what this one says.

 

The esd is unpacked from the 2 rar parts and only unblocked, i did decrypt it once to an iso.

Edit, a not yet decrypted esd shows the wright hashes, thanks for your help murphy78

 

And here is another reason why Windows 10 Sucks, I'm just collecting them you know... I will show Microsoft their faults... for backstabbing me and giving me that crappy XAML Start Menu instead of the Win32 ver which worked nicely.... and for removing various options from Control Panel like Windows Update and slapping it on that crappy Settings App.

 

You need to login to view this posts content.

 

Still no core de-de yet? I really need it. 10125 home can't find any updates.

 

You need to login to view this posts content.

 

It's not going to activate over copy that was not activated, if you have backup copy put it on, come back I'll try to help you get activated

 

So can you still get updates through WU after you activated with KMS?

 

I don't know, wait till 30 Jul and try

 

Anyone can link me Enterprise x64 en-GB

Thanks

 

And why not? Yes of course you do.

 

Isee why I got those 50 lines of output..I did a slmgr /dlv instead of slmgr /xpr...lots on interesting detail in the first.

 

I finally got it right:

the ESD I used (I re-downloaded it) is binary same to that in the OP


What I hadn't notice is that,
after you run the Decrypt script on your ESD file,
then, after the procedure is completed,
your ESD in the folder is now decrypted, meaning that it has a different SHA1 than before.

Here are the two SHA1 values:

Code:

before decrypt: 9D40E15F430AB89A1EABB165ACBF40C9F07D18BB (i.e. as it is in the OP)
after decrypt:  3d247daf2868ca7dd3e2dfdd65f4b57b95869065

Sorry for the noise, and thanks again!

 

which english versions (en-us ) are not time-bombed ?

 

You need to login to view this posts content.