Also, if you haven’t see this guide yet, it’s here:
Follow everything it says there…and you should be good.
Okay, thank you. Will try that and see how it goes.
NO soap. I created the boot disk using the Windows creation tool, used a different USB drive, changed the USB A card in the laptop and it won’t reload.
The framework logo flashes twice and I still get the same message to restart the machine.
Would really like to solve this. Any further guidance suggestions, etc…please.
I’ve my older laptop, on which I created the boot usb. Per @Second_Coming suggestion, I used media creation tool to create the latest boot usb. I swapped the 32gb (which appears faulty) with a 16gb micro, cleaned it prior to formatting it for boot as noted above.
I’m not all that familiar with bios and manipulating/playing in that environment.
Next likely causes:
- The NVMe drive isn’t fully inserted / has poor contacts.
- The RAM is bad.
Will endeavor to check this.
Wondering though, the initial install I was able to get the windows key entered and then things fell apart.
Does that indicate something else?
Trying to add some reassurance rather than noise.
The suggestions that @Second_Coming made are not incompatible with your initial experience. RAM failure is seldom complete and software won’t barf until it hits the dead bit. A loose NVMe can work itself out of the slot by a critical nanometer from the vibrations of your typing or those of the CPU cooling fan.
The Framework service desk is there to help you too. You (seem to) have a fully-supported configuration.
Dino
Hi,
I had the same problems with Gen13 DYI, Intel i5, 32GB.
The solution (for me) was rather easy:
- turn on laptop
- enter BIOS (F2)
- select “setup utility”
- select “advanced”
- set Wifi Mode to “Fallback”
- reinstall Windows completely
After installing windows, install the framework Gen13 driver pack. This will reset the wifi to default mode, which is ok.
Now the culprit:
After running windows update, which decided to update some intel drivers, I had a a few bluescreens again. Now the solution was to reinstall the framework driver pack again.
Since then I had no bluescreens, but I must admint I use windows only sporadically, so I don’t know how reliable windows runs on Gen13.
I think the BIOS’ windows setup detection just failed and this caused (for me ) the unexpected trouble.
P.S. Please note that these kind of problems are to be expected on a new platform like Gen13 and are not a problem of framework specifically.
3 Likes
I am again grateful and impressed with the guidance of this community. Thank you.
Indeed, I swapped ram slots and reattached the nvme this morning: nope, same issue.
Tried F12 and WiFi fallback, yep, worked.
However, 'sup with not being able to load win11 offline without having to create an account?
Got to that part of the install and I’m being funneled to create an account I don’t want.
Am going to try a fresh install later.
Any guidance on his to install win without having to create an account?
Again, my gratitude.
Hi,
glad that it worked. I did not use a microsoft account.
For the installation you can choose “I have no internet”( a small link near the bottom).
There will be a nagging screen later and there I am not sure if this one still can be disabled. I suspended it for x days, but I am sure it will come back 
Is there a way of reducing the screen image before installing windows or while installing it? I noticed some of the bottom of the images are cut off which is more than likely why I’m not seeing the choice to install offline.
Hi,
as far as I know there is no way of reducing resolution/image size upon install. But since the chosen resolution is rather low you should be able to see the whole image on nearly every screen with a resolution higher or equal than 800x600. I had no issues with the internal display. Are you using an external screen during installation ? If yes I would suggest to use the internal screen.
Sorry for the long delay. What I discovered was made known in a subsequent post here. The option for “no internet access” is now buried from view and it takes key combo: “Fn + Shift + F10” to get around the necessity to have a MS account to load windows 11. Not long ago the Pro version didn’t require this, but apparently ALL versions of Win 11 require an account unless you use the foregoing work around.
I’m up and running. Yeah.
2 Likes
I had the same issue as mentioned in this post. Adding onto the previous comments in this thread, the setting WiFi Mode to “Fallback” did not resolve my issue.
I followed the instructions on this website to change the setup.exe value from 1 to 3 from the following link: The computer restarted unexpectedly or encountered an unexpected loop error on Windows 10/11 | Windows OS Hub
This resolved my issue and I was able to boot into Windows and continue my installation process.
1 Like
Thanks for reporting this. We’ve designed 13th Gen BIOS to automatically detect a Windows 11 installer and set Fallback mode, but it sounds like there are scenarios where the detection isn’t occurring.
For folks who are seeing this issue, could you share:
- Whether you used the Media Creation Tool from Microsoft to create the Windows 11 installer.
- What model of thumbdrive you are using.
- Any details around the system you created the Windows 11 installer from (e.g. was it another Windows 11 system)
Hi there! Mine just arrived, and I had the same issue. In my case, the BSOD showed the culprit as net______.sys so it was pretty obvious that the network was at fault, and it was easy enough to find the WiFi settings once I’d made the connection and get it working. For the info @nrp requested:
-
I used the official ISO from the site, but used Rufus to create the USB, turning on the options to skip all the annoying settings and enable local account creation.
-
Thumb drive is a Kingston DataTraveller, 32GB version.
-
Creation system was Windows 11 Pro x64, using Rufus 4.1. Installer created was also Windows 11 Pro x64, with the modifications Rufus lets you make to skip the OOBE.
Hope that’s useful!
It’s possible that this is what caused the issue during your installation.
The OOBE is only skipped in part after the installation is done, why would this affect BIOS detection of a win USB boot drive?
Can confirm, same issue with my gen13 and win11_22h2, solved by setting WiFi to fallback manually.
Used Rufus 4.2 on win10 to create the boot drive.
Settings used: skipped hardware requierments check, no MS account and disabled data collection
It turns out the issue is actually not the customizations, but using Rufus (or Ventoy or similar) at all. We detect the Windows installer by looking for the presence of a specific file. With Rufus, the files aren’t visible, because it creates virtual partitions that are loaded with a UEFI driver. From BIOS, we can’t see what is in the partitions. We’ll update the guides to note that you’ll need to manually change the WiFi fallback setting if using Rufus: AX210 WiFi compatibility issues with the Windows 11 installer
2 Likes
Been uber busy, my gratitude for the shares. I did manage to figure this out and got up and running. Hoping so has everyone else.