Jump to content


Popular Content

Showing content with the highest reputation on 10/31/2010 in all areas

  1. The problem with people disabling services is that when they go to install a new software or hardware that may/is dependent on a certain service you disabled, it will complain or not install. It's especially a pain in the ass when people disable their services, then bring their machines into the shop talking about something not installing or function properly when it's because they disabled services follow those idiot's guides to disabling services. Idle services take up no resources at all. So disabling all those idle services isn't changing a thing. If you knew what you (not you as in YOU, but you as in anyone) were doing, you'd know not to disable services at all. Also, disabling idle services offers zero performance gain. Idle services take no RAM or CPU power at all. I'd love to quote the MSDN article, but I can't find it at the moment. The basic summary is that disabling a service that wasn't doing anything frees absolutely no resources. You should never disable the error reporting service either. Error reporting allows the end-user to obtain information after "serious error" crash dumps (STOP errors/BSoDs). It also provides the user with feedback if an issue has already been resolved. Example: http://support.microsoft.com/?kbid=894391 I had submitted an error report about this crash one day, and got no response back. The problem kept happening, and on multiple computers, so a few days later, I submitted it again, but this time, error reporting took me to a page stating that the cause was unknown but it research was in progress. Four days later, I submitted it again, and it took me to a page with the patch and the error never happened again. There will be a program just to undo all the bull**** that users are doing to their systems these days, including disabling what they think are "unused" services. If there weren't used, why would they exist? If they were unused, then they would be idle, and not taking up any resources at all. When the time comes to use the service, it will work fine, and all will be well. 6 months later, a program attempts to use a service that you've disabled because you think you are better than your OS, and you get a generic error: "The RPC server is unavailable". Now you think that the program you're using is a piece of crap, or Windows is a piece of crap, and you format/reinstall, and it works for a while... until you do your "tweaking" routine again. In summary, if you continue to disable "unused" services, and I meet you on the street, I should punch you right there in the center of your face. 100% Accurate Tweaking Guide. In fact, it's the only one you should ever listen to. My bottom line is I really hate stupid people. As far as I'm concerned, people who screw with their services fall into that category; because they obviously are lacking the intelligence to leave the services well enough alone.
    2 points
  • Create New...