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 shell32to 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.

windows xp battery icon not updating-74

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 Tea Rex 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.

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.

Please note that the problem has been completely solved.

You can find the solution in the next chapter, Main problem and complete solution.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.An earlier hypothesis, that 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_Notify Icon in shell32.dll, which has a timeout fixed at 4 seconds.(By the way, don't mistake UPn P for Pn P, Plug-n-Play, which is mostly a different thing.) Microsoft has not taken notice. Some users report successes with various changes that influence the boot and logon timing, but these changes do not reliably solve the problem.