Open information exchange
Active forum topics
There are currently 0 users and 18 guests online.
Systray icons missing
Result statisticsplease report your results.
The system tray (in short: systray, nowadays also called taskbar notification area) is the icon strip normally located near the right end of the task bar, next to the clock.
Some Windows XP installations show a peculiar defect in that some systray icons disappear or, rather, do not appear, when the system is booted and the user logs on. The problem is even more prevalent on systems with autologon. The most frequently affected icons seem to be the speaker icon (sound volume) and the power/energy icon.
Please note that the problem has been completely solved. You can find the solution in the next chapter, Main problem and complete solution.
Hide inactive icons
This has nothing to do with the hide inactive icons settings. The defect shows up when you don't have any icons set for hiding.
In any case, please make sure for now that you haven't activated that setting. Right-click the task bar, click on Properties, uncheck the last check box. You can reactivate it later if all other problems are identified or solved.
In Vista, if the Clock, Network, Volume and Power icons have disappeared and when you go into properties on the taskbar and look at "System Icons" under the "Notification Area" tab, Volume, Network, and Power are greyed out, then visit Paul's Forum and run his fixing program.
2006-08-14 – Glenn S. reminds us that, if other icons disappear for good and never reappear, we should check first whether the programs are started at all.
Check your Startup folder and the starter registry entries through Start, Run..., type: msconfig, press Enter, to check whether the programs are really started at system start, or use Task Manager (Ctrl + Shift + Esc) to see whether the processes are running.
A particular and special problem is that only the sound volume icon disappears, but the others are there. In this case the main solutions below will not work. Instead you have to look at the sound driver. Try to reinstall it. But first read the chapter "Other known causes" further below for some specific symptoms and solutions.
There are a few other problems that can cause similar behavior and can mislead you into believing that they are the same problem. If you are not sure, read the entire article first, because a few more are described later. The ones concerning Task Manager are described in the next chapter, because they can be too easily mistaken for the main problem described in the other chapters.
If, however, your entire taskbar or any major part of it is missing altogether, then the rest of this article is irrelevant to you. Instead the Kelly's Korner tool Taskbar Plus! may or may not help you. I don't know what exactly it does and can only recommend to use it carefully and to use only the function that pertains to solve your immediate problem, then test the result.
UPnP and some general remarks
Often, but not always, the phenomenon of the missing systray icons seems to be triggered by the UPnP User Interface, but more on that later. (By the way, don't mistake UPnP for PnP, Plug-n-Play, which is mostly a different thing.)
Microsoft has not taken notice. The causes are obscure. Some users report successes with various changes that influence the boot and logon timing, but these changes do not reliably solve the problem. Often they make the problem occur less often though and make it bearable.
Be careful not to be fooled by others or by your own brain that may see causality where there is none. People try the weirdest things, then they get all their icons and conclude sharply, but wrongly, that whatever they did solved the problem. About the weirdest and totally wrong recommendation I have seen was to switch off your computer and let it sit without power for three hours. Don't fall into such a trap. The web has a lot of snake oil, particularly in relation to the problem of the disappearing systray icons.
Then there is the fact that some change solves the problem, just by changing the boot and logon process sequence or timing a little bit. Thus I receive hundreds of emails, detailing ever more different solutions to the problem, each of which has been tried and worked on one computer. We have to suspect that each of these many solutions works only on a few computers. If defragmenting the hard disk can solve the problem for some, then anything can solve it, and the solution may not be long-lived either.
2010-10-09 – nars has posted a patcher tool (direct download link, also attached here—see below) that solves the problem even for future versions and makes patching very easy and quick. Thanks a lot, nars!
The main cause of the more common problem is that the systray program is temporarily unable to process icon inclusion requests. An earlier hypothesis, that systray.exe is loaded too late, has been refuted by Thomas Gregory Platt (see his email below).
According to the excellent analysis in the Problem analysis and proposed solution comment by tasmanian this is caused by a timing defect in the Windows function Shell_NotifyIcon in shell32.dll, which has a timeout fixed at 4 seconds. Combined with an unfavorable Windows API message this causes the problem, which befalls many heavily loaded computers that don't have ultra-fast hard disks. Changing the timeout to one minute and removing the unwanted message solves the problem, and in the Complete solution comment user depassp has perfected the procedure of patching shell32.dll to solve the problem, at least until a new version of that DLL is delivered by Microsoft that re-introduces the problem and requires another patch session. In fact, exactly this has happened around July 2010, but the solution is already here: Offsets for NEW 6.0.2900.6018 file by mcrealize, corrected by TeaRex
Unfortunately patching a system DLL is not an entirely simple procedure and can only be done with a certain minimum of computer handling experience, but this is the best we can offer for now.
A few special problems concern the Task Manager and its systray icon only, the green one that dynamically shows the CPU load. If your problem is the disappearing Task Manager icon, then read on. If, however, other systray icons disappear as well, then you should first skip this chapter and continue with the next.
Mike Newhall contributed the following information on 2005-12-10. Thanks a lot, Mike!
One problem is the disappearance of the Task Manager systray symbol when you start Task Manager the second time or subsequent times.
This problem appears to be related to the Classic desktop theme. When you change your desktop to the XP style, the problem no longer occurs. Do this for a test.
The cause is as yet unknown. The simplest workaround is to never close Task Manger.
Another problem is that the icon or the entire Task Manager never appears at all. This can be caused by a registry setting that is not present in a default installation:
You can set this value to zero or, to recreate the default situation, remove the value entirely. To have the value removed automatically, click here and give permission when asked.
In fact, the entire System key does not exist in a default installation, so you can even delete that key if you are sure there's nothing in it that you need.
If any of these solve your problem, please report here.
Log off, log on again
Now we're getting back to the main problem, the sporadic missing of various icons, particularly after the first logon after booting. Typically missing are the power icon or the sound volume icon, but many others can be affected just as well.
The immediate workaround is to log off and log on again (do not reboot, only log off). In many cases the icons then reappear. If not, you can try to repeat the procedure until you have all of them.
If this works, then most likely you have the central problem described in this article.
Wait a minute!
The other workaround is, the next time you boot your computer, wait for a full minute after the logon dialog appears or, better, watch the hard disk light and wait until disk activity subsides entirely for at least 5 seconds. Only then log on and check whether this solves your problem.
On two of my computers this solves the problem entirely, even though other workarounds, like the systray_cleanup.reg file mentioned below, don't work. This also means that you have to log on as quickly as possible when you're trying to test other workarounds.
2006-02-03 – Eric Maier mentioned that you can only delay the logon when you have at least two active user profiles to log on to, or one with a password. If you have neither, the logon prompt wouldn't appear, and there would be no delay.
And, as a final remark, retest from time to time whether the problem has disappeared on its own, particularly after installing a service pack.
Rooting out the problempatching shell32.dll
Oour users cooperated to find and program the fundamental solution to the problem. The cause has been determined as a defect in shell32.dll, a Windows component. Please see Main problem and complete solution above.
The Ostuni Workaround
2004-11-11 – Francesco Saverio Ostuni wrote: "... I found a solution for me that works perfectly. I simply went to My network Places and on the left pane I chose to Hide UPnP devices. This operation does not disable the service (which I need)."
To see this choice, you have to have Tools, Folder Options, Show Common Tasks selected.
This is still one of the most successful and not very intrusive workarounds, so you could try it first. I keep getting emails stating that the Ostuni Workaround worked well and solved the problem.
See also the subchapter on some more details below.
Cleaning up the registry
The following text contains links to registry setting files, which, except for the first one, are a bit stronger than the straight Ostuni workaround. If you want to check what they do before actually applying them, you can right-click on the link and elect to save the file to your hard disk. Then you can open it with a text editor like the Windows notepad editor and see what they do.
After two emails (see emails from Mark Medrano and Ingo Schupp below), the suspicion grows that the PastIconsStream registry entry can grow beyond proportions and hinder the systray icons. The solution is to click on systray_cleanup.reg, confirm the execution, then confirm the registry change, reboot your computer and test.
These registry entries can safely be deleted, because Windows automatically recreates them after the next two reboots. By the way, this registry file does about the same as running systray.reg and then systray_undo.reg (see below).
2007-01-16 – Thanks to Haris J. S. for the following information: This and the fixes below reset the inactive icons timers, so for some time like a week or two there will be no inactive icons. They will come back later on their own.
More radical: stop UPnP services
If the workarounds described don't work for you for any reason, read on. Before we go into the details, if you still want a quick solution and don't mind that a few settings, including any Explorer policies, are reset to their defaults, you can click on systray.reg, confirm the execution, then confirm the registry change, reboot your computer and test. Unlike the softer Ostuni workaround this disables both services, SSDP and UPnP, altogether and also cleans up the registry as described above. Since the Windows Media Player network sharing service depends on the UPnP service, it also gets stopped, so if you need that, you cannot use this workaround.
If this still doesn't cut the bill, you can try this stronger one: systray_plus.reg, and again confirm, reboot, and test. However, the old poll results show that few users actually did this successfully, so we may consider this workaround undesirable and not waste time on it. I leave it here just in case somebody wants to experiment with it.
You need to do this only once. The changed registry settings are permanent, until you undo them.
If none of the above works for you or if you later need the UPnP services, you can undo the nonstandard changes and reset them to their defaults with systray_undo.reg, but note that any previously removed non-standard settings, like Explorer policies, cannot be reinstated. In a normal installation there shouldn't be any such settings. A reboot is again required to make the change effective.
If you've tried these, please report here which one worked or didn't work for you. Please try them in the order below, like this:
Please test more than just once if the problem is sporadic. It is important for all of us to also learn which one didn't work.
Results from since 2006-11-10:
If you want to know what these files do or if you just want to keep them, you can store them by right-clicking on the above links and choose to save the target on your computer. Then you can open each file with the Notepad editor (Open with ...) and, if you like, make the registry changes by hand. They do a bit more than what is described below. The minus signs in the files indicate deletions.
A new program
Alex Milner has written the new program TrayIconsOK!, downloadable from http://am.vghost.ru/, which purportedly solves the problem permanently (but not the sound volume problem). Thanks, Alex! The program delays desktop loading by some adjustable seconds, and that seems to do the trick for many installations, but not for all.
This is shareware with a single-digit $ price. The unregistered version is fully functional for 30 days and has a nag screen. You can test it thoroughly before having to pay up.
If you've tried this program, please report here if it worked for you. Older results of 2007-02-06 to 2007-07-21:
The Diez Workaround
2006-06-30 – Steve Kreideweiss wrote from Cairns, Australia: "I tested the tip from Jose Luis Diez setting SSDP and UpnP to Automatic. This seems to work fine for me as well. I was wondering why it was on Manual at all?"
So please read the hint from Jose Luis Diez below or just read on. Apparently this changes the boot and logon timing enough on some computers to make things work. On one of my computers just setting the SSDP service start type to automatic did actually solve the problem.
Here's the quick way to test it. Click on the desired setting, then confirm as often as needed, then reboot and test.
Change settings to automatic:
Change them back to their default setting of manual:
You have to reboot each time to apply the settings and test.
If any variant of the Diez workaround solved your problem, please report here.
Emails received before 2007-07-21:
Unfortunately the statistics don't look too good. If we don't get a number of successes soon, this subsection will have to disappear. But read also the following:
2006-10-11 – J. L. Heath wrote:
More details of the Ostuni Workaround
Francesco Ostuni further mentioned that the same can be done through Control Panel, Add or Remove Programs, on the left side: Add/Remove Windows components; select Networking Services, click on the Details... button, remove the checkmark for the UPnP User Interface, then click on OK. The result is the same. Now the icons are back every time at each reboot.
This has meanwhile been confirmed by many other users and consistently kept a success rate of well over 90%, so we can conclude that this solves the problem on all but the most unusual Windows XP installations.
Thanks, Francesco, in the name of the many systray users you've made happy!
Apparently this option is only there after Service Pack 2 is installed. I'm not sure whether and how this would work in Windows XP installations without SP2.
It is as yet unclear what exactly the UPnP User Interface does, beside opening two ports. Any information is welcome.
Several people including myself suspect that the UPnP interface does not directly cause the problem, instead there seems to be something wrong with the load order or timing. Perhaps the UPnP interface hogs the system in a way that blocks the systray for too long on some computers.
2005-03-13 – Volker Severt wrote that a side effect of having the UPnP User Interface installed already makes the UPnP devices visible, namely that the relevant ports are opened in the firewall. If you uninstall the UPnP User Interface, these ports are automatically closed, but you can reopen them by hand. They are TCP 2869, subnet, and UDP 1900, subnet. Thus you can still have the UPnP devices visible.
2005-06-15 – Jose Luis Diez wrote the following intriguing email (see also the subchapter "Diez workaround" above for the short step by step instructions).
2005-07-17 – Michael Fornoff wrote:
2005-07-18 – M. D. Harper wrote:
2005-10-15 – Drystan Brod wrote:
Done, but instead of using a big, obscure program, you can just as well use the tiny, open-source systray.reg registry script to stop the UPnP services (see above), or you can even disable them by hand in less time than it takes you to download the program.
2005-10-19 – Richard (Rick) Murphy wrote:
Thank you too, Rick, for your good report and, of course, for the generous donation!
2006-04-03 – D.K. Kraft wrote:
D.K., thanks for the good information and the nice story!
2006-04-20 – Dwayne Osbaldeston wrote that disabling the two services solved the systray problem, but also disabled a Palm Pilot hotsync function. He was able to get that to work again by reserving a fixed IP address for the computer and using that for hotsyncing.
2006-04 – In some web forums it was reported that Windows Live OneCare (WOC, WLOC) or Defender triggered the problem, but the above workarounds worked for them.
If disabling the UPnP service altogether solves the systray icon problem, but you needed UPnP, you can work around it by using a fixed IP address and opening ports on the router directly. If you use a router that allows you to assign a fixed IP address to a certain computer (by MAC address), fine. If not, simply give the computer a fixed address outside the router's DHCP range.
Analysis of possible causes—PastIconStreams and timing
2006-11-10 – Mark Medrano sent in the following intriguing information. Please note that the newer file systray_cleanup.reg already cleans out the big registry entries he mentions, so try this first and move on to the more severe systray.reg only if the former fails to solve the problem. Here is Mark's email:
2006-11-16 – Ingo Schupp confirms this as follows:
2006-12-15 – James Covington sent these Microsoft support instructions, some of which overlap information already given on this web page. But he wrote that this procedure always fixed the missing icons problem for some time, then needed to be repeated.
2007-05-19 – Thomas Gregory Platt confirms that cleaning out these registry entries solves the problem for him too. He also wrote the following, intriguing message, whose core, I believe, is true or close to the truth and refutes my earlier suspicion that systray.exe is loaded too late. Thanks, Thomas! I have already amended this whole web page accordingly, so the following message now no longer appears as a correction:
This is an error message that some programs, apparently all written in Delphi, show when they cannot reach the systray task to put their icon into the system tray. The most prevalent of these programs is Asus Probe. Most other programs don't throw an error message, but instead simply forgo creating an icon if they can't do it instantly. Both behaviors are insufficient, as we know.
This problem can be solved with Startup Delayer (see below) and by other means of delaying the startup. One of the simplest is to enable a splash screen like described here:
2006-09-14 – Eric-Jan Damen writes that his problem with the Asus Probe systray icon appeared after he removed the check mark to "show up on next execution" in the splash screen. The delay caused by the splash screen may be enough to make it work.
To re-enable the splash screen for Asus Probe, after you've already disabled it, click on AsusProbeShowSplashScreen.reg, confirm as often as needed, then log off and log on again to test it. (Works only for Asus Probe, other programs have their settings at a different location in the registry or elsewhere.)
If that doesn't solve the problem and if you want to do it yourself, you can do it as follows.
Write a little program in Visual Basic Script that delays the start. Create a text file (File, New, Text file, or just open an Editor) and copy the following two lines into it:
The delay time is in milliseconds, 240,000 in the example. Everything to the right of the apostroph (') is only a comment, has no function, and is not required. To solve the problem here, a delay of 30 to 60 seconds suffices, but if you also have the problem that a regulated fan triggers an alarm when cold-started, 4 to 8 minutes may be required.
Save the file under the name DelayedStartup.vbs into the folder where the AsusProb.exe file resides. If the path is different from the one in the second line, change it accordingly. Actually, the file can be anywhere else, if you like, if only you enter its path into the registry as described below.
Test it. Close Asus Probe, then double-click on the VBS file in Windows Explorer, but double-click only once. There is no apparent reaction and no window opening. You have to wait for Asus Probe to appear after the given time. If you're in a hurry, you can shorten the time to a few seconds for the test, then change it back after the test.
Open regedit (Start, Run..., regedit) and change the following value.
Double-click on "ASUS Probe" on the right side and change the value to read:
The path given in the above example may not be the same as on your computer. Adapt it accordingly.
Log off and log on again to test the change. Asus Probe should appear after 4 minutes or after whatever time you entered.
If you want to use this program to start several programs delayed, use the following example.
Repeat the last two lines as needed.
Note that some programs may reinstate the original situation when they are installed, reinstalled, or updated. Then you have to make the changes to the registry again.
User ClearAsMud remarked that this method can be used for systray icons as well, if you write the program such that it starts the respective programs with delays. Of course, the normal start of the programs would have to be disabled and the delaying program amended whenever a new program with a systray icon is installed or an old one removed.
Make sure first that you either don't have the following registry values at all or, if you have any of them, that it is set to zero. Deleting the value entirely is easiest and safest. If you want to have all of them removed or set automatically, just click here, then give the permissions when asked.
2005-04-05 – Reagan Wiliams reports that in Windows XP (2002) a similar value with the same effect is here (meanwhile confirmed):
It is easiest and safest to just delete that value, but if it is all zeros, it should have no effect either. If it is non-zero, that may be the cause of your problem.
2005-10-06 – Christian from Germany wrote that you should make sure you do have the following value, which should exist in a normal installation. Its absence may cause the problem:
Check also the message "2007-04-21 – Karel" below, which also refers to this GUID and shows how to restore a missing InprocServer32.
2005-10-25 – Keith Sagona wrote that the DisableLocalUserRun registry value should be set to 0, not 1. Even a repair installation of Windows XP does not appear to fix this.
If this value is set to 1, that may be the cause of the problem. Search the registry for other instances of that setting, particularly in HKEY_CURRENT_USER, and set those to 0 also. Then reboot. In many installations this value doesn't even exist. In fact, in many normal installations the entire registry key Explorer does not exist. You can try to back up that key by exporting it, then delete the entire key for a test.
Unfortunately the absence or presence of these keys and values does not guarantee that it all works, and it is not clear whether some of these values work only for some people because they change the logon timing.
Also make sure that you don't have the taskbar set up the wrong way. Make sure that the quickstart icons are on the left side, not on the right, and the running programs area is in the middle of the taskbar. If they are arranged the other way around, then unlock the taskbar and drag the program icon area far to the right, between the quickstart icons and the system tray (system notification area). Then use the sliders to use the available space optimally and relock the taskbar. If this solves your problem, be happy. The problem for which most people visit this web page is much more intractable.
2006-05-12 – Asa Jay Laughton wrote that Norton AntiVirus has a specific setting to hide its systray icon, so if that is the only icon is missing on your computer, please read: How to hide the Norton AntiVirus Corporate Edition icon from the desktop of NAVCE servers or unmanaged clients on Symantec's web site.
2006-05-13 – Poul Eric Madsen wrote that the spyware program regperf.exe caused his Norton AntiVirus icon to disappear, and only spyware removal, followed by a repair installation of the Norton program brought the icon back into the systray. A full Norton reinstallation didn't do the trick, only the repair function worked.
It may be worth noting that various malware attempts to deactivate some well-known antivirus and anti-spyware programs, and that may also affect their systray icons. Also, Symantec/Norton software is generally not recommended, because it causes a variety of other problems.
2006-07-14 – Steve McAfee wrote:
2006-08-09 – Mikael Tilly wrote to confirm Steve's findings.
2006-08-10 – Hakan Turan also confirmed:
2006-09-10 – Tomer confirmed.
2007-03-19 – Bruno Zumella wrote:
2007-04-05 – Nalin confirmed.
2007-04-14 – Joe confirmed and mentioned that the problem appeared after he uninstalled the quite popular ffdshow codec.
2007-04-21 – Karel wrote:
These entries are there in every normal Windows XP with Service Pack 2 installation, so it usually doesn't hurt to re-enter them. If they are already there, nothing will change. You have the following choices:
New information is added at the end of this chapter, so you can read on, but skip to the last paragraphs if you get bored. Thanks to everybody who contributed useful information!
In spite of the apparent effectiveness of the Ostuni workaround, I'm still looking for a way to make the systray icons show up without having to disable or uninstall anything. So the search is still continuing.
Anything that streamlines or delays the boot and logon process appears to help in many cases, though not all, for example thoroughly defragmenting the hard disk with a good defragmenter like PerfectDisk by Raxco. Other examples keep being reported, but none is a real solution. They all work on some computers, but not on others, usually by disabling something and thereby changing the boot timing. Typical culprits are slow, inefficient virus checkers that are set to automatic, like Norton Antivirus 2005 Pro.
First give your user account a password, so the computer cannot rush through a quick auto-logon.
It clearly helps (on at least one of my own computers) if the user waits until he actually logs on. You may enter your password, but do not immediately press return or click on the OK button. For a few thorough tests wait at least a full minute before logging on, or wait until disk activity subsides. You could watch the hard disk light, memorize the rhythm of the bursts, which is usually always the same, and the next time wait until after the last big loading burst. If this helps, it probably does so by getting some system (particularly network) loading processes out of the way.
As mentioned above, disabling the UPnP (Universal Plug and Play) service or the SSDP (Simple Service Discovery Protocol) service or both solves the problem. Microsoft proposes the latter in http://support.microsoft.com/kb/841571/. However, this is not a very good solution because you may want to have these services running. Another proposal is to set the start type of these services to Automatic. They are by default set to Manual, and at least the SSDP service is nonetheless started automatically by other means. Setting the SSDP service to Automatic would likely let this service start earlier, so it doesn't get in the way of other software that is loaded later.
2005-03-10 – Rob Nunn wrote that his Systray icons fail to appear exactly on those days when his antivirus program, NOD32, updates its virus definitions, which it does after first being loaded, i.e. just after system boot. This, of course, uses the network connection. My first thought is that, if one could delay the antivirus update by a minute, the problem might not show up.
2005-04-10 – Stein Bjorndal reported: "... a process named sdmcp.exe crashed on me. After a bit of investigation, this turns out to be a part of the DesktopX application by Stardock (http://www.stardock.com/products/desktopx/), ..." Uninstalling the program didn't work for him either, so he just erased all traces that could be found, including the start of the exe file. That solved his problem.
This has meanwhile been confirmed by two other users, Gary Melady and David Perry. The culprit may be Stardock Central.
2005-05-21 – Daron Brewood wrote: Solved my icon problem in the end by disabling WindowBlinds 4 (I had to as it conflicts with the new Pocket PC Active Sync program) – but it has the side effect of fixing the icon problem, so in my case it looks like it is/was due to WB4.
2005-06-14 – Ansgar Nell sent an intriguing hint, originally written by Guloso on a discussion board—just restart systray.exe, for example by putting a shortcut to it into the startup folder. No need to provide a path, since the program is in the search path. I have meanwhile received an email confirming this, but it doesn't work at all on my own computers. Another of those solutions that work for some, but not for most. I have heard of one case in which systray.exe didn't get loaded at all, and using this method or the one below fixed the problem.
A similar, possibly better method to start systray.exe is through the Run key in the registry. Unfortunately this also doesn't bring any missing icons back on my computers, but if you want to try it nonetheless, the procedure is as follows.
Another of these hints (thanks to John Erikson) is that emptying the Prefetch folder (C:\WINDOWS\Prefetch in a normal installation) helps. The file Layout.ini is automatically recreated at some later time and is not essential anyway. Just cleaning out the prefetch folder did not solve the problem on my test computers and I also get reports from other users that it doesn't solve the problem there, so it is obviously not a universal solution. I guess that it merely speeds up the logon process a little.
2006-10-23 – WvU wrote that deleting Prefetch\Layout.ini, then defragmenting the hard disk, solves the problem for him. He supposes that the defragmenter has a defect in relation to rearranging the boot files according to Layout.ini.
Yet another hint came from Harold Collins. He used the MSCONFIG utility to disable the Adobe Reader Speed Load, which solved the problem for him. This is apparently yet another way to accelerate the loading process for the other systray icons and may work for some.
www.tech-pro.net provides a tool set named Tech-Pro Utilities Startup (http://www.tech-pro.net/startup.html Version 1.1 as of 2004-11-22), which contains one tool named Startup Manager. You need only the Startup Manager for this particular problem. This program can delay the loading of programs from your Startup menu and allegedly solves the missing systray icon problem.
I have my doubts though, because most of the possibly offending programs aren't started from the Startup menu at all, mine is empty, for example. I guess we need something to delay the loading from the Run key in the registry. But if you try any of these programs, please let me know your results.
2005-01-26 – Found a program named SysTrayHack at http://desktopian.org/addons/systray2kfix.zip and tested it. It claims to solve the problem of not appearing systray icons when another shell is used in place of Windows Explorer. I tried it, although I do use Windows Explorer. As expected, it didn't solve the problem for me, but I have received 2 confirmations that it worked for other users.
2005-02-16 – Lutz-R. Frank wrote:
Thanks, Lutz! This is indeed promising. The program is try-before-you-buy shareware and costs $24.95. I haven't tested it yet and will wait for independent confirmation.
2005-02-17 – Cliff Cawley of r2 Studios contacted me and recommended his freeware program Startup Delayer, available from http://www.r2.com.au/software.php?show=startdelay. 2005-04-01 - Bruce Sylvester reports that he tried Startup Delayer after the Ostuni Workaround hadn't helped. His statement: "Voila! Works perfectly and problem gone." 2005-10-12 – I finally got to testing it myself and can recommend it with some reservations. The program itself works very well and does exactly what it should do—delay starting the automatically started programs. Unfortunately it does not solve the entire problem on my computer. Some of the missing or disappearing icons will still not appear if delayed, or they will never appear when delayed. Examples are the Bluetooth icon and other icons that depend on it, like that of the Nokia PC Suite. Startup Delayer seems to work well with the SoundMan icon though (the speaker symbol to control the sound volume) and with several others, like Asus Probe. It also appears to have a perfect installer and uninstaller, so there is apparently no risk in trying.
2005-05-16 – IceBear wrote:
2005-07-20 – Dan Berger wrote:
2005-10-11 – Vivek Tanna outlined the following procedure:
Unfortunately I cannot confirm this. Sometimes it works for me, but usually it doesn't. Some icons do not return, even if I repeat the procedure. But try it anyway, perhaps it works well enough for you.
2005-10-21 – Anastasia wrote that one method of last resort is to give up the user profile, create an entirely new user, and copy as much data and settings as possible from the old user to the new. She then wrote:
A remaining problem is any software that had been installed for this user only, because that would have to be reinstalled. But if all else fails, this is still a way out.
2006-01-16 – Larry Bowman wrote about a last resort workaround. You can create shortcuts to the programs that belong to the missing icons. For example, you can create a shortcut to sndvol32, so you can always get the volume control, albeit the big one. Or you can right-click the Sounds and Multimedia applet in Control Panel and create a shortcut to that, so you can get your volume icon back with a few more mouse clicks (disable the icon, apply, enable the icon, OK). With similar shortcuts you may be able work around all or most missing icons. Another example for such a shortcut is this, which you could call Hardware Unplug:
rundll32.exe shell32.dll,Control_RunDLL hotplug.dll
2006-09-28 – Bart van de Beek wrote:
Unfortunately on many computers this delay is not enough to prevent the problem, but, like many other workarounds, it seems to solve the problem on some.
2006-11-22 – Lawrence LaCroix wrote:
2006-11-28 – Lawrence LaCroix wrote about an interesting point again:
2006-12-13 – Pete Green wrote:
Windows XP has a similar automatic function already built in, which is enabled by default, so it is a question why that didn't already solve the problem, but Pete mentioned that, even in a test with an earlier disk image, it was only Bootvis that solved the problem in his installation.
2007-04-29 – Bob Malcolm confirmed that the Bootvis optimization function solved the problem for him too.
2007-02-17 – Paul Santangelo wrote that he had one particular case of the disappearing systray icons where he found that something was wrong with the .NET 2.0 Framework installation. Calling up the installer again and electing to repair the .NET installation fixed it permanently.
2007-05-11 – John Smallridge wrote:
Thanks, John, for this interesting observation! This also indicates that my earlier suspicion, that systray.exe loads too late, is wrong, and that a more likely cause is some kind of overload on systray.exe.
2007-05-13 – TUPOLEV wrote from France that deleting the following registry value solved the problem for him:
If you don't like to delete the value altogether, you can just make it temporarily unusable for a test, for example by adding DISABLED in front of the opening brace of the string value.
2007-06-14 – Brian Burdett wrote:
2007-06-21 – Jali Pajula wrote from Finland:
Cited emails can be edited and abridged to fit this web page.
Thanks to everybody who wrote! If you have any further relevant information or found one of the above hints to work, please click on Add new comment or on reply to reply to an existing comment (below, account required; if you don't have an account yet, create one first).
Please check also the result statistics and report your results there.
Result statisticsplease report your results.
Recent blog posts
Windows news ticker