Embedded Product Key (8.0) for 8.1 install

[pparks1]

Alright, my boot issue was a Paragon Backup and Restore issue. It was very easy to fix.

After restoring my image, boot from Windows 8.1 USB key. Repair. Command prompt. Run, bootrec /rebuildbcd

Then, reboot and the box will come right up.



Now, onto what happens to the actual key. To recap

• Take running box with 8.0 and run showkey.vbs (found in another thread)
• Install Windows 8.1 clean from MSDN media and use the dummy key in this thread
• Boot into Windows, run slmgr.vbs -ipk xxxxx.xxxxx.xxxxx.xxxxx.xxxxx (input the legit key from the host)
• Reboot with network connected and it will activate
• Run, Sysprep and choose Shutdown option
• I used Paragon Back and Restore to grab an image of the hard drive
• Restore the image on another 6430u that I have lying around.
• Boot from the Windows 8.1 USB key
• Repair, command prompt, bootrec /rebuildbcd
• Reboot computer into Windows 8.1
• answer mini setup questions, accept license, etc
• Optional: Ran showkey.vbs and confirmed that it's actually the embedded key for THIS laptop, it's not the same key that I had input before.
• Connect ethernet, go to Properties of THIS COMPUTER. Click on Activate Windows. In a few seconds, it will say "Thanks, you are all done".
• The box is now activated, reboot and the watermark will be gone.
• Optional: Ran showkey.vbs and confirmed that it's still using the embedded key for the actual laptop in use.

Moral of the story:
I was able to install 8.1 clean with a dummy key. I was able to change the product key back to the real embedded key. Was able to sysprep, then restore on another machine and it will activate (and it uses the other machines embedded key, thus my licensing is legit).

 

[SIW2]

Thanks for that pp. Wasn't sure what would be the result re the embedded key after restore to different machine .

Curious to know if a Paragon image (not sysprepped ) would have the same result.

 

[pparks1]

Curious to know if a Paragon image (not sysprepped ) would have the same result.

i tested that very thing and it still had the problem. Restoring on the same machine also had same problem. Windows 8.0 works fine. It's definitely a Paragon/8.1 thing.

 

[popeye]

This is what I've been looking for. The ability to get a clean install of 8.1, not just upgrade, with an OEM key.

pparks1, you da man!

 

[alphanumeric]

:thumb:

 

[SIW2]

I didn't expect it it have any result on the boot problem after restore.

I meant the same result re the key. I.E

a sysprepped image accepts the embedded key automatically after restore to a different machine.

Does a non sysprepped image also do that?

Curious to know if a Paragon image (not sysprepped ) would have the same result.

i tested that very thing and it still had the problem. Restoring on the same machine also had same problem. Windows 8.0 works fine. It's definitely a Paragon/8.1 thing.

 

[pparks1]

Does a non sysprepped image also do that?

That I do not know. I don't restore images on other hardware without it being sysprepped first.

However, I restored the sysprepped image on machine #2. Verified it was using machine #2's, key and it was. Then, I physically removed the drive from machine #2 and put it back into machine #1. I simply booted machine #1 and it came back up, still activated, and showkey.vbs shows that the key is the key from machine #1. So, it changed from 1 key to the other, without me doing anything and without having to manually activate anything.

 

[popeye]

So, can we get a step-by-step guide with the things we need to download first before we start, then the process?

I know I'm sounding like an idiot but I really want to be sure I have everything lined up before I attempt this. I have extracted my embedded key awhile back with the vbs script. I also lost track about getting the actual 8.1 ISO. I can download it as described in the retail instructions?

Yes, a bit confused.

 

[SIW2]

I also lost track about getting the actual 8.1 ISO. I can download it as described in the retail instructions?

No, because you have an oem key

 

[pparks1]

I also lost track about getting the actual 8.1 ISO. I can download it as described in the retail instructions?

Yes, a bit confused.

I got my Windows 8.1 ISO from my MSDN account.

 

