In some cases there can be valid reasons to disable certain stuff. But these cases are not very common, and, in the vast majority of cases, it takes a bit of advanced knowledge and experience to be able to avoid falling into the usual trap of adding unwanted side effects, I agree.I disagree. Maybe you are technically savvy enough to disable stuff and have a good result. Good for you. My point is the average Joe User does not know how to do these things successfully and can seriously mess up his installation. Then he winds up back here with a problem that is very difficult to troubleshoot and is all of his own making.
How many threads have we seen that start with "I disabled (X) and now my PC won't start..." or something or other doesn't work anymore?
Just because you can tinker with something doesn't mean you should.
I don't, and I rarely, if ever, have an issue with my PC that is not driver or update related. My machine runs like a top, for the most part, and I have all of that "horrible, evil" service bloatware still installed. At least if I do have a problem, I don't have to re-enable a whole bunch of services to rule out a problem with them when I am troubleshooting. I dunno. It seems like a no brainer to me.
If it ain't broke, don't fix it.
(And right to repair is simply corporate greed. Nothing more. Big companies don't give a damn about your stuff as long as they get their money. And then more of it when you are dependent on them for repair. Right to repair does not even count in this case.)
Most users don't even know things like the fact that, much more often than not, blocking all UWP apps in the list of apps that are allowed to run in the background does not make a PC run faster, as the vast majority of these apps don't actually even have the ability to run in the background anyway in the first place. Next thing you know, you get forum posts from users who are wondering why they've missed an appointment after their Calendar app stopped popping up reminders in their Notification Center.
The same with disabling Search indexer. They choose to disable the whole service altogether, not knowing that there can be other things besides Windows Search that rely on the indexing service. To avoid breaking such dependencies, a better approach to get rid of the pesky slow green progress bar that appears in the address bar of File Explorer is to remove folders from the list of indexed folders and/or to add folders to the list of folder exclusions.
I could easily fill up a whole website with more topics like this, but won't. People want to struggle with Windows and Windows software in ways that can simply be avoided? OK. Let them struggle. The more they keep struggling like this, the better IMO. Eventually, their eyes will open. Or not...
Last edited:
My Computers
System One System Two
-
- OS
- 11 Home
- Computer type
- Laptop
- Manufacturer/Model
- Asus TUF Gaming F16 (2024)
- CPU
- i7 13650HX
- Memory
- 16GB DDR5
- Graphics Card(s)
- GeForce RTX 4060 Mobile
- Sound Card
- Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
- Monitor(s) Displays
- Sony Bravia XR-55X90J
- Screen Resolution
- 3840×2160
- Hard Drives
- 512GB SSD internal
37TB external
- PSU
- Li-ion
- Cooling
- 2× Arc Flow Fans, 4× exhaust vents, 5× heatpipes
- Keyboard
- Logitech K800
- Mouse
- Logitech G402
- Internet Speed
- 20Mbit/s up, 250Mbit/s down
- Browser
- FF
-
- Operating System
- 11 Home
- Computer type
- Laptop
- Manufacturer/Model
- Medion S15450
- CPU
- i5 1135G7
- Memory
- 16GB DDR4
- Graphics card(s)
- Intel Iris Xe
- Sound Card
- Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
- Monitor(s) Displays
- Sony Bravia XR-55X90J
- Screen Resolution
- 3840×2160
- Hard Drives
- 2TB SSD internal
37TB external
- PSU
- Li-ion
- Mouse
- Logitech G402
- Keyboard
- Logitech K800
- Internet Speed
- 20Mbit/s up, 250Mbit/s down
- Browser
- FF