Windows 10: Distie put wrong version of W10 on my machine

A distributor built a machine for me and I asked for Windows 10 Professional 64bit


I did not notice when it arrived that he had installed W10 Home but given me the OEM licence key for Pro.


I spent 3.5 hours installing the clients software and setting up the machine and do not want to start again with a fresh install.


Is there a way that I can upgrade this unactivated Windows 10 Home install to Windows 10 Pro that I legally bought a key for? They key is on the machine.


Thanks


Steve

:)

 

Clean install of W10 not possible in Virtual Machine.


Please get a cup of coffee, lean back and think an answer for these two questions. Take your time, then check the answers below the questions:

Questions:

1. If you do a clean install of let's say Windows 10 Insider Build 10525 on a totally new computer which has never had an activated Windows 10 on it, does it activate?
2. If you do a clean install of Windows 10 Insider Build on a computer where the underlying Windows 10, upgraded from a qualifying old operating system has already been activated, does it activate?

Answers:

1. No, of course not.
2. Yes, of course.

Why do you think that a virtual machine would make any difference? You have tried to install Windows 10 on a totally new machine which has never had an activated Windows 10 installed, therefore the Microsoft activation servers block the activation due invalid machine ID. In the highlighted part in below quote you admit your mistake yourself, plain and simple, yet you when doing this wrong draw conclusion that even if done correctly it would not work:

What you have tried is essentially the same as if you took a brand new real physical PC without any operating system, which has never had any operating system, and then installed Windows 10 Insider Preview wondering why it does not activate! Virtual Machines behave exactly the same way; if you want to clean install Windows 10 Insider Preview and get it activated you must do it on an existing virtual machine, one which has already had an upgraded Windows 10 activated. This "computer", the virtual machine, its machine ID is marked on activation servers as valid and activated and it will of course activate.

Be it a virtual machine or a physical computer, you cannot activate a clean installed Windows 10 Insider Preview on a totally new machine. How difficult can this be to understand?

When clean installing Windows 10 Insider Preview on a computer which has already had a previous Windows 10 Insider activated, you do not use the product key! It will be asked twice, once before the installation starts and once after the last reboot to OOBE phase. In both cases you skip the product key and your Windows will be automatically activated.

 

Issues with W10 Mail App

Hi Frank,

To guide you in the right direction, let us know the following:

• Did you add your fsnet.co.uk (POP3) address as an additional account in W10 Mail App?

I suggest you to remove the account and re-add it.

I suggest you to try the steps provided in the link below and check.

http://windows.microsoft.com/en-in/windows-8/remove-account

Please get back to us with the required information, to assist you further.

Regards,

 

Clean install of W10 not possible in Virtual Machine.


@Kari

You can do clean install with windows 10 but it won't activate on Virtual Machine at least it didn't on mine. I followed the proper steps to do that.

Again I will repeat what I did step by step with some additions.

Step 1 Installed windows 7 retail on a virtual box, it activated without issue.
Step 2 changed the virtual box description to windows 10
Step 3 upgrade to windows 10 and it activated without issue
Step 4 backed up (So I could go back to it later)
Step 5 Removed windows 10.
Step 6 created a new virtual machine
Step 7 Installed clean windows 10 and it didn't activate and did that error code see below.


@night-hawk had a similar issue and got the same error code

Error code: 0xC004C003 with the specified product key being blocked

Night Hawk does it make a difference on what version of Virtual box that you are using?

My testing was done on Xubuntu using VirtualBox Graphical user interface version 4.3.26-Ubuntu r98988