- #My windows key stopped working install
- #My windows key stopped working windows 10
- #My windows key stopped working iso
Instead, you write things like " it's a shame you guysĬan't accept that." Also, why do you answer now, almost 9 months later? I really don't understand that. Which I wrote down for you does not apply? You didn't comment on that. If that does not apply to you, I am afraid your partition is broken"
#My windows key stopped working windows 10
I tried to open a bitlocked partition that was encrypted using AES-XTS (the default encryption method of windows 10 v1511 and higher) on a downlevel OS like win7/8.1 or even on win10 10240. So, you have the same problem and you can assure that the previous comment of mine " the only time I saw a key not working was when If you reuse this one, it will only be seen by the very guys that are already active in this thread. If you created a new thread, it would be seen by the whole community. Ok, we could talk about it here, but it would have been better to create a new thread since maybe the mail accounts that subscribed to this thread are no longer in use after 6 years. You have a similar problem as in a 6 year-old thread. To protect my original data from any students that may want to go exploring, I just wanted to enable Bitlocker on my original Windows install. I tried one thing, installing an educational version of Windows to demonstrate liquid cooling and thermal electric cooling to a local school, while allowing them to game on this monster of a machine (dual GTX Titans, tri-monitor surround, etc) would be simple. Machine any more (powering it on once every few months) as the family and I enjoy no-computer-issues blissfulness.
#My windows key stopped working install
Moving from a MS developer of 20+ years over to Linux and macOS, I have become far more productive - since Windows 10 wants to install an update and reboot every day it seems. I know it sounds like I am venting, and I am. Trying to fix this - where I had family priorities instead. Right now, I simply lost an entire evening Or, setting #1 as the default boot version. I put my trust into Microsoft that they knew whatĪt this point, I will try a few hail mary's like encrypting the newer Windows #2 partition and trying to select the original #1. But nothing like this, where I was completely locked out before. I've had various issues with BitLocker over the years with TPMs on tablets and desktops. I also run several Linuxīoxes and VMs, all with various levels of disk encryption on multiple partitions. I have moved all other machines in the house to macOS on Apple and multiple odd encrypted strategies. You'd think Microsoft would be stable by now (will have lost about 1 years of baby pictures if I can't get this fixed). From within the #2 newer install, if I select the old #1 drive, it prompts me to enter the long recovery key - I enter it exactly, and it says Invalid Key. I can boot normally into the newer Windows #2 installation at the end of the disk. No matter how many times I EXACTLY enter that recovery key, I always get a blue screen saying unable to mount disk. It says no TPM module, and to enter the LONG recovery key from the USB stick. Rebooted and selected the old #1 installation.Asked me to back up my key, and I did on a USB stick.Thought this was part of the newer AES-XTS option and it needed me to reboot before asking me for password. It did NOT ask me for a password! I felt this odd, as I didn't have TPM on this machine (yet).I believe I selected "Used" not "entire disk" but, I can't remember. Rebooted back into Wind#1, the old Windows, and enabled BitLocker on this one drive.Note that Windows Boot Loader is now defaulting to Wind#2, as it was the version I just installed.
Enabled Developer Insider on this 2nd installation.
#My windows key stopped working iso
In the meantime: the only time I saw a key not working was when I tried to open a bitlocked partition that was encrypted using AES-XTS (the default encryption method of windows 10 v1511 and higher) on a downlevel OS like win7/8.1 or even on win10 10240. Geortge, please open a separate question.