Has anyone else noticed that after certain Windows 11 updates, Process Lasso settings (like CPU affinity, priority rules, or power plans) seem to reset or behave differently? I've had custom rules working perfectly, then suddenly after a big Windows update, my system ignores them until I manually reconfigure. This seems to affect gaming performance and even simple multitasking.
Is this a known conflict between Process Lasso and Windows update policies, or am I missing a step to "lock" my rules so they survive updates? Would love to hear how others are handling this — do you reapply configs, use export/import, or is there some hidden setting I'm overlooking?
Rules should not be lost under any circumstance. Does it look like your entire config is wiped or do you still see the rules?
I see my CPU affinity and priority rules still listed, but the system runs as if they aren't active (processes go back to "default" Windows behavior). Once I reapply the same settings in Process Lasso, everything starts working again.
So it's not a total loss of config, more like the rules exist but aren't being enforced after big updates. Could this be related to how Windows reinitializes policies after an upgrade?
Quote from: pandrhola on September 09, 2025, 10:53:47 PMSo it's not a total loss of config, more like the rules exist but aren't being enforced after big updates. Could this be related to how Windows reinitializes policies after an upgrade?
Quite possibly, yes. That would be more likely if you are depending on inheritance (whether intentionally or not) to carry your rules to children processes.
Is menu item "Options > Forced Mode" checked? If not, checking it may help.