|
I screwed up. Installed a technet edition of Windows 8 in Hyper-V, upgraded to Windows 10. Wrote down the 'new' key and deleted the image. Tried installing Windows 10 from scratch, but now neither the Windows 8 key or the 'new' Windows 10 key work. How do I fix this?
|
#
¿
Nov 22, 2015 04:18
|
|
|
|
| # ¿ Apr 24, 2024 23:21 |
|
|
From reading some articles trying to figure out what went wrong, I thought Windows 10 doesn't use product keys anymore? As in, you need a product key to install -- but after you install you essentially have a license tied to a particular hardware configuration and not the key itself? I though that is why I was extra screwed. As in, the key was now tied to a Hyper-V GUID that no longer exists. When I get back home I'll check what Win10 install media I was using. I downloaded it using the update Windows 10 update tool if that is a clue.
|
|
#
¿
Nov 22, 2015 05:12
|
|
|
Happy_Misanthrope posted:There has to be some install issue that they've detected...maybe? It's MS, who knows. Christ this organization is so schizophrenic. The whole reason I wiped was because doing it this way creates a lot of trash in a VM instance that you can't get rid of. Sigh.
|
|
#
¿
Nov 23, 2015 02:42
|
|
|
Are we still in a situation where upgrading from Windows 7/8 to 10 messes up the license keys in such a way that you technically don't get a new license key for 10, but you invalidate the ones from 7/8, meaning you are SOL if you need to reinstall or move the license to a new PC? Asking because I have some VMs on 7/8 and would love to move to 10, except for this issue.
|
|
#
¿
Jul 5, 2016 08:19
|
|
|
fishmech posted:This situation never occurred - the Windows 7 or 8 keys never get invalidated or messed up. However it's true you don't get an actual Windows 10 license key unless you buy Windows 10 outright or get a new computer with 10 on it. Thanks for the reply. So just to be 100% clear, I can do the free upgrade on any Windows7/8 PC, and go back to Windows7/8 at any time? What I can't do though is, after deadline, is re-upgrade freshly installed Windows 7/8 instances to 10 even if they were 10 before? I remember there being a lot of confusion over this, namely at the time (soon after the free upgrade) Microsoft was saying there was no key because the copy was tied to a hardware fingerprint instead. Is that actually true, i.e. I can install a fresh copy of 10 with no key on a computer that has been upgraded to 10?
|
|
#
¿
Jul 6, 2016 02:35
|
|
|
fishmech posted:Yes you can go back to Windows 7 or 8 at any time (though you'll probably have to fully reinstall them, if you didn't keep a backup. A backup is automatically created when you install Windows 10 but that will be removed from your drive after a while because it takes up a lot of space). You can also return to Windows 10 on a system that previously had the free upgrade, so long as your hardware doesn't change too much. So for instance, if you just change the graphics card out you'll probably be fine, but if you change the whole motherboard to another one it won't be fine. Do you know how the windows 10 upgrade works with VMs? Specifically, if I upgrade to 10 on a VM is that key now essentially tied to the VM image somehow?
|
|
#
¿
Jul 6, 2016 03:01
|
|
|
|
| # ¿ Apr 24, 2024 23:21 |
|
|
Installed the bash shell on a box where the Windows user I log in as is 'root', and I took the default option of naming the shell user after the windows user. Having the shell user be named 'root' confuses the Ubuntu subsystem really badly. Is there an easy way to reset it so I can give the shell user a less problematic username? About the shell in general -- this really is the future of getting posix tools working on Windows, but without good network support I think I'll stick with cygwin for the near future.
|
|
#
¿
Oct 1, 2016 07:00
|
|