Nope. Been using the same installation of Windows 10 for years, and everything just works.
Even swapped the SSD from one laptop into another one. Added a UEFI boot entry, and it came right up.
I think the only problem I ever had was audio or Wi-Fi occasionally failing to work after resume. But that resolved itself after one of the major updates.
The only annoyance I've run into is the "Let's finish setting up your device" screen after feature updates. But you can disable that fairly easily.
I mainly use it as a glorified Chromebook though. Browser, Windows Terminal + WSL, maybe the occasional Inkscape or Lightroom. All the "interesting" stuff happens in Linux VMs atop ESXi running on an old desktop.
But for everyday use, it's nice to have something that "just works" when I pick it up.
I might check out Linux again in a few years though. From what I've read, PipeWire seems to be killing it in terms of progress on the audio side. So once the Wayland ecosystem matures, it should be fairly easy to get back that "just works" status with Linux.
In terms of performance, the main issue Windows really has is disk I/O. But a modern SSD fixes that easily. I am using a second-hand, nine-year-old Dell Latitude laptop, and it does everything I need it to do. Boots up in seconds. Has to stay plugged in though.
As a man I can assure you we have the same problem. I have garments with a 30" waist that fit the same as a 34" waist. And I have pants with a 29" inseam that go past my feet and 32" inseam that don't.
My biggest gripe is that the all feed is not actually the all feed from across the fediverse, but a feed from all instances your instance is federated with.
It's even worse than that. It's all communities that users on your instance have subscribed with. If someone creates a new community on another instance, you won't see it on yours until you or someone else discovers and subscribes to it.
I generally start looking to replace mine around the time that Google Maps starts becoming laggy. That's usually around the 3 year mark for me. After 4 years things get pretty bad.
Nexus 5 -> Pixel 2 -> Pixel 6a
Practically every app update grows its respective compute and memory footprint. And over time, it adds up. Combine that with the big jumps in resource usage that come with OS updates, and eventually things just start slowing down.