Has anyone been able to test this? https://forums.mydigitallife.net/th...odename-sun-valley.83555/page-77#post-1669002
Try this [DISCUSSION] Windows 10/11 Insider Preview Build 21996.1 (PC) [FAST/Dev Channel - co_release] [LEAK] | Page 25 | My Digital Life Forums Post #496
I have an old Dell Inspiron 15 N5050 laptop, with dual boot Windows 7 Ultimate and Linux Mint. Intel(R) Core(TM) i3-2370M CPU @ 2.40GHz 4.00 GB RAM I used Option 2 of the 21996 Boot And Upgrade FiX KiT v1.3 to create an ISO and burned it to a USB drive. It wouldn't work on boot so I just let Win7 load and then ran the setup.exe off the USB to install Win11 on top of Win7. It took about 30 minutes or so to install but it installed fine without any problems. I activated Win11 with the latest KMS_VL_ALL_AIO and everything seems to be running fine so far. I'm going to keep it for now to play with it but will eventually format again and reinstall Win7. \m/ (-_-) \m/
@Enthousiast I've been playing with Win11 and I suspect that there's just no way to use the old win8 recovery partitions. There seems to be a way within Windows to create a recovery drive. It's accessed through Control Panel -> Security and Maintenance -> Recovery -> Create a Recovery Drive How this compares to the normal renew function I don't know. Does it save your documents and registry settings? I have no idea. Anyway on Win10 and beyond the recovery partitions are borked. I am going to do some work on my diskpart/setup script to warn about this and test on the international stuff. I don't have any non-en-us keyboards, but I can set my vm to non-en-us keyboard and system settings and see how the script functions. I've been thinking about your script installer though. That's a very clever bit of scripting. I bet you could use that basic method to make a boot.wim and winre.wim DaRT installer if you haven't already.
no it isn't. TXT implies TPM is present, but is not required to be enabled for TPM to be used. These boards obviously have tpm locked on or under an entirely different name.
It's part of certain Intel CPU's not Hardware on a Motherboard: Trusted Execution Technology, (TXT), is a feature available in some Intel CPUs, that provides a "root of trust" which is enabled in the CPU hardware itself. TXT provides a mechanism to check whether or not running software has been modified, and can stop the execution of the software if these checks fail.
Hi guys. how are you feeling today? I hope you are well. In a Germany website I found a tutorial with photo. And say step 1 register to insider preview, step 2 select dev channel, ect ect steps. At step 12 you have from Windows Update the windows 11
Is there a significant boost of performance? Because I'm using Windows 10 LTSB 2019 and runs flawlessly on my machine with 4GB of RAM, no wasted RAM or annoying features. Is it worth the upgrade?
I'm not moving any system I maintain to 11 until 2022. I have a few test systems using it for now. Its mostly just slightly different UI for now. I can't tell a difference at all on any of my systems other than the really old one, that one stutters a lot of 11.
Yep works, I Brought up X:Boot and typed in regedit, Then Manually entered it. don't enter it into the registry until you get to the error, then go back 1 screen, I did at the beginning and it did not work.
The warnings suggest you have an iso that does not match the official leak. Perhaps it is malformed. Find the sha-1 sha-2 or crc and verify with a hashing tool such as hashtab. If the iso is malformed, the programs to try to work with it will obviously fail.
No, the SHA 1 was checked before attempting this bare metal trial. I think the warnings relate to the Windows 10 ISO I used. Just guessing mind you, or I wouldn't be looking for guidance.SHA1 = 3b6da9194ba303ac7dbbf2e521716c809500919c Might try a different 10 version. Suggestions welcome, thanks
Hmm, well the more recent the Win10 version the better luck you would have, but honestly you shouldn't have any problem just using the 2nd option. I will note that sometimes if you bury files really deep in folders, scripts like these can cause problems because of the 256character limit problems on file paths for cmd prompt. If you think that might be the issue you can try just making a folder like c:\work and try that.
Yes, that is doable. I was issuing the command in a distant folder. Time for another experiment, cheers
I am back on Windows 10 as the current leaked 21996 build has serious IPv6 problems. It routinely loses IPv6. There are sound stutter in games and my PC randomly starts in the middle of the night.