NeoSmart Technologies' ToolTipFixer 1.0.0


Recommended Posts

Press Start | Programs; and right-click on "Accessories," then press "Open." Close the window that opens up, then go to your taskbar (next to the system clock) and hover over an icon, what do you see?

If you're using anything from Windows 95 to Windows XP, chances are, you're just about to experience The Wow - a 14-year-old bug that Microsoft finally admitted to in 2006:

Before.png

Microsoft's advice? Reboot your PC.

NeoSmart Technologies' ToolTipFixer 1.0.0 is a patch to address this issue that Microsoft refuses to fix: just run the (free, small) patch once, and you're set. If you want your messed up tooltips back, just uninstall it and no harm done!

Not tested on Windows Vista

After.png

linkicon.gif Link: Windows XP's ToolTip Bug.. Fixed!

softicon.gif Download: Download ToolTipFixer 1.0.0 (88kb)

souricon.gif News source: NeoSmart Technologies

Edited by Computer Guru

It happens to everything >.<

The technical explanation is that in the Win32 API, tooltips are coded to have HWND_TOPMOST as their z-index - meaning that they are on top of everything.

However, due to a series (many) (obvious) bugs and miscodings in the Windows Shell, when you perform certain actions with dialogs and Windows that are supposed to appear above current windows (like the context menu when you right click the start menu items) end up coming even above the HWND_TOPMOST entries as well - that's not supposed to happen.

Then it seems (from here on in, i'm only guessing based on what i can see) that the parent window/dialog (in this case, the start menu, then the taskbar) inherits the window status when the child is closed, and keeps it.

Think of it like Dominoes. The first window is made topmost - no problem. as it closes, it's parent takes that z-index. then its parent, and the next, and the next - until you end up with something in the same x-y plane as a HWND_TOPMOST item, and it ends up with a lower z-index; therefore obscuring that item from view.

Basically, it is something that could be avoided by properly handing off z-indexes and keeping these always under HWND_TOPMOST items.

You are mighty welcome, guys.

I do not use XP anymore to use this, but finally a patch! That was the most annoying thing about XP for the years I used it :angry:

I formatted my Vista two weeks ago, haven't looked back - can you tell me if you follow the steps at the very top of the original post, do your taskbar tooltips get messed up?

I know I saw it once or twice in the 8 months I used Vista RTM; but I don't know if it is 100% reproducible like it is in XP.

You are mighty welcome, guys.

I formatted my Vista two weeks ago, haven't looked back - can you tell me if you follow the steps at the very top of the original post, do your taskbar tooltips get messed up?

I know I saw it once or twice in the 8 months I used Vista RTM; but I don't know if it is 100% reproducible like it is in XP.

No, I haven't seen it ever in Vista and doing the steps aforementioned yielded no results. Looks like they fixed it in Vista.

Hmm. Runs on startup, creates a t.txt in my root, eats up 8 mb of ram, and made an unrecoverable system error after install.

Sorry, but looks rather dangerous.

Also, I don't know since when, but I don't have that problem on my computer. Tried the right click open thingy... Nothing happens.

t.txt is a left over from the debug process, it used to contain the all the HWND_handles for open win32 controls. Must have forgotten to remove it - now it just creates the empty file without writing the handles to it. I guess the inevitable .0.1 build is coming out soon to make t.txt disappear :)

Kill ToolTipFixer.exe in taskmanager than try the right-click, open thing and see if you still have that bug. (what OS)

I'm running Windows XP SP2 manually slipstreamed along with all the other patches and everything.

I tested this in classic and normal mode with the taskbar set to auto-hide or not and with it set to to top, bottom, or side. Each time it could be reproduced so long as tooltipfixer.exe was killed.

Running tooltipfixer.exe fixed the problem and prevented it from happening again.

I'm running Windows XP SP2 manually slipstreamed along with all the other patches and everything.

I tested this in classic and normal mode with the taskbar set to auto-hide or not and with it set to to top, bottom, or side. Each time it could be reproduced so long as tooltipfixer.exe was killed.

Running tooltipfixer.exe fixed the problem and prevented it from happening again.

I uninstalled it and still don't have the issue :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, unpacking and setting up the smart scope + tripod for equatorial tracking, mucking around with settings, maybe shoot some calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!