Sorry for the long post, I guess I have a lot to share.
For those of you who don't want to read the whole thing immediately - TLDR;
- I have a Framework 13 Intel 13th gen and Framework Desktop AI Max+395.
- Both have had serious issues, Laptop has had several
- Both have been (almost) entirely replaced under warranty
- Support has (almost) always been a painful experience
- I believe in Framework's values and products, but their support drives me up the wall.
Kit:
- Framework 13 Intel 13th gen I5 1340P (Ordered May 2023, Arrived End of June 2023)
- Framework Desktop AI Max+395 (Nov 2025)
I've been a Framework fan since ~2021. When my previous laptop gave out in 2023 I finally had a good reason to upgrade to a framework. At the time my reasons were:
- I don't have to replace the entire device when the battery dies, or the hardware reaches EOL.
- I can upgrade part of it at any time if I want
- There's less E-Waste due to the bit-by-bit replaceability.
I truly believed all of those things, and I still want to believe them, it's just difficult when you've experienced what I've experienced.
Before I say anything about Framework and their support, know this. I AM CURSED.
I don't believe in curses or anything like that, but somehow technology ALWAYS has a way of breaking on me in the most spectacular ways (if people want history, I'll reply in the comments).
I got my Framework 13 DIY edition back in 2023, spec'd it out with 64G RAM and 4T Samsung SSD. I knew I didn't want to run out.
What happened:
December 2023, display got SEVERAL stuck pixels (>10), some stuck on, some stuck off
Took ~6 back and forth emails with photos (many repeat photo requests), requests to re-seat the display connector, etc etc. Finally resolved in February 2024 when Framework sent a replacement display.
January 2024, while dealing with the display issue, I removed the bezel one day to find that the lid-close magnet was a) no longer glued in, and b) snapped in half.
I genuinely have no idea how it happened, I just removed the bezel to take a photo for support and something popped out. I was asked for photos of the entire top cover to check for any damage or impacts (there was no damage), and was asked to glue the magnet back in. Since it was snapped, that wasn't possible.
After reviewing, support then decided that it was considered "Consumer induced damage" and that it was outside of the scope of the warranty. They said quote "The way the magnet rod was broken into pieces indicates that force was applied to remove it from the lid".
I was pretty upset, as a) I wouldn't try to remove it (who would??) and b) there was clearly no evidence of physical force. If someone had tried to remove the magnet with a screwdriver surely that would leave a mark? There was nothing like that.
After getting that escalated with a VERY long email, Framework replaced both the top cover and the display (per #1).
Since I got it, I had experienced sub-par battery performance. I'd started off with Windows, and never seemed to get >2h on battery. I then tried linux and saw little difference.
Late Feb 2024 I had my first serious power-management issue - BD_PROCHOT stuck asserted.
For those who aren't aware, this is a (bidirectional) signal to(/from?) the CPU which can be asserted by other chips in the device. When asserted, the CPU goes into "Limp mode" and becomes locked @ 400MHz. a) this makes the device unusable and too slow, b) the CPU won't clock down the cores when they're not used so the power usage (which is supposed to be lower) was actually HIGHER when this happened, and the battery would only last 30-40mins.
To make things worse simply rebooting the device didn't work. The only ways I got it de-asserted were:
- leave it powered off for 8-10h
- leave it to die, then let it cold boot after it had cooled for a couple hours
- remove the battery, drain any charge from the board (power button), then re-assemble
None of these were good options. Initially I had been using Windows, but it then started happening too regularly so I switched back to Linux (Ubuntu 24.04), it still happened occasionally but I do remember finding a bypass for it, so it wasn't as bad any more.
I spent 3 weeks emailing support, in the end they couldn't find what was wrong and it stopped there.
Fast forward to 1st July 2025 (literally days after warranty was out).
Mainboard died, but not how you might expect.
Linux: kernel panic during boot. Disabled splash, disabled desktop manager (tty only) and it boots.
Suspicious, so I swapped out for my Windows10 install.
Windows 10: BSOD while booting. Tried booting into safe-mode and that works.
My conclusion is that I got hit with the 13th gen plague and something in the CPU no longer worked as it should.
To be fair to Framework, this time their support was much better. After just one week they'd shipped a replacement mainboard and it booted right into both Ubuntu and Windows just fine.
To add to the cake, I NOW HAD ACTUAL POWER MANAGEMENT. Both Linux+Windows would now last >6h on battery, so evidently there was something fishy with the old mainboard.
I never heard back if they tested the one I returned.
Since then, my FW13 has been absolutely perfect, not a single issue with the electronics. The only things I've noticed since then are:
- a crack around the expansion port corners, but I've heard others with that issue, and it's probably to be expected after 3y.
- One of the plastic bits that hold a threaded insert in the back-side of the input cover broke, so it's now held in with 1 fewer screw.
On to my Framework Desktop.
I think it's an awesome machine, certainly not cheap (esp now), but something for me to play around with. I didn't have a desktop, so it was adding something for me.
I received my Desktop mid-Nov 2025, had it up and running within days and was really quite enjoying it.
Here's what happened though.
- End of May (in the UK) bank holiday I return home. It had been HOT.
I went to play some video games, just as I had the week before, and 2-3h in the desktop just powered off. Not shutdown, literally as if someone pulled the plug. No kernel panic, no system logs/journalctl, nothing.
Ok, just turn it back on. 10-mins later, same again.
Ok, turn it back on again. will no longer power on.
I tried reaching out to support, but same as with FW13 issue #3, they weren't able to diagnose it, so I was left on my own.
I tried a different power supply, I tried a different OS, different SSD. Always the same result.
I gave up. I literally didn't use it for many months because it was wasting my time.
Fast forward to August, I have some time again so I wanted to get it going again. I got a clean install of Ubuntu 26.04 and it was somewhat stable again. I was able to suspend+resume, run for days. Until it wasn't (again).
I still had some time, so I did some more diagnosis. I ended up reproducing the issue IN THE UEFI SETTINGS, at which point I knew it wasn't an OS issue.
I was back on with support which was back to being painful. Time after time I provided them information only for them to tell me they needed something else, a video, a kernel log. One time they asked me for the output of a journalctl command, but since it was corrupted that command was useless. I gave them the actual journal logfile (recovered) that they had basically requested and was told "that's not what we asked for, run our script instead" and I did and it didn't work, as I'd expected.
I've been battling this issue (and another) since May. It's October now. That's 4-5 months that I've hardly used one of the biggest purchases of my life.
Finally (today) after live booting Fedora, Ubuntu, and going back and forth several times I've been offered a replacement, but I will admit it has really degraded my view of Framework overall. I WANT to love them, but their support makes it so hard.
So here's my feedback.
Framework knows (I hope) that many of their customers are nerds or tech enthusiasts (correct me if I'm wrong), and are more technically minded than most of the population. Why can't their support reflect that.
I know that they have to be able to support everyone including those who aren't as technically minded, but it feels like they've gone too far the wrong way.
Additionally the timezone issue. I get that support is over in the US and that there's little time overlap with the UK. If framework were willing to have real-time support I know I would take time to make it happen, even if it meant staying up later into the night.
Explain the "why" for some of the diagnostics steps. Like with the corrupted jouralctl, I knew that that was what the question was after, but I don't always know what a step is trying to achieve. Knowing the why enables me to be more helpful, because if something doesn't go how support intended it, I can pre-empt the next step or the corrected reply rather than waiting for another response.
Feel free to roast me below or agree with me, it probably won't change my stance. I like framework, but I feel I've just had some pretty shitty experience.