Install and config Win10 and apps on a VM then move it to PC

I still use Win7 and wanna move to Win10. But it's gonna take days to install and configure all apps I need. It's a troubling process as I'd become limited on using my PC while I do whole installation and backup.

I'm thinking then on doing it on a VMware VM. Then when all installation is finished I'd backup its partition and restore it on my PC.

My question is if if'd work. How would Windows behave upon being moved from a VM to a hardware PC. Would VM's drivers be a burden or just rest still and not cause any trouble. Would Win10 work as if it was installed there to begin with or would it be crippled and should I forget the idea?

Hikari

Posted 2019-03-10T07:05:24.050

Reputation: 268

You probably want to look into sysprep.

– jamesdlin – 2019-03-11T02:25:13.377

Also, your question is basically about moving a Windows installation from one machine (virtual or not) to another. See also https://superuser.com/questions/644862/move-existing-windows-7-or-10-installation-to-new-computer, https://superuser.com/questions/1205069/possible-to-move-windows-8-to-10-upgrade-installation-out-of-virtual-machine, https://superuser.com/questions/1027847/move-hard-drive-without-using-sysprep

– jamesdlin – 2019-03-11T02:34:31.410

Answers

Another easier way of doing this would be to have a dual boot or to boot on separate drives.

Dual boot:
Dual-booting Windows 7 and Windows 10 (with windows 10 installed first)
What should be the installation order for the Dual Boot Windows 10 and Windows 7

Separate drives:
Install Windows on separate drive WITHOUT dual boot

Ola Ström

Posted 2019-03-10T07:05:24.050

Reputation: 355

Yes, that helps but would still require to alternate. I can't be working on new Windows and use current one at the same time. That's what I wanna achieve by working on it in a VM. – Hikari – 2019-03-10T13:34:53.023

This might work, but might not be straightforward. There are some issues to be aware of:

Driver issues

While P2V (Physical to Virtual) is usually straightforward, what you are planning to do is the reverse (V2P, Virtual to Physical), which is not. As the underlying hardware changes from generic "virtual" hardware to your specific physical hardware, there might be issues with basic drivers, disrupting the boot process or subsequent installation of drivers for your specific hardware.

Windows 10 is generally good at resolving these kinds of driver issues but it might not work in every case. If you run into issues, you would need to use a tool like Microsoft Sysprep on the VM to prepare the virtual machine before moving it to new/physical hardware.

License issues

If you are using a Windows OEM license (if you are using a privately bought PC this is probably the case), you're not allowed to move this license to another machine (either virtual or physical). In this case it means you will likely run into activation issues before or after the V2P process.

Advice

There is a high probability the V2P process will not work as intended and will cause you to spend a lot of time troubleshooting. It might cost you less time to just bite the bullet, backup or image your current Windows 7 installation, and perform a fresh and clean Windows 10 install on your (physical) PC.

StarCat

Posted 2019-03-10T07:05:24.050

Reputation: 507