Recommended Posts

Can't replicate that at all and never seen it. GFX driver or mouse driver issue?

It's not that easy to see and as we've established it's impossible to just replicate with any precision. I was actually going to make a thread about this as it happened to me for the first time after a few months on build 7068.

With the amount of people reporting it I doubt it's any specific driver. This looks quite obviously like a bug in the OS if you ask me.

I'm not that impressed that it will most likely still be in the RTM. Around the time that it happened I also noticed a lot more taskbar preview windows getting "stuck" after you move the mouse away from them as well as the tooltip for an inactive taskbar icon sticking in the same way the highlighter does. Do any of you running the RTM-ish builds get these symptoms too with this bug?

Happened to me once or twice before 7264 builds. After that though, never had any more of these bugs and I'm using Windows 7 exclusively. What is your graphics card and what driver are you running? Make sure it is an updated one and not the one included in the build.

It is not graphics card specific for me. Saw it on all my systems (intel/ati/nvidia) at least once. Though only runnning build 7600 16385 on my notebook for now and it happened in just the same way as on older builds. So, naturally I expect all my other systems to still have this bug in this build.

i think lot of people are facing his bug & it definitely is not a driver issue. the problem is that this issue occurs randomly & is non reproducible what ever we do to reccur it. it is with taskbar itself i believe coz the problem goes away at restart of explorer.

It happened to me once in three months (taskbar thumbnail previews dissapears too). But the problem it's gone if I open a program with middle click, on IE for example. Also if I unlock and lock again the taskbar or killing the explorer process.

My graphics card is an ATI Radeon 9600 and the drivers are the same from the Windows 7 DVD so I doubt it's a drivers bug.

How can they call this build golden code when obviously it is flawed, when they failed to remedy this obvious error what other serious flaws have they overlooked.
It's not uncommon for minor bugs to be pushed back to later updates when the development focus is on getting blockers fixed for release.
How can they call this build golden code when obviously it is flawed, when they failed to remedy this obvious error what other serious flaws have they overlooked.

Only un-confirmed sources are calling it the finished article though .. let's wait for Microsoft for the real thing.

post-23540-1248189978.png

its not a bug

attached above is my taskbar as currently running with "The bug" as some of you put it;

Opera is the currently selected window (On main display)

Outlook is minimised

RDC Is running on another monitor (I am running extended desktop display and RDC exclusively has that monitor to itself)

WLM Is running minimised.

So as you all can see, there is no bug as such. As i see it, the only thing that can be causing this is programs to not be closing down correctly so the system thinks they are still running in background.

post-23540-1248189978.png

its not a bug

attached above is my taskbar as currently running with "The bug" as some of you put it;

Your taskbar is NOT showing the bug. All your programs are running and minimised or focused.

On our screenshots, there are running programs, focused programs and programs that look as if the mouse was still hovering them. The ones with the mouse hovering ARE the bug.

post-23540-1248189978.png

its not a bug

attached above is my taskbar as currently running with "The bug" as some of you put it;

Opera is the currently selected window (On main display)

Outlook is minimised

RDC Is running on another monitor (I am running extended desktop display and RDC exclusively has that monitor to itself)

WLM Is running minimised.

So as you all can see, there is no bug as such. As i see it, the only thing that can be causing this is programs to not be closing down correctly so the system thinks they are still running in background.

What you wrote has nothing to do with the bug people are experiencing.

It's happened to me a few times. It really bugs me. It seems to fix itself if you change your taskbar icon size to small then set it back.

Yeah, that is why they call it a bug in the first place. :laugh:

This happened once in a while in some of the earlier leaked builds, but have not seen it once in 7600-16385. Never really figured out how to replicate the bug, but it seems like it might only happen when your computer is crawling and doing a lot of work. Could be graphics related. Hard to say but it seem fixed by now.

Why are you guys hovering over icons on your taskbar if you are not going to do anything other then stop hovering over them?

I?m am going to take a wild guess and say 99,9% of windows 7 users will ever notice this bug without being told about it and they trying to reproduce it

Why are you guys hovering over icons on your taskbar if you are not going to do anything other then stop hovering over them?

I?m am going to take a wild guess and say 99,9% of windows 7 users will ever notice this bug without being told about it and they trying to reproduce it

In fact, this bug can cause quite a bit of confusion to regular users. When the highlight sticks and does not disappear and you have some programs open and others not, you end up with 3 permanent states for the icons (when you should only have 2, ie. open/closed). So instead of having to distinguish between open program icon and regular icon you now get some weird highlighed icon that just stays there.

In fact, this bug can cause quite a bit of confusion to regular users. When the highlight sticks and does not disappear and you have some programs open and others not, you end up with 3 permanent states for the icons (when you should only have 2, ie. open/closed). So instead of having to distinguish between open program icon and regular icon you now get some weird highlighed icon that just stays there.
My point being that this bug happens when you hover over an icon and then leave it with out doing something, that never happens, you hover over it to do something (open,close, checkt status etc.)
My point being that this bug happens when you hover over an icon and then leave it with out doing something, that never happens, you hover over it to do something (open,close, checkt status etc.)

No... the bug happens randomly, you launch something from the taskbar, and then move the mouse away but the taskbar will randomly think the mouse is still hovering over the taskbar and have the relevant 'mouse over' effect on one of the taskbar items.

The bug is when the hover ( j. edgar hoover ) semi bulb appeares even if the icon is not under mouse hovering that moment. It happened to me too ,but after a restart , it was ok . I did not see the problem on build 7260-xx64 - 7600 . it was on the post RC builds

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

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!