Dear samwindsor
Thank you for sharing additional details and I completely understand your frustration. You’re right: on older or resource-limited machines, Efficiency Mode can sometimes work against the very productivity it is meant to protect, especially in environments where applications like Chrome or Adobe need consistent full performance. I recognize that this becomes even more disruptive when Windows continues to reapply throttling despite your attempts to manage processes manually.
While I personally cannot override product decisions or directly modify the feature, I can confirm that feedback from IT admins like you does reach the engineering teams, and cases with widespread user impact are reviewed with priority. I will escalate your scenario internally so it becomes part of the broader conversation on how Efficiency Mode should behave in enterprise or heavy-workload environments. Your real-world examples add meaningful context that helps shape future improvements.
Although I fully understand that you don’t accept the current limitation, the official guidance remains unchanged third-party tools may work temporarily but are not supported and could introduce additional risks. Still, your feedback is absolutely valid, and you’re not alone in raising it.
If this update helps, please consider hitting “Accept Answer” so we can close the thread with a smile . And of course, I’m here if you need anything else or want help documenting the escalation.
Thank you so much. Hope you have a nice day