[Solved] - Framework desktop

I have a new framework desktop within the last 30 days, which I am unable to boot, booted initially, now no display, cannot reach bios screen.

I have opened a total of 3 support tickets, The first one, was in reference to a mis-deiivered ethernet add-on plug. That one got resolved and I did receive email communication from support several days later.

The other two ticekts, were in reference to the no booting sistuation. One opened on May 2nd 2026, and again on May 9th. I have not received a response to either. It is frustrating, having a new machine I cannot use.

I sent link to video of the diagnostic lights on the second one. too much blinking for me to make sense of.

Perhaps… there is some issue with my email? Do not know, the support page says the tickets were accepted, but I received no automated confirmation or reply. I would really like this to work.

If anyone from support is here. Please assist.

@catastrophic can you help with this support case?

tagging @Eagle in - I’ll see if I can find your tickets and we’ll follow up.

I see the emails went through on our end including replies from Support - can you double check spam? I’ll also check with the team in case I’m missing something.

I received this email notification from the community post just now, but nothing from support, and I have checked my SPAM. Nothing.

Kevin Eskridge

Can you try whitelisting support@frame.work or see if the domain youre using accidentally blocked emails from @frame.work?

I do not have anything, blocked. But there is a proxy in the middle.

I did receive that one email from support on Apr 18th for the delivery issue. But nothing since then.

After reading here and there that others occasionally had issue with that sort of email, I tried to change my email address to a direct one, but did not receive the confirmation email to allow me to do that.

If you will look at the ticket I submitted on May 9th, you will see I supplied an alternate email address. Perhaps that one will work better, as there is no proxy.

apologies, it is the one from May 8th. It has the link to the video of the lights.

I just got a replay at the alternate email address. I will follow the instructions as mentioned and update.

We got the communication issue resolved. Short answer is, if you are using a proxy or something odd with your email, their ticket system is hit or miss in reaching you. Once I switched to a direct email address, support was able to be in contact.

After some trouble shooting back and forth they sent a replacement mainboard. Still uncertain if original was a bad board issue or some configuration corruption.

Mainboard replacement received, and I had time over this weekend to replace. Ran into a couple of issues getting into BIOS with the new board but was able to work through it. Documented below.

After receiving the new board, initial Issue: After installing the replacement mainboard, the system powered on but would not enter the BIOS/UEFI setup screen. Pressing F2 (or F12/Del) during boot had no effect. The connected monitor repeatedly cycled between blue (signal detected) and amber (no signal) for several minutes. The system would only boot into the OS (Windows 11 Pro or Bazzite) if I manually powered it off and back on after the cycling phase. EFI USB boot menu was also unreachable. This occurred with both NVMe drives installed or removed.

Root Cause Context: This was a post-mainboard-replacement issue where the pre-boot phase (BIOS initialization and keyboard detection) was not displaying or responding properly, even though the board could eventually load the operating systems.

Resolution Steps:

  • Tried with and without NVMe(s) installed.

  • Switched the wired keyboard to a front USB port and changed the display cable from HDMI to DisplayPort.

  • This allowed successful entry into the BIOS setup.

  • Updated BIOS from version 3.03 to 3.05 using the prepared EFI USB.

  • In BIOS: Disabled Quick Boot and Quiet Boot.

  • Performed full power resets and used direct wall outlet power during troubleshooting (per prior support guidance).

Current Status:

  • Can now reliably enter BIOS with F2 on cold boots.

  • Monitor blue/amber cycling is resolved.

  • System boots normally into both Windows 11 Pro and Bazzite.

  • Successfully tested on UPS power.

  • Current BIOS: Insyde Corp. 03.05 (2026-01-21).

All issues appear resolved. Thank you for the replacement mainboard and support.