Taskbar Icons

[mcmxli]

As do most users of Windows XP (Home with SP1), I have programs set to load when Windows is started. Many of these programs are set (at my option) to display an icon in the (system tray of the) taskbar. However, two of these programs, while always loading when Windows is started -they show up under the Processes tab of Windows Task Manager-their program icons do not always display in the taskbar. Sometimes they display and sometimes they do not display. When they do not display, I open Windows Task Manager and manually delete their process then manually reload the programs whereupon the program icons correctly display in the taskbar. Also, I have a third program which is suppose to load when Windows is started and is set to display an icon in the taskbar. However, this program does not always load when Windows is started. Sometimes it loads and sometimes it doesn't load. When it does load, it does display the program icon in the taskbar. When it does not load, I have to manually load it whereupon the program icon appears in the taskbar. In addition to this, The Sound and Audio Devices Properties is set to always display the Volume icon in the taskbar but it doesn't always do so, requiring me to open up The Sound and Audio Devices Properties (in Control Panel) and uncheck "Place Volume Icon in the Taskbar", click the apply button, then recheck "Place Volume Icon in the Taskbar", then click the apply button whereupon the Volume icon appears in the Taskbar.

Does anyone have any ideas as to what is causing this erratic behavior as I have described it and how to correct this problem so that these programs always run and the program icons (including the Volume icon) always display in the taskbar so that my manual intervention is not required?

[Mhollinr]

I have experienced the same thing. I have a laptop and sometimes the power icon doesn't show, sometimes the bluetooth icon doesn't and a few others. I have searched for this problem, but never found a reason for it.

[mcmxli]

Well it's "nice?" to know that I'm not the only one with this problem. There are just too many things to track down the reason/cause for this problem:wrong data/flags set in the registry?;msconfig?;specific configuration file associated with the program?, etc. It's more of a nusance then a major problem, but still something is causing it. Guess we'll just have to live with it.