Try listing drives/partition using diskpart (Shift+F10 to open cmd). Happened to me in various builds over years, on various hardware, disks are working (no driver issue) just the GUI installer doesn't list them. (can be installed via dism+bcdboot)
Have to say, upgrading to 26100.2 has been smooth sailing so far.. I really like it, nice and snappy!
Hello I didn't "follow", it's possible to install this build on a non-compatible PC ? If so how (as with 23h2) ? Thanks
I tried quite quickly (bypass with NTLite) but it doesn't seem to work on a clean install (old laptop, CPU does not have SSE4.2) It displays the Windows logo then it reboots after a few moments (like this in a loop) No worries with the 23h2 I would look in more detail or wait for the ISO provided by MS for further testing
Still I have some issues on Build 26100: Unable to enter PIN instead of Password when logging in on Safe Mode. https[://]aka [.] ms [/] AApyjss Crash when selecting "Disable driver signature enforcement" on Windows Startup Settings. Remove [] for the Feedback Hub link.
My understanding is 24H2 wont work with really old computers that dont support SSE4.2 or the like. Like when 86 CPU.s went the way of the dodo, well the same has happened to old CPU's. Thats progress. Mind you, it would have to be a REALLY OLD computer. ALL OTHER BYPASSES STILL WORK
I can confirm the SSE4.2 requirement for build 26100. Until now all W11 versions still installed fine on older processors (using direct apply and such). I also tested the new 26100 ADK PE boot.wim, this still boots fine on older systems. One of my museum pieces is a Phenom II 1090T 3.2GHz system with 16gb RAM and other nice additions, all Windows 11 builds up to now were running just fine, but now with build 26100 the fun (...) stops. Maybe there will a change or fix to this, but I must admit I don't think this one will be easy.
Even if you select a keyboard at the beginning of the installation, it is not reflected. All the way from 26100.
There will be NO BYPASS for this, so dont hope for one. The SSE4.2 (and like) requirement is basically how the processor "thinks". Its how it processes EVERY PROGRAM running on the computer. All the programs in 26100 and now on are written with the code, so older processors without SSE4.2 cannot read the program. Again, this will only affect REALLY OLD COMPUTERS, the vast majority of people are unaffected.
SSE4.2 is a thing since 2008 intel cpus and all ryzens(just because I don't consider the pre-ryzen CPUs even worth mentioning). So given that the majority of PCs around the world are either some Core iX or a Ryzen platform, I don't see what all the panic is about...
Hello, has anyone already dealt with cleaning out the source folder on the installation stick? What is absolutely necessary! With the 23H2 I only had 3 files (Install/Boot.wim, Setup.exe) and everything worked. With the 24H2 I have over 1000 files! Thanks and regards
New Setup design require all (or most) \sources\ files, because it's built as in-place upgrade experience i think you can remove asz, dlmanifests, etwproviders, replacementmanifests, sxs folders
On a 26100.1 iso it's about 200MB worth of space. Is there anything to be gained by "cleaning" those 200MB off the iso?
Is 26100.2 possible to clean install? Or do I need to install 26100.1 and then upgrade to .2? I don't really understand the different version numbers. So basically if there was a leaked .2 iso, we could also clean install it? Or is .1 the "main" build with small updates released afterwards? Thanks!