For those who aren't already aware (because this has apparently been happening for along time already), you may encounter the following situation. I make note of it however as this is my first encounter of it: 1. Buy OEM hardware 2. Reformat HD per usual OEM bloat removal. Prepare a superior version of Windows key that you have (never been used license).

Windows Preinstallation Environment software included with this software may be used for boot, diagnostic, setup, restoration, installation, configuration, test. Driver Do Monitor Lg Flatron W1642s on this page. 2.4 How to create the AVG Rescue CD - burning ISO image. That is included in the Windows Server 2003 Resource Kit Tools (downloadable also from the. Copy ImageX to the appropriate spot in the newly created directory structure so that it will be part of the ISO image you create: copy “c: program files windows. You can then burn the file to a writable CD using standard CD-burning software, including the free CDBurn.exe that is part of the Windows Server 2003 Resource.

During OS re-installation process, notice that the setup never asked you to enter the license key. After installation, note that Windows is already activated.

Attempt to activate your unused license to unlock additional features (e.g. From base version to pro). Get an error message stating that the license key won't work. There is no way to alter the license key that is stored in the BIOS. It is possible to view it using BIOS tools or even use more commonly known programs such as Belarc. But there isn't much use in that.

We need a way to actually stop the Windows setup using this license in the first place. It is at this point I learnt that it is possible to exploit legacy Windows setup behaviour. Here's what you need to do: 1. Copy the content's of your Windows setup media (in the case of a CD) or extract it from the ISO (in the case of a DL). Once you have the folder structure, open the 'Sources' folder. Create a new text file and paste the following into it.

[EditionID] [Channel] Retail [VL] 0 4. Save and rename the file to 'ei.cfg' thus changing its extension. Depending on your boot media type, re-build the.iso with a program like ISO Creator and either extract & burn it onto a DVD or use a program like Universal-USB-Installer to create a bootable USB drive. Reboot your machine and boot from the media you just created as you would normally when setting up Windows. Note that this time, the setup process will prompt you to input a license key thus bypassing the BIOS version! Enjoy reclaiming control over the legitimate hardware and software you purchased. Hopefully this information will help keep you 1 step ahead.

At least until MS patches the exploit. It's a brave new world. EDIT: Updated to reflect extent of practice. Dude, welcome to 10 years ago. It's called, and it's been going on since the Windows XP days. Well damn, i've bought many an OEM machine over the years and this is the first i've ever encountered it. I guess it just depends which vendor you use.

Either way, it took me a while to find out a procedure that works to bypass it so hopefully this will be helpful to someone like me who, somehow, managed to bypass this 'convenience' for so many years. Although I guess a large part of that that is because for along time I was just building my own hardware - which I will revert to doing once again. Retail/MSDN/TechNet XP images didn't have the right files inside to use SLIC data. The full Service Pack downloads had the files embedded, but you had to put them in place yourself. Most OEMs distributed their own (customized) XP installers that used the SLIC data properly, but had their own extra crap rolled in on top. The availabilty of VL keys meant that most enthusiasts simply didn't have to give a shit about that though. With Vista and 7, I never ran into this as a problem.

Either the edition I chose to install matched what was stored in SLIC or it didn't and I was prompted for a key. I haven't had to do a clean 8/8.1 install on a PC with it shipped OEM to run into what you did as a problem though. The license key is NOT stored in the computer BIOS. The OEM install app check in the BIOS for the OEM manufacturer name and if it is not found or different than what is hard coded in the install app, then the Windows install fails. All of the normal Windows install apps check the volume name of the install CD/DVD and compares it to the hard coded install app data.

If the volume name is different then the install fails. You can change the install type from Home to Professional to Enterprise simply by burning a new disk with the appropriate volume name. The license key is NOT stored in the computer BIOS. The OEM install app check in the BIOS for the OEM manufacturer name and if it is not found or different than what is hard coded in the install app, then the Windows install fails. All of the normal Windows install apps check the volume name of the install CD/DVD and compares it to the hard coded install app data. If the volume name is different then the install fails.

You can change the install type from Home to Professional to Enterprise simply by burning a new disk with the appropriate volume name. Where is this 'install app' located?

I've run RWEverthing on my system and sure enough, found my OEM Win8 license key embedded in.something (at least I thought it was my BIOS). I wasn't using some custom Win8 image, I was using a vanilla.iso. Sterling_Aug that is only true for windows 7 and below, where one could install any version of windows (i.e. Pro, home, etc.) just by using the appropriate OEM windows key.

I believe Windows 8 does not use the same SLIC method. It appears that the bios stores the OEM Windows key, and the installer reads it from there if one attempts to install a different version it will fail. I ran in to the same issue as the op, you can also get past this by creating a file called PID.txt in the 'sources' folder, an just stick your legitimate product key as follows: [PID] Value=XXXX-XXXX-XXXX-XXXX-XXXX.

Ok, sorry to wade in here with my cluebat on my first post, but there's a lot of misinformation and almost-not-quite in this thread, and I feel compelled to educate. My apologies. OEM activation down through the ages, oldest to newest, with a particular focus on how it can be used and abused, with customer/user OSes as the default: Windows 2000 and prior: OEM protection is pretty much a joke, just changing the product ID to the right numbers removed all serial prompts. Activation not invented yet. Windows XP: Online activation and OEM SLP bios locks: Commonly defeated by pirates by simply using VLKs. VLKs were not checked online in any way in XP/2003, so this was ideal.

Later many/most VLKs got blacklisted, but just generate more! Royalty OEM activation at this point used generic XP keys which simply provoked OEM validation.

OEM validation consisted on checking the oembios files. Oembios.bin was a somewhat obfuscated and MS-signed file describing memory locations and copyrighted/trademarked data to look for at those locations. If the OEM check scanned the appropriate memory addresses and found one or more matching strings, activation was done, OS was activated. This wasn't widely abused by pirates because VLKs were easier, but towards the later days of XP, it grew in popularity because it was easy to abuse, and hard for MS to check and invalidate. Windows Vista: First generation ACPI table locks (SLIC): With the lessons learned from XP activation and the abuses thereof, Microsoft decided that a more active approach was needed in later OSes. Starting with Vista, VLKs as they had been were over.

There are no longer any 'magic keys' which allow an unlimited number of offline activations. Volume customers (businesses) were steered towards KMS and MAKs, which are useful but not for Royalty OEMs and/or pirates. Since the old VLK path was now fully locked off, pirates now looked into Royalty OEM methods.

Microsoft had observed some limited abuse of the old oembios system in the latter days of XP, and they wanted a new, more tamper-resistant method. SLIC was a custom ACPI table that contained a public key encrypted OEM certificate.

When Windows installed, it could be given certificate files with appropriate OEM information and public keys. The certificates themselves were signed by a Microsoft private key to resist tampering. The Royalty OEM process was triggered by use of a generic OEM serial number, common to all computers sold by a particular OEM. Once an OEM serial had been given, the system firmware would be checked for a SLIC table, and the contents compared to any and all OEM certificates that had been loaded by Windows. If the SLIC table was present, and matched a signed certificate, Windows would activate, completely offline.

Many BIOS modifications were used to exploit this method, from initial ISA module loaders to rather complex ACPI edits. Windows 7: Exactly the same as Vista, just the certificate version was increased from SLIC 2.0 to SLIC 2.1. The system had not been successfully exploited by many pirates, partially because bios modification was more difficult than prior methods, but also because Vista was widely disliked. With Windows 7 being massively more popular, BIOS modifications to exploit SLIC became more and more popular.

As the tools advanced, the process became simpler and easier to apply. Microsoft did not overlook this, and prepared a third generation of OEM activation. Windows 8, 8.1, 8.1u1: SLIC 3.0. This system is a further development and refinement of the previous SLIC 2.0 and 2.1 systems. Windows 2012, in fact, uses SLIC 2.2 with no other changes from the Windows 7 methods, precisely because server OEMs did not want to take on SLIC 3.0 for small volume markets. Windows 8 uses a new generation system, looking for an OEM ACPI table called MSDM.

The MSDM table contains a hardware hash that matches the machine it is installed on, along with a full OEM Windows key, which is specific to the machine it is installed on. There are no longer generic OEM keys that will trigger OEM activation, each OEM machine has a unique key. No system is perfect, and MSDM could probably be overcome by pirates if there were no other methods, but since there are alternatives, attention has focused there. Specifically, local KMS server emulators are very popular for the purposes of Windows 8+ and Office 2010+ piracy. To further refine my post and get a little closer to OP's point, some additional information on Windows 7 and Windows 8 OEM licensing: With Windows 7, OEMs generally had one key for each major product version (Home, Pro, etc), and you could change versions by simply using a different OEM key. The BIOS certificate (SLIC) was specific only to the OEM, one SLIC was used for any and all Windows versions.

With Windows 8 and SLIC 3.0, there were not generic OEM keys in this way. Since each machine had a unique serial embedded into the firmware, it was possible to determine Windows edition as well as type/OEM from the firmware alone. If your new laptop has a Windows 8 Standard preinstalled, and you've purchased an OEM System Builder (OEMSB) copy of Windows 8 Pro, you will encounter the problem OP had. Installing from Windows 8 Pro OEMSB media, the installer detects the valid Windows 8 non-Pro MSDM table, inserts that key, and installs non-Pro. You are not given any opportunity to override this.

You are also generally not allowed to change edition easily post-install with the OEMSB keys. In order to keep your install media from using your MSDM key, the methods mentioned here generally work.

By creating an ei.cfg file and adding it to your install media, you tell the installer that it is not OEM media, it is retail. Since retail does not have MSDM, it never checks for it and will instead ask for the serial to use. Likewise, forcing a PID via pid.txt will insert your OEMSB or retail key before the installer does the edition (retail/OEM/VL) check, so that works as well. Sphynx - You had most everything correct. Congrats on figuring this all out by yourself! It's not an exploit, though, it's MS's backdoor designs, so don't worry that this will ever go away. Ardax - As you can see in my posts, it's a little more complex now.

With SLIC 3.0, it can force a particular edition of Windows, so this info can be handy if you're installing 8 Pro onto a machine that came from the OEM with Win 8 non-Pro, for example. Sterling_Aug - Sorry, but you're just plain wrong. With SLIC 3.0 and MSDM, there certainly is a complete and human-readable product key in the ACPI table. You've mixed up info from OEM SLP, SLIC 2.0-2.1, and SLIC 3.0.

Also, Windows edition hasn't been determined by the volume name, not ever. There are other places and switches on the media to set that, ei.cfg is the common one for Vista+. HellDiver - ei.cfg changed the way it was used after Windows 7. Windows Vista and 7 both had an ei.cfg by default, and removing it caused the install to ask what edition to install.

With Windows 8, it's reversed. If there is no ei.cfg file, Windows 8 will look for SLIC 3.0 information, and if it isn't found, it'll ask for a key. If you create and add an ei.cfg file, you can change the install media from OEM(default) to retail or even Volume Licensed. That's what is done here, by creating an ei.cfg and tagging the release as Retail, it skips the step where Windows Setup looks for SLIC 3.0/MSDM info, and goes straight to the next retail step, where it asks what edition to install and then prompts for a key. It's generally frowned upon to post to a thread that's nearly 6 months old, but if ever there was a good reason to do so, providing a thorough background on the issue and fleshing out previous 'trial and error' discoveries is certainly it.

That was one of the best first (and second) posts I've ever seen. Welcome to Ars Technica!

EDIT: Also, the increasing sophistication of Microsoft's attempts to guard against OEM license exploits certainly explains why so many pirates found shelling out a paltry couple hundred bucks for a TechNet subscription (and its juicy, totally-legitimate licenses) a much better value proposition. Which thus explains why Microsoft neutered and eventually euthanized TechNet. Thanks for the detail, Forge64. Just to add my own recent experiences, since I've wiped the OEM installs on two laptops (Sony and Lenovo) and had some issues: - I tried installing with clean 8.1 install media (probably a Technet version).

During installation, the BIOS key was not found, as far as I can tell. Without using Belarc to get the key before wiping the computer, I found no way to get Windows installed. - If you specify a version in ei.cfg, the installation doesn't ask for a key. If you don't, you can enter your key (or a temporary key, which are sometimes posted on the internet) to get past this step.

I found the key I extracted from Belarc was rejected during this step (possibly because it was an 8 key, not 8.1?) It worked after installation to register and activate Windows later. Thanks everyone! I normally don't necro, but this thread got under my skin, and I felt compelled. MartinH - Actually, your media did detect and use your MSDM key, it's just that 8.1 and 8.1 spring update won't activate at install time with an 8.0 key, which is what all the OEM machines I've dealt with have had. My Dell Precision M4800, ordered a few weeks ago, came with a factory 8.1 install, but the MSDM key is 8.0 RTM, I'm guessing that's to make reinstalls simpler, since I can use any media, and it'll update to 8.1/8.1SU via Windows Update. For my own personal reinstalls, I'll pick an edition in ei.cfg, install, read the MSDM key, install that one, and Windows sorts itself out online.

If I don't have prep time, and I have to use my usual media, I'll use the GVLKs Google turns up to pick an edition and install it. I'll switch to the MSDM key and let it activate after install.

EDIT: Also, the increasing sophistication of Microsoft's attempts to guard against OEM license exploits certainly explains why so many pirates found shelling out a paltry couple hundred bucks for a TechNet subscription (and its juicy, totally-legitimate licenses) a much better value proposition. Which thus explains why Microsoft neutered and eventually euthanized TechNet.

Yes, at this late date it's very easy to draw a line from the first activation, through to the refinement and lockdown of OEM activation, straight towards TechNet getting the axe. If I had to guess, MS will go after KMS next, but that's a slippery slope. Agitate the IT support staff enough, and pushback against OSX/Linux/etc starts dropping off. MS would be very ill-advised to attack any other traditional Windows supporters, just to attack piracy. Thanks to everyone, especially Forge64, for the education on this topic. I've been looking into this for about a week and have tried all the approaches I could find to do something that I've done easily many times before: install a new copy of Windows on a larger hard drive in a laptop. Despite all my efforts (bootable USB drive with licensed Win 8 image, PID file, ei.cfg) I cannot get my Toshiba L55T to allow the installation of Win 8.

I don't want to use the pre-installed Win 8 on the original hard drive because I believe it's compromised. If it sounds like I'm at my wit's end it's because I am.

Any suggestions will be proundly appreciated. Sorry if I'm prolonging a thread that should have been retired, but I didn't have anywhere else turn. If you are like me and have a licence key, but you don't know what type it is (retail, OEM. Volume etc) Then i used this great app that can tell you what Type your licence key is and the vendor that issued it (Dell, samsung, HP etc) go here The Ultimate PID Checker Download ir (RAR) use 7zip (Free download to unpack it) It runs without Installing (portable) For me I confirmed it was an OEM licence -- Dell --- so run Any Dell OEM disk to repair (Same OS disk) I had to also use (For my particular case) Its too complicated to make any other notes (as your case will be particular to you) Its not easy but i did it. Thanks to all who are so knowledgeable here. Noobie to ars technica but hardly a n00b. Maybe I am asking a dumb question: I am NOT trying to beat the OEM licensing, I am just trying to reinstall 8.1 Pro on a Lenovo W540 sans bloatware.

[Note: I have many legal copies of Windows, all versions; I am just trying to get this machine to work without the crapware.] A friend bought the machine, settings may be mangled, etc. And of course no installation media.

I partitioned the disk and did successfully get a retail 8.1 Pro to install [mine; not to be left on this machine!]. Used my key, no problem [seems the general subject here turned inside-out].

First, a slight digression about installation with partitions and Windows 8: On my own machine, I want to have XP, Vista, Win 7 Pro and Win 8.1 Pro so I can support a freeware application extension I wrote [for some other freeware!] that depends muchly on the cosmetics of the desktop. [That machine has all but 8.1, and that's not for this post.] When I install Vista or Win 7, if you boot to the install disk, you wind up with this twisted configuration where the partition you choose is 'proclaimed' drive C. As a result, all partitions lower than the reality of that partition are 'off by one'. [C: is D:, etc.] To get around this, all you have to do is boot to any existing O/S and run the setup.exe on the install disk. When you get to the similar portion of the install, you get a subtle difference in the screen with the partition choices: Instead of just partition by number, you get the actual logical volume as well! Thus, for example, I was able to install Vista on E: and Win7 on F:, etc.

When you do this with 8.1, from the install disk you get the same problematic choices [that will be 'off by one'] but if you run the setup.exe, it works a bit differently: Instead of it asking you to choose, it instead does an automatic upgrade of the partition you are/were booted to; the old O/S is gone [and the files saved in Windows.old. However, it is otherwise properly behaving in the logical drive letters sense. Thus, unless anyone has any ideas regarding this, the only way to do it is to first install a 'sacrificial' system to get over-written by the 8.1 install. [If that's the best that can be done, so be it, but it is a time-waste.] Back to the main reason I am here: I cannot get the 8.1 disk en_windows_8.1_with_update_x64_dvd_4065090.iso to accept the product key I got from Magical Jerrybean on the factory install C: drive to pass [but my retail key works fine]. What do I need to do the install so it doesn't ask me for a key and uses the key in the BIOS? Do I need some other media [and if so, what is it and where do I get it?] I hope my question isn't a dumb one.

[From what I've read, this site has a lot more 'hospitality' than some other 'expert' sites [which I won't mention even though I am a very long-term member of one]. On my own machine, I want to have XP, Vista, Win 7 Pro and Win 8.1 Pro so I can support a freeware application extension I wrote [for some other freeware!] that depends muchly on the cosmetics of the desktop.

My first inclination is to say: 'Do this in VMs' unless you've got a really good reason not to. Most modern VM software will let you define multiple virtual displays of whatever resolution you want -- which is far better for testing than being limited to whatever your display currently supports. I cannot get the 8.1 disk en_windows_8.1_with_update_x64_dvd_4065090.iso to accept the product key I got from Magical Jerrybean on the factory install C: drive to pass [but my retail key works fine].

What do I need to do the install so it doesn't ask me for a key and uses the key in the BIOS? Do I need some other media [and if so, what is it and where do I get it?] If I'm reading Forge64's posts correctly, you simply need to remove the ei.cfg file from the installation media. That should force it to read the SLIC 3.0/MSDM data and use the embedded OEM key to install and activate. If you're prompted for a key anyway, just skip that step in setup and it activate once you get through Setup. Thanks for replying to me. I don't really want to get involved with VM's both on principle and also it's merely a sample of what I do. I already have my *own* machine doing all but 8.1 [and 10; never done anything in the new O/S at all].

This all works fine. [It takes awhile, but it is done; repeating it again?

Who knows; addint 8.1 on top of it I already know how to do, but the question within the question is what is the best way how given my experience; I know, it's confusing]. My display is not a problem as I am quite adept at dealing with all resolutions, etc. Because I am somewhat vision-impaired. [I didn't want to mention it; it doesn't stop me; part of this is to prove it DOESN'T stop me.] No, you have it incorrect. Let me go through this again: When you install these systems BOOTED to installation media, you get an unacceptable half-assed 'solution': Lets say I want to put Win 7 on drive H: and have it actually *be* drive H. If I select the partition BY NUMBER when booted to install media, that's all you get [which is NOT enough]. The outcome is a system in the partition all the OTHER operating systems see as drive H: but it identifies ITSELF as C.

As a result, the REAL C: [as reckoned by all the other systems] is D:, the real D: is E:, etc. [if there are any drives higher than H: in the example, they are fine]. But this is avoided only by NOT booting to the install media. Instead, you boot to any pre-existing operation system that qualifies [such as Vista64 to install Win7-64] and run the setup.exe on the install media. When the analogous part of the installation process gets to that part, the screen is DIFFERENT.

Each choice of partition shows not only the same partition by number, but also the drive letter in the context of the booted system. Thus, in the same example, I am installing to the same partition number, but it is also drive H: [NOT C:] and when the installation is done, it will come up on drive H: as expected. The process is as 'extensible' as needed. In earlier machines I had such as WinXP on F: and also on G: so one is a maintenance system for the other. There are malware situations where an infected system cannot diagnose itself [stealth viruses running the show] and by booting to the other system [hopefully not infected] the malware can be located; the previous attempt to find malware with the same set of programs fails to find anything wrong.

[This is from experience, not merely a theory. Think of those who have to pull the hard disk out and take it to another machine to get rid of nastier malware; it's the same idea]. So, this is why it is NECESSARY to NOT boot to the installation media.

It doesn't work unless you are actually WANTING to use drive C: [Only one can get that 'honor'.] Now all that said, Windows 8,1 will not cooperate AFAIK but if you also install a 'sacrificial' system on the partition where you intend to put 8.1, then boot that partition and then run setup.exe from the installation media for 8.1, it will 'upgrade' the partition to a complete 8.1 install with the old files in windows.old directory, etc. Thus, it does get the job done, but it needs that time-wasteful step.

If you boot to the installation media, you get the same exact [and wrong!] choices that provide exactly the same wrongful outcome. So far, unless someone has a 'better way' I am not so much seeking help on all of the above as much as showing how it gets done [notwithstanding the 8.1 part of it seems avoidable, but how, if at all.] Back to the main reason I am seeking assistance: That media does NOT have an ei.cfg file, and the W540 has the embedded key; it's stated in the BIOS as '0B98401 Pro' It's how Lenovo factory-installed the 8.1 on drive C: [which is a bit mangled; I want to reinstall it and benefit from bloatware removal]. Yet, it won't take the key Magical Jelly Bean indicates is in the pre-installed system, and WILL take my retail key [and Magical Jelly Bean indicates my key is in effect in my installation]. Note: I've done the 8.1 installation 'both ways' in terms of booting to the installation media or running setup.exe when booted to another system.

It doesn't change the situation; it only likes my retail key. Since the ei.cfg file is not present, this seems to defy all of the conclusions here. Also, this particular disk [which seems to be the proper one; anyone familiar with it?] apparently you CANNOT leave the key out [as in Vista and Win7]. [Is that perhaps part of the problem?] Thus, I postited that they used some other form of install copy of 8.1. Since this is a UEFI and securesafe-capable BIOS [I've tried I think most if not all of the variations] perhaps that is the missing factor.

But I'm no expert on that aspect of things; help! Thus, if this is the wrong media, what is the 'right' media? Or what settings should I try in the BIOS [or both]? Btw, en_windows_8.1_with_update_x64_dvd_4065090.iso is also known as SW_DVD9_NTRL_Win_8_1_64BIT_English_2_Win_Pro_X19-40141.ISO depending on where you get it [the former is available on several websites; the latter is MPN/Technet notation]. Note: I have already backed-up the machine as I got hold of it and I restored it to another hard disk and it booted normally, all this before partitioning, etc. I can do anything anyone wants me to try and report back on what occurred, etc. This system does work, but I cannot reinstall it; counter to the entire thrust of this thread.

On partitioning: I do most with Easeus with one exception: Easeus will not delete the C: partition, although it will allow resizing it. For that function alone, you can delete C: with mini-port tools Partition Wizard and the free version can make a bootable CD; with Easeus yuu need the 'pro' version for that, etc. But once you have one good partition on the machine, Easeus can be run from whatever system you install [XP and up are acceptable to Easeus]. I solved the problem, stumbled on the answer by nosing around related topics regarding the ei.cfg file, etc.

It turns out this is RETAIL-ONLY media and thus the problems mentioned do not apply. It also means that OEM installs cannot work at all.

[I also have a retail 8.1 key and it liked that fine, but the W540 in question comes with 8.1 Pro.] By downloading the Microsoft Windows 8.1 Media Creation Tool, it is possible to either create a USB drive or an.ISO. I chose the latter and used IMGBURN. The USB drive method is also more suitable to deal with creating the ei.cfg file. [This release does not have it.] [Although some ISO modding tools exist such as Gburner. Make sure they can work with the above 2GB size needed.] However, for this purpose I don't want the file; rather I want the Windows 8.1 install to find the BIOS-based 8.1 Pro key. The ISO has a volume label of ESD-ISO. It DOES support OEM installs and apparently retail as well [but I haven't tried that yet; it would be handy if one size fits all, etc.] The 8.1 install never asked for a product key and created a bloatware-free install of 8.1 solving the problem.

But I went further: As I explained, you can install 8.1 on a drive other than C: but not the way Windows 7 allows it. Thus, I put a temporary 'sacrificial' Win7 on the drive, then booted to it.

It then was used to run the setup.exe in the root of ESD-ISO and after many reboots, Windows 7 was replaced by 8.1 using the BIOS-based key and properly showing as on drive H: [that's the one I was testing on; too many systems on this machine! A final pass will pare it down a lot.] When you have a lot of systems installed and the last one is 8.1, you see the 8.1 version of the boot manager screen which is mouse-driven [but can be navigated with keys]. If you install Windows 7 [or Vista] last, you see that screen. [I also have Dual-Boot Pro which forces the pre-8.1 screen. So far, I have no way to choose the 8.1 screen other than to start an 8.1 install [which need not finish.] So, I have solved the original problem, and of course learned some stuff as well. Sharing the information here, etc. Now all I have to do is delete a very large Windows.old directory. Install Block Erupter Windows 7.

My friend has some interest in Windows 10! Thus, I am not 'done' yet. Thus, I will be installing either yet another Win 7 or Win 8.1 [now that I know how!] to be the sacrificial system that gets upgraded. [I am being presumptive that the process doesn't get worse in Win 10, and is only as 'simple' as how to get 8.1 installed on a partition other than drive c.] Anyone who has done battle with the nastiest malware will demand the answers to whatever questions are needed to have at least a maintenance operating system. I suggest all think that over [not saying which two, just that it ought to be two independent ones]. But unless you buy into this silliness that my system is drive C: [no matter what else that screws up] you have to go with something such as what I did.

[Or be prepared to pull hard drives.]. A) I do lots of different things, including countenance of many systems, and I do not want to get involved with higher-end systems necessitated by VM overhead; some of the machines are quite low-end, and the programming work I do is in many cases for them; thus, I need real-world situations. B) I do lots of things in general in a different way, and that includes multiple installation of operating systems; as I explained earlier in the thread, if you do not have at least two operating systems, you open yourself up to being very badly hit by very badly behaved malware that cannot be removed from a one-system machine. Your choices are to remove the hard drive or have multiple systems.

I find the latter preferable to the latter. Beyond that, it's personal preference as well. I'm sorry, but I completely disagree on some of your basic assumptions, including what you have determined are 'low-end' systems. I have viable systems for this application I develop that cannot run Vista, yet are perfectly fine for the purpose.

The VM sloth on such systems is intolerable. I suggest you take a longer view as to what machines are viable and low-end. You seem to be perceiving all systems as being 64-bit and at least 40% of the latest model's capability; what I work on [and others actually use] belies that theory.

To each their own; I am not attempting to 'coerce' anyone on any issue. Malware happening is quite real; VM might help, if it could be tolerated to be sure, IF it were acceptable at all. And once your host system gets hacked, you are in the same exact situation I describe. So, unless you do literally everything virtually, there are some notions here that do not hold up. As this thread is still alive and kicking i'm going to lay my problem here for you people. Try to help me out.

I've got this new Lenovo G50-80 laptop which came with Win10 home pre-installed. I have a very much legal Win 10 VL Pro key and I want to get Pro.

I go to the store app and select that I have a key. I'm asked to enter it so they can verify it. The app says everything is hunky-dory and you, my lad, will get Pro.

I say ok, on with it. When everything is done and I have restarted to my newly upgraded Win 10 Pro, I see that windows is not activated because the key ain't for this edition of windows (error 0xC004C003). The windows support guys think its because of the conflict between the Key in the UEFI which says 'this shalt be Win 10 Home OEM' and my key which says 'but master, i'm Win 10 Pro VL here'.

I know the problem can be solved by just doing a fresh install using the PID.txt method, but I have configured the OS the way I like it, and it has downloaded gazillion updates over my slow internet that I'm loath to lose. Is there any way to solve this without fresh reinstall? I do know the key works because I helped my colleague use it on his non-UEFI laptop without any problem at all. Windows support can't do anything today 'cause it's sunday and the really knowledgeable people aren't in.

1 - Open C: tokens.dat in a hex editor - I have used the excellent tinyhexer. 2 - Search for text OEM Certificate (Ctrl+F, select/tick the Find Text and Ignore case boxes and click on Find).

3 - Manually scroll upwards and locate the text proceeding the OEM Certificate string located in step 2. 4 - Now manually scroll down and find the text string directly following the OEM Certificate string located in step 2. 5 - Now highlight from (and including) (step 3) to (step 4) 6 - Copy the highlighted text (Edit >Copy) 7 - Paste into a new file (File >New, followed by Edit >Paste) 8 - Now save as oemcert.xrm-ms file (File >Save) .

But the Dell Branded media that I have skips all options to repair installation, as described in this KB Recovery console is not a solution as far as I'm aware as I have to reinstall to re-activate with the correct key. Right now we cannot activate as someone entered a key from another server by accident and the CHANGE PRODUCT KEY option in windows would not accept the code, so MS said we had to perform a repair installation. Any other links to where i could find Dell branded media to attempt repair? Sold out on the link you sent. Okay figured out how to do it. I burned a downloaded copy of standard windows 2003 SBS install disk, not Dell's version, I booted to that CD and then at the first screen where you can choose recovery console or hit enter to install, I swapped discs over to the Dell Media, THEN i hit enter and continued so it skips all the stupid scripts that Dell wants to auto-install with and then uses the Dell Media to copy files. Then when install continued and I get prompted for my product key, I knew it was different because the graphic they used to represent COA was different!

Then I entered my Dell-provided serial and it took it! All should be right in the world shortly. Thanks so much for the advice, everyone.