New
#21
I honestly think that somehow Windows 10 v2004 caused a conflict with Bitdefender. This never happened until I updated Windows 10 to v2004, recently, and honestly, I'd never even touched the Profiles settings in Bitdefender, so I assume they were always set to automatically adjust the profile based on the power needs of what I was doing at that point in time. Unfortunately, I don't really have any way of telling. I mean, I could probably rollback the update, maybe...I'm not sure how that would work, anyways, then test it. That kind of seems like too much work, though, considering it seems like I got it working the way I want it to, now, so I'm not going to touch it. Maybe someone else who hasn't upgraded yet to Windows 10 v2004, can confirm, before and after?