WPA = Windows Product Activation

BTW = By the way

BTW Try using Google when you don't understand an acronym.

No matter how you get your current version of Windows that is installed on your physical machine into a virtual machine you will have to reactivate it (WPA issue) and it requires you to have an additional license if you intend to continue to run the physical machine and the virtual machine created from the physical machine.

As far as Paragon Go Virtual is concerned it appears you didn't read what it said at the link provided and its documentation!

In short, you'd install and run Paragon Go Virtual on your Physical Machine to create a VMware Virtual Machine of the Physical Machine and then run the resultant Virtual Machine with VMware Player.  Nothing else to do as far as creating the VM is necessary, it will boot to Windows however because of WPA you may have some difficulties and this is not a VMware (or Paragon) issue, it's a Microsoft issue and you may need to directly contact Microsoft to resolve any WPA/Licensing issues.

Using Paragon Go Virtual doesn't require you to do anything with Macrium Reflect and it creates the VM ready to run in VMware Player by just double-click the .vmx file it created along with the .vmdk file it creates.  It is the shortest and fasted route to create a Virtual Machine of your Physical Machine and makes all of this nonsense of the discussion thread moot.

Also I do not like being misquoted and I never said "3) yesterday you told me: "yes, VMPlayer create a standard IDE/sata hdd interface"  I said "The Macrium Rescue CD, Linux CD/ISO Image, Rescue.iso does recognize VMware IDE/SCSI Disks out of the box! "!  SATA and SCSI are not the same thing.