Apparently I edited this after you saw it. W10 has the problem with core parking, not W11. W11 seems to 'fix' the erroneous forced core parking. W11 doesn't have the issues. W10 isn't 8 years old. They didn't stop updating it 8 years ago, when they decided to to switch to W11, they stopped updating it with the changes W11 saw, probably 2021.jorimt wrote: ↑15 Mar 2023, 08:46You'd have to take it up with Intel and Microsoft, though I'd assume core parking behavior can be tied/related to scheduling in this specific instance.
As for "intentional sabotage," that's an odd way of framing an upgraded OS with a scheduler built from the ground-up specifically for new Intel CPU types. I'm no Microsoft fan, and Windows 11 still needs tons of work (things like the new right-click context menu are absolutely mind-numbingly stupid), but the hate they constantly get online is bordering on hyperbolic and nonsensical; Windows 10 is pushing 8 years old, so when is it "too soon" to expect them to move on to a newer operating system with exclusive features?
So once again I'm not pointing out that it doesn't support my 13900k, but rather it seems it's going out of it's way to reduce the effectiveness of my 13900k by parking 3 out of 8p cores even with core parking disabled. My 5900x did not have this behavior and I explicitly shut it off. In w11 it doesn't do it.
If you read from the OP, the problem I was having was with core parking remained even after disabling core parking in W10. Nothing would shut it off.InputLagger wrote: ↑15 Mar 2023, 17:13Cores can be unparked via quickCPU program too, if you already have it