[pparks1]

Well, the Windows 8.1 UEFI install has done something a bit wacky. After playing around with 8.1 on this laptop, I decided to simply set the laptop back to my standard Windows 8.0 image. So, I restored my standard image that I use on all of my 6430u's, and it won't boot. Same BCD errors as above, 0xc0000034.


So, I decided that I would take the Windows media, boot, go into repair, get a command prompt, run diskpart and issue the clean command to wipe everything from the drive. Then, I would just restore my image and I should be right back in business. Well, no such luck. Still booted up to the BCD error screren, 0xc0000034.

So, I'm a bit baffled right now as to what has occurred on the disk that seems to be hosing up what I have always done.

So, now I am taking the Windows 8.0 USB key and just installing the OS and making sure that it will then boot on it's own. If that is successful, I will then take and restore my image again and make sure that it continues to boot.


EDIT: After reinstalling Windows 8.0 manually and ensuring that it indeed can boot, I can now restore my Paragon images to that drive and all is well. So, Windows 8.1 does something odd with the UEFI boot stuff...beware in case this happens to you.

 

[SIW2]

Yes, that was what Paragon mentioned, tho they didn't attempt to explain what was going on. They just said they are updating their programs accordingly.

 

[popeye]

I also lost track about getting the actual 8.1 ISO. I can download it as described in the retail instructions?

Yes, a bit confused.

I got my Windows 8.1 ISO from my MSDN account.

Bummer. So basically, after my initial excitement, us OEM folks still can't do a clean install unless we somehow get the 8.1 ISO?

 

[SIW2]

us OEM folks still can't do a clean install unless we somehow get the 8.1 ISO?

That's right.

 

[Saltgrass]

[DEL]I was wondering, if someone with an OEM key were to install in Legacy mode, would it make any difference as far as the Embedded key? I will stipulate I would have no way of knowing if the OEM key itself could be impacted by installing in such a mode, but I would not think it would be effected. Or perhaps even installing the Preview and using the trick to download the .iso.[/DEL]

There are places to download the RTM .iso which are not torrent sites, so it could be used. But hopefully, the rumor about the 8.1 .iso being released this month is true.

Disregard, you will probably still need a valid non-oem key.

 

[Clintlgm]

[DEL]I was wondering, if someone with an OEM key were to install in Legacy mode, would it make any difference as far as the Embedded key? I will stipulate I would have no way of knowing if the OEM key itself could be impacted by installing in such a mode, but I would not think it would be effected. Or perhaps even installing the Preview and using the trick to download the .iso.[/DEL]

There are places to download the RTM .iso which are not torrent sites, so it could be used. But hopefully, the rumor about the 8.1 .iso being released this month is true.

Disregard, you will probably still need a valid non-oem key.

No actually all you need is a Install only Key when you clean install turn off auto activate. After your installed and booting up then activate with your OEM Key or Upgrade Key Etc. I myself used the $14.95 upgrade Win 8 Pro key That upgrade was from a Win 7 HP 64. I did not upgrade I clean installed using a Win 8.1 Pro 64 Retail ISO. You can goggle for these install only Keys they are legal and will not activate your product. They will only allow the install to complete.

 

[alphanumeric]

I also lost track about getting the actual 8.1 ISO. I can download it as described in the retail instructions?

Yes, a bit confused.

I got my Windows 8.1 ISO from my MSDN account.

I did that too, but also downloaded the other ISO though the download trick. The retail MSDN ISO is the RTM build. The other download is a custom GA build.

 

[theog]

Just test Paragon 12 Restore.
Error Code: 0xc0000034


than with SSR Desktop Edition,
on first boot, Automatic Repair run, than rebooted to desktop fine.

 

[SIW2]

Is the message something like:

The Boot Configuration Data file is missing some required information

 

[theog]

For Paragon 12:
RECOVERY
Your PC needs to be repaired
Error Code: 0xc0000034

For SSR Desktop Edition:
Boots to Automatic Repair first.