Nope, I disabled Core Isolation and all that too, I've done and tried many things trying to keep it disabled always like it once was, not related to any of that even with that stuff disabled Win 11 Antivirus will always reenable itself on 22H2, and wouldn't on builds prior, it's literally as...
In every build of Win 11 before 22H2 and Win 10 prior if you enable the 'turn off Defender Antivirus' setting in Group Policy, Defender Antivirus would stay disabled forever unless you manually reenabled it - no matter what else you clicked on your computer afterwards and no matter how many...
Learn the meaning of the phrase 'exactly the same behavior' before you rattle off like that
People are welcome to try this on 22H2 and another previous build/version themselves, and see who the real bullshitter here is
Then help explain it to me - because he says it functions exactly the same as before
How is this
exactly the same functionality? Please, by all means make that make sense if you can.
And I don't need antivirus, and it gets in my way running automated scans bogging things up when...
No, before 22H2 if you enabled the 'turn off defender antivirus' in group policy, Windows Defender Antivirus remained permanently off forever without doing anything else at all
Now with 22H2 if you do the above it reenables itself automatically after a set amount of time - IT NEVER DID THAT...
A setting worked one way before, by enabling that one setting and one setting alone, now it no longer functions as it had, it has been neutered
Pointing to a pile of additional hoops you now have to jump through, over there, does not erase the above. It re-emphasizes it.
I also don't like I can't open start menu right away to all apps
edit: oh lets see maybe not https://www.intowindows.com/how-to-show-all-apps-by-default-in-windows-11-start-menu/#:~:text=Step 1: Open the Start,key to open All apps.
double edit: nah 3rd party bleh
again, disable it yourself via group policy while on windows 11 22h1 and any prior version of windows 11 or older
go back in a week and see one disabled still and one not
as I edited in above, whether via group policy or registry, it will only stay permanently disabled now when there is...
nah it re-enables itself, always
this is new behavior introduced in 22h1, only change after disabling successfully in all prior 11 and older windows
you can try it yourself
go back in a week and look
edit: to add, it will ONLY disable itself now when another antivirus is...
My 3570K was running games fine till about 2018 I started getting CPU limited with a 2070 - Div 2 and Shadow of the Tomb Raid I couldn't get over 45FPS @ 1440p IIRC even reducing settings
Games less demanding than that or older should be fine on it still - Resident Evil 2/3 Remake and Hellblade...
Honestly over 8 years and 8 various SSDs for multiple HTPCs/computers of mine I've only had 1 die in all that time and it was an 840 EVO back in like 2015, they're more durable than we all scare ourselves into thinking IMO
No one has answered what information of theirs they think is NOT already out there and already in some company's data set that they've protected by NOT having a smart home device.
Maybe, maybe, your voice pattern? That's about all I can think of.
So why is your big beef then with a smart...
Plus, your data is already out there.
You protect nothing.
You 'kill Google' or whatever, cool. Your data is still out there. Companies still buying and selling it from each other. Mission accomplished 👍
I dunno man I've been doing this for over a couple of years novelty hasn't worn off yet. I also don't buy something unless I know I can get use out of it.
A smart thermostat for example can not kick the air on when it senses no one is home, and also not let it get above a certain temp, but then...
Couldn't disagree more. I love my smart home crap, but also it's part of why I was doing HTPCs even years back and was the same exact thing to me then - it's TV, but cooler. Now it's everything else in the house from lighting to your grocery lists to thermostats and DIY security systems - but...