The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    background processes

    Discussion in 'Windows OS and Software' started by bobfet1, Oct 27, 2005.

  1. bobfet1

    bobfet1 Notebook Consultant NBR Reviewer

    Reputations:
    12
    Messages:
    135
    Likes Received:
    0
    Trophy Points:
    30
    How many background processes dose WinXP pro require?

    I just got my computer, and right from the start there are like a million processes going! Plus the little system tray thing on the right side of the taskbar has like 10 things in it!

    I had Symantec IS 2005 on it, so I add/removed that, but didn't decrease the number of processes that much.

    Is this just how notebooks are? This is an asus so there isn't really any bloatware on it except the symantec.
     
    bobfet1, Oct 27, 2005
    #1
  2. drumfu

    drumfu super modfu

    Reputations:
    436
    Messages:
    3,651
    Likes Received:
    0
    Trophy Points:
    105
    i think with a fresh install of the OS, the # of processes is about 20-22.

    for the sys tray, there are only a couple things running.
     
    drumfu, Oct 27, 2005
    #2
  3. DownByFive

    DownByFive Notebook Consultant

    Reputations:
    426
    Messages:
    153
    Likes Received:
    0
    Trophy Points:
    30
    Well, if you are using Proset, that's like 5 processes, and then there's the ATI (or Nvidia) stuff, which is probably 2-3. Then there's HControl, the ATK util, the sound drivers...it starts to add up. I've got mine pared down to about 32, since I don't use AV. I just have Hcontrol/ATK, CHC, and Proset as the only (I think that's it) non-windows processes at startup. Just use MSConfig to experiment with what needs to run and what doesn't. You'd be surprised at how much stuff Windows DOESN'T need to run properly.
     
    DownByFive, Oct 27, 2005
    #3
  4. Charles P. Jefferies

    Charles P. Jefferies Lead Moderator Super Moderator

    Reputations:
    22,339
    Messages:
    36,639
    Likes Received:
    5,078
    Trophy Points:
    931
    If you go to Elder Geek on Windows XP , you can get great info on what processes you should leave alone and what to get rid of. Great site!
     
    Charles P. Jefferies, Oct 27, 2005
    #4
  5. myrancid

    myrancid Notebook Enthusiast

    Reputations:
    0
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    5
    myrancid, Oct 28, 2005
    #5