I just got a new FW13 Prop and Windows 11 fails to install every time at 77% I’ve read the other threads on this in the forum and have not found a resolution. So far here is what I have tried:
What else can I try?
I’d get memtest86 on a memory stick, and immersion-test your RAM. It’s always worth doing on a new machine anyway.
Maybe try to find an older Windows build like 23H2? What is the make and model of SSD?
Usually Windows either sees the drive to install or not, do not remember the last time I had a partial install after it started copying files.
Maybe the TPM needs to be reset? It is much more critical on the Windows install with the checks it makes than on Linux.
Could be something going on with the SSD too but just not being reported. If a spare SSD is around maybe try installing on that? Just some quick thoughts on the matter.
Edit Read also that issues can come up with the Intel RST/VMD driver, setup sees the drives initially but at about that point in the install reinitializes the storage subsystem and something doesn’t get written to correctly to the boot manager (BCD). Because the system was not actually a system yet the only log would be on the recovery media since the recovery environment in memory gets scrubbed on boot.
Memtest unfortunately results in a blank screen while running the test, but the log files did not seem to indicate any errors after ~2 hours of testing.
I actually pulled the drive out when I did the Linux partitioning initially. I tried to load the Fedora 45 live USB and it will not start. So that’s one more interesting data point.
I’ll try resetting the TPM and a new SSD later today.
I reset the TPM and tried another SSD and the install still fails nor can I get the Fedora 45 live ISO to load on this machine. I’m going to open a support ticket with Framework, but I’ll keep trying to work through it too.
My primary suggestion for Windows would be to ensure you’re using the old installer if you’re on a newer ISO (at some point after lang/keyboard setup there’s a clickable text on the lower left). My last Windows 11 install on my desktop also failed partway through but went off without a hitch doing that.
What about enabling/disabling Secure Boot altogether? Different distro? Fedora and its variants have been somewhat temperamental IME.
I would be slightly minded to reconfirm this with a visual confirmation. There are unfortunately two versions of memtest86, one of which is an open-source fork, and one is a freeware version of a commercial version. I would be inclined to use the former, not the latter.
Okay, I got memtest86 running from GIT and found no issues with the memory.
I can’t find a secure boot option anywhere in the BIOS, which is super frustrating. Otherwise I’d turn it off. The 13 PRO seems to go right to “Settings” whereas my 13 takes you to a screen where you can select what you want to do, administer secure boot being an option. Wonder why doesn’t that exist on the PRO?
Have not seen or played with the new pro series laptops personally.
There has been a shift in what screen comes up by default now among some vendors to make it more “user” friendly. This usually means it starts at a screen most of us are not used to being started off with because systems were never presented this way.
It may take navigating around to find is being sought out. What has support said on this topic so far in response?
That’s quite odd, every time I reboot my Pro into the UEFI setup I get the selection menu. How are you booting into the setup? The option in GUI does it every time for me.
Make sure you’re in the BIOS, not the boot menu. Take some mobile-phone pics of what you see if you’re not sure, and pop them here. 
If it is hard to get the timing right to press F2 to get into the BIOS menu, pull the SSD out temporarily so the system can’t boot to anything else.