Maybe a different product id and a different product key = a different activation and I would have no problem. Maybe I don't understand how Microsoft does it these days. īeen trying a bunch of different things during this to figure it out, like making a copy, selecting "I copied it" but once I went as deep down as creating a new vm and still getting the same product key I must say I'm baffled. Then I would not be able to upgrade any of my core machines either. I thought it might be I'm using NAT for all vm's and that would affect something but as they have different MAC's that would make no sense. Yes, I thought my method for getting the product key is wrong but when a vm is created from scratch there's no way that vm could "know" anything of a vm I just deleted. and the WIN10 product key is the same as for everything else. I have even created a new virtual machine from scratch with a product key I have never actually used before. Windows product id ( ! ) differs, MAC differs, memory amount differs, 32/64-bit differs. Problem is, I get the same product key for machines that are totally different (all on the same host though). Assume I have the newest version of everything (less than a week old, 12.x). I have about a dozen virtual machines I figured I should upgrade to WIN10 and then continue to use them as WIN7/WIN8 until I have sufficient time to deal with possible issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |