Hey AltCoyne,
I’m the one experiencing the same behavior (threads 1 you mentionned).
I have contacted the support aaaaaaaaaaaand… no answer…
I tried to unplug everything, reinstall windows, update drivers with and without Framework bundled ones. This is a disaster.
I bought another dock and even if it’s a little bit better, if I plug an usb A or C device in the dock OR in the laptop directly, it crashes and can’t reboot properly.
I wonder if this could help you out https://answers.microsoft.com/en-us/windows/forum/all/windows-11-shutdown-takes-a-long-time/17e7538e-ec48-460a-8ad6-bdb340e28720
Appreciate the thought, but disabling fast startup was one of the first things I did and I’ve also done the sfc /scannow song and dance, both to no avail. I won’t be doing any more deeply involved troubleshooting at this point as it’s a waste of work hours, as soon as support gets their ducks in a row for a return I’m replacing this computer with something else.
It seems like a Windows Update is probably to blame. Getting this sorted will be very important so that if a BIOS or driver update is necessary that they are able to work on it. Working with support is going to be the best way to facilitate that.
Understand that if a Windows Update is to blame this means MS changed something and it broke current drivers or BIOS functionality. It isn’t really fair to blame Framework for something MS did.
Of course this isn’t proven here, and we are just trying to drive down to the root issue. But just throwing that out there for what it is worth.
I didn’t find much to indicate that people were havin this same issue outside of Framework users when I looked around initially, but you may be right. Personally I’m not very interested in assigning blame, I just need a computer that functions properly for work - I’ll probably replace this machine with some MacBook variant as Windows 11 seems outright hostile to its users even when it “works”.
I would encourage you to do what works for you. Understanding why things don’t work help you to make informed purchases. For example is it Windows that is the problem or perhaps the maker of your audio cable that you are trying to plug in? Have you checked that it supports Windows 11 by any chance?
I think you are confusing Thea and myself but to answer your question, yes, the cable does support Windows 11.
I totally understand your reasoning and would do the same given you’re unable to connect literally any external device to your machine.
That said, I would encourage you to detail as much of the issue in your return request (or even better, an initial support ticket if you haven’t already) to try and help Framework avoid losing any other customers. I will do the same once I’ve tested the USB 2.0 hub.
As AltCoyne mentioned, I’m not just having trouble with any one cable or device. Audio, HDMI, USB (with or without powered hub), even bluetooth, it doesn’t matter what I connect. I can see that there are a lot of issues in Windows 11 that’d bother me as well - the constant push to put “AI” in everything, the slow and crash-prone UI, the inability to fully disable Edge as a browser option, and so on - but this particular problem seems to run deeper than that. Plus that even when I boot into Fedora I’m unable to use my bluetooth peripherals.
So yeah, the breaking issues are the reason that I’m returning the computer, and the things I dislike about Windows 11 (which I’ve never used before now, I was on Windows 10 which I find tolerable) are the reason that I’m switching to Mac for work.
I included a link to this very forum thread in my return request, which is part of why I keep describing my issues in detail even though I’ve given up on solving them 
hopefully you and others can get your Framework machines working as intended, I really do like them conceptually and might get one for personal use in the future. But for a work tool that needs to be stable and reliable I think it requires too much tinkering.
Good points. I did confuse the cases. All fair enough! 
Not that you want to be a test subject any longer; I am curious if the same issues happen with the Intel Core Ultra 1 Framework Laptop 13. If you were willing to return your AMD model at least the memory and SSD works between the two mainboards if you bought the DIY setup. I suspect the issue may not persist with the Intel chipset. There have been a number of oddities that only get brought up on AMD systems.
The latest consumer updates or whatever it is being called in Windows Update (The optional one that is not installed by default and you have to click on it for the “latest experience”) is not a final release; installing those gives users the false sense that it is fully tested and it is NOT. It is being used to expand their testbed before they push it as a full release.
Not saying that is the cause here, though with all the complexities of modern operating systems; sometimes less complication is more beneficial. I do not want extra features if it means having buggy symptoms of the core functionality of a device.
I suspect the issue may not persist with the Intel chipset.
I strongly suspect the same, however I’ve had the laptop since March so I won’t be switching 
The latest consumer updates or whatever it is being called in Windows Update
They’re called “Preview” - Stupidly that’s the only difference in the name so they’re easy to mistake for an update you actually want and are displayed even when you’re on the General Availability update channel. That said, I’m on the latest GA (non-preview) update.
Same issue with the USB 2.0 hub. Time for a ticket!
FIXED! Thanks to @Vincent_Llora, I followed the post here to disable “AMD Audio Coprocessor” in device manager.
Hilarious that I found this on the day the USB hub arrived but I’m pleased I’ve got it sorted, regardless.
Hi.
Does that imply that there is a crash bug in the “AMD Audio Co-processor” driver in Windows 11 ?
I’m not entirely sure. It’s either that, or some kind of conflict with certain audio hardware. I’m not well versed enough in this to give an educated opinion, apologies!
If I hadn’t shipped my laptop off for return yesterday, I would’ve tried that as well (after seeing you mention it). Thanks for sharing your troubleshooting steps and results, hopefully it’ll help others as well. And hopefully the root cause can be resolved!
I’ve reached out and not gotten a confirmation that there is a bug, but I think it is more of a conflict of two drivers trying to do the same job.
@AltCoyne Glad you got the issue fixed. I know it surely was frustrating for me.
Just a thought that might help others in the community: edit the title of your original post with [FIXED] we might need your help back at the beginning so that others with a similar issue can get it solved quickly by going to that discussion.