[Not working anymore] How to upgrade from W7/8.1 without going through the complete upgrade process

Look in
C:\Windows\System32\spp\store\2.0

Tokens.dat is in that folder.

On earlier W10 the folder was as my last post it was same on W8.x as well.

Code:

net stop sppsvc
cd %windir%\System32\spp\store\2.0
ren tokens.dat tokens.bar
net start sppsvc
cscript.exe %windir%\system32\slmgr.vbs /rilc

Note it will look like it has hung after typing the cscript line in and pressing enter... It takes about a minute then you will see a lot of writing whizz up the screen and then License files re-installed sucessfully. should appear. Reboot. See if it activated, if not disconnect from the net and copy the genuineticket into the required folder again, and then reboot again. On the next boot, connect to the internet and see if it has sorted it.

Failing that a reinstall of the OS, may be needed. Never tried a repair install to see if it sorted it.

Activation can be a very awkward thing to mess with. Usually easier to just bite the bullet and reinstall from fresh.

 

I've done a test, ran the x86 gatherosstate on a x64 win 7 and used it after installing 10 x86 and it worked. To be sure i will do another test with running the x64 gatherosstate on a x64 win 7 and install 10 x86 (on a freshly created VM ofcourse).

 

Found the folder and renamed the tokens. No luck. Do i need to install the default generic key prior to doing this? Need to do reboot? Need to disconnect from internet any point?

 

Have added some text to the post.

If this still not work then you could try a repair installation (ie run setup.exe on the usb/dvd/folder) and see if it repairs the confused activation status. If not then only option is back up your data and then do a fresh install , then the ticket way should then match that board.

As i mentioned the activation mechanism is very fussy and will refuse to activate, what has happened is that the OS that is installed (from another system) has sent the new HWID (via the ticket) and returned either a null and void reason code, or it just totally messed itself up.

The generic key should be already in the OS as if it was activated on the other system the key should not of changed.

 

This scenario also works

 

Are you using Windows 10 Pro Enterprise? Like I said, if you are using Windows 10 Pro Enterprise, this DOES NOT WORK! As I had Posted regarding RETAIL or OEM of Windows 7 Pro to Windows 10 (Pro/Home) OEM/RETAIL or Digital License Upgrade.. Seem like you did wrong.. Some bios has UEFI enabled.. Make sure you Disabled UEFI and use ACHI Lency mode.. then go my topic: https://forums.mydigitallife.net/th...te-upgrade-process.64770/page-74#post-1407307

 

Pro

https://forums.mydigitallife.net/th...te-upgrade-process.64770/page-75#post-1407681

 

There's no such an edition. It's either Pro or Enterprise.

 

You need to login to view this posts content.

 

How to accelerate the 40 mins wait? Please share. i had PC on almost all day, it didn't reactivate itself....

thank god we are not on Windows Vista/7 where we have home, home premium, starter, etc... 20 different versions to choose from lol

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

If you copy the genuine ticket, reboot, and then let the PC sit idle for 30-40 min, it will activate on its own.
Somehow, if you are using the PC, it will not try to rebuild the tokens. It will only do it if the PC is idle...

I had written that the 40 minutes wait would be shortened as I suspect that the tokens rebuilding with the script provided by mxman2k would do it.

 

ClipSVC uses it's own tokens to store HWID activation information (and activation of other Store products). SPPSVC tokens have nothing to do with it, you can rearm/remove them infinite number of times and ClipSVC will activate it even offline after license was downloaded.

If you need to reset Store license status you need to remove or rename C:\ProgramData\Microsoft\Windows\ClipSVC\tokens.dat (you need to stop ClipSVC service to do this). This allows also to activate PC that does not have Store license using "dirty" system cloned from another PC. After doing it you'll also lose a local license for any application downloaded from Microsoft Store/Windows Store that was not preinstalled.

 

i didn't know that, thank you for these information.

 

That is great info, thank you!

So for use of a image to deploy across PCs, should the image have windows NOT activated? Or could token.dat from clipsvc folder be deleted once the hard drive is used as off-line for image creation?
If those statements are wrong, then how should an image be created?

Thanks again.

 

Both statements are right.
If you have created an image from activated Windows then removing tokens.dat should do the trick and you will be able to use Store license on any PC. The not activated option also should work, because tokens.dat in that case probably will not have information about license for PC that was used to create image, but I'm not sure, it needs to be tested.

I personally would go with removing ClipSVC tokens.dat offline from image, because I have done something similar while deploying a bunch of PCs and it worked (I have removed the tokens.dat when system was running, but probably there will be no difference). This option has a caveat of losing license for not preinstalled UWP apps, but who needs them anyway?

 

Hmmm... so this explains what's going on! I have two backup hard drives (one 2.5" and one 3.5") that I use when servicing machines, while doing user data backup I use one of those to meanwhile create the genuineticket.xml and then try to generate the digital license... I'm using 1709 for that... I'd get an "unable to reach activation servers" error, or an outright failure. Didn't know about that ~40 min idle wait either to get it to finally activate.

Reused hard drives and 1709... So many unnecessary headaches lately! I'm downloading 1607 right now for this specific task, once a digital license is approved I'll then proceed with 1709 or whatever future edition is up next. I don't remember 1703 being this picky.

Thank you very much.

 

On most of my generated HWID's it instantly activated, only three times it needed a reboot. And all my HWID's on my main system were generated on other hdd's than it has now.

 

Yeah, same experience here. I've had many successful activations on 1703/1709 + same hard drive on different machines, generally no issues, one reboot at most. All my home machines' HWIDs generated on 10586 are still active and those had their hard drives upgraded to SSDs.

It's just that lately I've had issues/failures with that tried and true method doing the very same steps as I've been doing since 10586 as explained in the first post, and the quoted explanation above shines some light on what could be going on. I'll try 1607 for this particular purpose and see how it goes.