Microsoft wants you to know how easy it is to ruin your computer with Windows 11

[–] • 1 pt

I am about to pull the trigger on a Mac Studio. It's not like Apple gives a fuck about my security or privacy but they at least make the government file shit in court and get legit warrants vs M$ that just hands over shit to anyone with two fucking pennies to rub together.

link

[–] • 0 pt

Apple's hardware can be really good or absolute shite. Too rich for my blood.

parent
link

[–] • 1 pt

My rational is if you max out the mac mini it comes up to $1999 but the base Mac Studio is the same price with the same 32GIG of RAM with a M2 Max instead of the Pro in the mini. It's almost as if Apple wants people to either buy a mid range mini OR a base level Studio.

I'd buy the iMac of the screen were larger. The smallest screen I have is a 27".

parent
link

[–] [deleted] • 1 pt

My computer forces this last obscure update... And uninstalls the update because it can't apply the update. My computer is pissed off sounding like the fan can't keep up very well. Functions are difficult to use, like I have to hard shutoff my computer to turn it off. No sleep option anymore. And everytime I turn it back on it updates and undoes the updates scream

link

[–] • 1 pt

If you're using windows, turn off the update service in services.msc

parent
link

[–] • 1 pt

Windoze pro versions have "group policy" editor or "gpedit". Allows user to mod the snot out of windoze. The editor is the only reason I installed win 11 pro over 10 (cough cough no charge)

parent
link

[–] • 1 pt

(edited )

gpedit is essentially a front end to the registry - you can do the same thing by modifying, adding, or removing keys. gpedit just does it for you in a graphical sort of way.

at least for single user machines. Group policies under a domain controlled machine have other uses.

My solution doesn't just prevent updates, it disables the machine's ability to do updates at all because the service that provides them isn't running. It's what I do on Win7 machines (and did on XP machines when those were going out of service) - I don't trust microsoft not to slip in something funny, and there's always that chance you get a bad update that does what OP described.