Twice this week I’ve lost both rear USB-C ports. Lost as in no response when anything was plugged in
I resolved the issue the first time by reinstalling the latest FW Desktop drivers. The second time I wasn’t so lucky; reinstallation didn’t work
They are both working again, now. I’ve reinstalled the FW Desktop driver once, the chipset driver seperatley again, and, while rebooting, the weekly beta channel Win 11 drop installed (26220.7344)
Dropping this into the chat just in case others see the same issue
Ok, third time. Rather annoying. Is anyone else finding their rear USB-C ports fail under Windows 11?
I’ve attempted to get them to work by reinstalling the driver pack. Three attempts without success.
Is there a verbose switch for the driver installation package that will pipe the outcome (success, failure, error message) of the installation to the screen?
When the ports fail ..
And when the ports are working …
Four tries reinstalling the driver pack and no luck. Reinstalled the BIOS and the ports are back. Very odd!
sun
January 10, 2026, 1:22pm
4
Maybe try linux to rule out hardware/firmware issue?
RobG
January 10, 2026, 7:10pm
5
I looked at my Win11 USB drivers and they’re all provided by MS, rather than AMD.
On the release notes for 7.11.26.2142 chipset drivers, which support AI MAX 300 Series, AMD USB4 CM Driver is listed as not applicable for Windows 11
Is your TB5 hub bus powered? Wonder if this is related to the external drive power issues other folks are reporting.
That’s a great idea @sun Thank you!
I’ve set up dual boot to Ubuntu so that I can check the ports there the next time they fail under Windows.
It’s difficult to isolate drivers from the Framework package. In addition to the chipset there are crosecbus and storage drivers which are part of the mix
I have the AMD Adrenalin drivers installed but will uninstall that entire package now and rely entirely on Framework’s drivers
No. It is powered by an external brick
There is one additional thing I’ve noted. I use a Shokz dongle and headphones. After a while I hear very load static and have to remove and replace this dongle. I thought the dongle might be faulty so have purchased and replaced the old with new. Same issue. So far I cannot recreate this issue when using the front USB port
There are similar issues discussed in this thread
And reported on Framework GitHub here
EDIT: and here and here
sun
January 18, 2026, 8:35am
10
This sounds like the USB C power issue that I have seen and documented in the BIOS 3.04 thread. Basically the device bugs out when it failed to get enough power from the rear USB C ports.
Recap: I used a USB3 (10 Gbps) hub to connect my gamepad and headset dongle to the motherboard, and I’ve been experiencing random flickering. I spent a significant amount of time testing and trying to reproduce the issue, and I’m increasingly convinced it’s power related. I’ve also noticed a couple of new scenarios, so I think it’s appropriate to post in this thread.
Test setup
Motherboard: Framework Desktop (motherboard only, 128 GB)
PSU 1: SilverStone SFX 450W
PSU 2: Seasonic Prime TX-1000 …
Sure, could be
What does “bugs out” mean? When mine drop they are no longer visible in Windows device manager … I have screen shots in my thread
sun
January 19, 2026, 10:18am
12
I mean the device will start malfunctioning first (in my case my HDD making scratching sounds) then fully cut off. The devices will disappear from the OS. The only way to bring them back is to unplug and reconnect them.
That’s slightly different to my experience. Firstly, disconnecting and reconnecting will not bring the devices back. Secondly, I don’t get the “scratching” sound nor any prewarning that the devices will drop.
That said, both ports do drop from the OS as I’ve noted in the Device Manager screenshots. And I can’t get them back easiy. Disconnecting and reconnecting doesn’t help nor does rebooting. Reinstalling drivers seems to bring them back sometimes. Reinstalling the BIOS also sometimes works.
Edit: Just because I see somewhat different behaviours does not mean that you are on the wrong track re power @sun . The Framework Desktop is a desktop but Strix Halo is mobile (as @rjones suggests ) so all ‘mobile’ related assumptions are worth checking to ensure they are applicable to ‘always plugged in’ reality.
sun
January 20, 2026, 6:00pm
14
FW4TeePee:
That’s slightly different to my experience. Firstly, disconnecting and reconnecting will not bring the devices back. Secondly, I don’t get the “scratching” sound nor any prewarning that the devices will drop.
I was referring to your headphones having loud static.
Yes I agree. BTW in my case I was comparing to my Lenovo Thinkpad T14 laptop with AMD Ryzen AI 350 apu which is as close as you can get for a non strix halo cpu.
I’m not sure if the issue was Framework USB-C or Shokz bluetooth dongle related. I have a new Shokz dongle and so far (although with extensive testing) I haven’t seen the static issue resurface
sun
January 20, 2026, 9:17pm
16
Does the new dongle have or not have the issue? Earlier you mentioned the new dongle has the same issue:
The one time it did occur might have been a furfy. As I said, I haven’t extensively tested so I’m unsure as it only happened that one time.
I’ll test it on a Teams call next week
I bought a new external 10Tb LaCie d2 and have connected it directly to the USB-C rear port (with the new USB-C cable and drive power supply). I had some time trouble free but yesterday the partition table on the d2 became corrupt again making the drive unreadable. This is the 2nd time my new drive partition table has become corrupt on the FW Desktop; the 5th time overall if I include the previous LaCie d2.
I am still having the same issue i.e. intermittent loss of my rear USB-C ports. Is anybody else seeing the same problem?
Listing some potentially related issues purely for cross-reference purposes
I’m having an issue with the 1TB Framework Storage device when using either of the front USB-C bays. I’m trying to rsync some data over to it and keep getting stuff like this:
[1262129.817003] usb 4-2.1: new SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
[1262129.828654] usb 4-2.1: New USB device found, idVendor=32ac, idProduct=0005, bcdDevice= 1.10
[1262129.828673] usb 4-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1262129.828677] usb 4-2.1: Product: 1TB Expansion…
There are related issues for 13 and 16 laptops, too:
Are you looking for a Thunderbolt/USB-C dock for your Framework laptop? This wiki entry will provide a list of docks the community has tried and tested.
[Note: this is a wiki post. If you have information to add/change, then you can edit this post.]
Notes: looking for devices worth testing, and performing tests:
Wattage: At least 60W is needed to charge the laptop. If the dock provides greater than or equal to 60W, then it passes this criteria. Framework 16 needs 60-100W and with GPU 180-2…
I booted my Framework to find out that none of the expansion ports worked.
The kernel messages were filled with messages like
[ 2.449908] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.02
[ 2.449911] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.449912] usb usb1: Product: xHCI Host Controller
[ 2.449912] usb usb1: Manufacturer: Linux 6.2.8_1 xhci-hcd
[ 2.449913] usb usb1: SerialNumber: 0000:00:0d.0
[ 2.450001] hub 1-0:1.0:…
I have a Framework Laptop 13 (AMD Ryzen™ 7040 Series) and a monitor connected to my Lenovo Hybrid (USB-C, USB-A) Dock. When I connect that dock to the laptop via USB-C to a USB-C expansion card at position 1, it does not detect the monitor. But when I connect it via USB-A to a USB-A expansion card at position 2, it does.
But using USB-A to connect to the dock I miss some other functionality of the connection via USB-C like recharging the laptop.
So the question is: Why is the monitor not detec…
Github:
Periodic loss of USB ports - Desktop · Issue #158 · FrameworkComputer/SoftwareFirmwareIssueTracker
USB-C Problems with USB-PD cycling every second · Issue #78 · FrameworkComputer/SoftwareFirmwareIssueTracker
Lost my rear USB-C ports - Framework Desktop - Framework Community
This link points to a newly created Github issue that acts as a point of collection for issues relating to the ones described in this post
opened 03:53AM - 23 Jun 26 UTC
This issue has been created to track and gather information related to PD issues… we have seen reported to us on different AMD Mainboards across our different platforms. This includes;
**Framework Laptop 13;**
- AMD Ryzen™ 7040 Series ([BIOS & Drivers page](https://fr.mw/link/13_7040_BIOS))
- AMD Ryzen™ AI 300 Series ([BIOS & Drivers page](https://fr.mw/link/13_AI300_BIOS))
**Framework Laptop 16;**
- AMD Ryzen™ 7040 Series ([BIOS & Drivers page](https://fr.mw/link/16_7040_BIOS))
- AMD Ryzen™ AI 300 Series ([BIOS & Drivers page](https://fr.mw/link/16_AI300_BIOS))
**Framework Desktop;**
- AMD RYZEN™ AI Max 300 Series ([BIOS & Drivers page](https://fr.mw/link/Desktop_AIMax300_BIOS))
### **Some of the issues we have seen reported (_includes but is not limited to_);**
- USB Port 5 Lost on Framework Laptop 16 AMD Ryzen™ 7040 Series.
- TBT Device not working on AMD RYZEN™ AI Max 300 Series. (JHL7440 controller) on Framework Desktop.
- Network Disconnection when running sunshine service on port 4/5 on Framework Laptop 16 AMD Ryzen™ AI 300 Series.
- Specific Portable Type-C monitor cannot be displayed on Framework Desktop.
These issues are being investigated by us as well as our manufacturing partner Compal. If you believe the issues you are facing fall under this problem, please include the below requested information in a comment following the posted template. Depending on which Operating System you are using, the process may be different on how/ what information is gathered.
**These issues do not include;**
- Wi-Fi or Bluetooth loss when using high speed devices on the front right expansion card slot on the Framework Desktop, this is an issue related to signal integrity.
First, if you are having this issue, make sure that you are on the latest BIOS & Drivers. If you are not, you can go [HERE](https://fr.mw/link/bios) to make sure you are up to date. This is required as any testing done by us or our manufacturing partners will be done on the latest BIOS & Drivers.
- You can also [sign up for notifications](https://fr.mw/link/BIOS_Driver_Notifications) of when our latest BIOS & Driver updates are available for your device. This way if an update is published, you can test if the behavior being faced is resolved, same, or different on the new BIOS.
**Important if using Linux** - Please use the CLI (_command line_) utility fwupdmgr to update your Framework Computer firmware. This will provide detailed information about what updates are being completed. In the unlikely event that anything goes wrong with firmware updates, using the CLI utility will also provide us with output messages that explain what happened and why.
- Updating instructions using fwupdmgr can be found on each respective release page: https://fr.mw/link/bios
- If you have any issues in performing this, please reach out to support: https://frame.work/support
### **If you are using Windows;**
- Using [framework_tool](https://github.com/frameworkcomputer/framework-system) in Command Prompt (Ran as Administrator), run the `framework_tool --versions` command.
- Copy the output information into your comment.
- If you run into an error, make sure framework_tool is installed. You can follow the instructions in the above hyperlink to get it installed.
- You can also directly use the `winget install framework_tool --source winget` command in Command Prompt (_Ran as Administrator_) to install framework_tool.
### **If you are using Linux;**
- Firmware: (Output of `framework_tool --versions`)
- OS / Kernel: (Output of `uname -r`)
- DRM Status: [Paste output of `grep . /sys/class/drm/card*-*/status`]
- Use this to gather the requested logs;
- LOGS: (Link to `dmesg` or `journalctl -b`)
- Output of `sudo framework_tool --pdports` and `sudo framework_tool --pd-info` while the failing peripheral is connected to the affected port.
## **General information we will be asking for;**
- Behavior being experienced/ Issue:
- The device you are trying to connect to your Framework Laptop/ Desktop (_Name and Model Number_)
- If it includes a cable, is it the cable that came with the device, or a different one?
- If it is a different cable than what came with it, what cable is it? (_Brand & Information_)
- If you can include a link to where it was purchased from, or product page matching exactly what you have - it is additionally helpful.
- The Port/ Expansion Card Slot you are trying to connect it to.
- If you are not sure of the exact Port/ Slot number, you can check our page [HERE](https://fr.mw/link/ECF).
- Which Expansion cards do you have in each slot?
- Does the device you are trying to connect work in other Port/ Expansion Card slots?
- If so, which ones does it work in & which ones does it not?
- Does the device work when plugged directly into the Mainboard (_Expansion Card removed_)?
- (For Laptop) Does the behavior change if you unplug the Laptop from the Power Adapter, have the device shut down for 3 or more minutes, plug the Power Adapter back into the Laptop, then turn it back on?
- When did the issue start occurring? (_Date in YYYY/MM/DD format_)
- Which BIOS version did it start occurring on?
- Did the behavior get better or worse when updating to a different BIOS?
- Detailed replication steps from beginning to end so our teams can try and replicate.
- If you wrote into support and have a case number, please include that case number.
- Any additional information you think would be helpful for investigating.
## **Please see below comment for Template to use for inputting your information into a comment;**
To use the template, please follow these steps;
1. Click "Issue Body Actions" in top right of the comment below
2. Click "Copy Markdown"
3. Paste info comment & fill out/ provide needed information.
- (_Second comment will show an example of what the template would look like when filled in_)