Were these Windows 7 bugs fixed in Windows 8?


Recommended Posts

Not a "BUG" I I would say is a feature--

The Shadow of the mouse is what you are seeing and if you turn that off in the effects the "BUG" will disappear.

If you notice there is a highlight under your mouse before you "mouse over" the close "X" which follows you to the Close "X"

The same effect can also be seen if you mouse over the start menu orb where it highlights itself to show it can be selected.

In earlier Windows such as XP that effect was called mouse spotlight.

It is not selecting and deselecting anything but showing you it is a click-able item.

If its a feature then my does the Red X not blink in any other windows?

Those bug don't exists in 7, your Windows installation is probably messed up (sounds like bad gpu drivers to me).

The flickering Close button is an issue that everyone has, just open the properties of any hardware you have installed and hold the mouse over the close button. It only occurs when it's in focus and TBH how many times are you holding the mouse cursor over the close button.

I reported Bug 1 during the Windows Vista beta back in 2006 on MS Connect. Closed as [Won't Fix].

Then reported Bug 1 during the Windows 7 beta. Closed as [Won't Fix].

Bug 1 definitely happens on all computers, but it's such a minor issue you probably won't ever find it. It certainly doesn't affect the functionality.

In the Windows 8 Developer Preview, the issue still exists - it still has different behavior from all other windows, but it doesn't blink anymore. As I recall, it will only blink once. So you won't notice it in Windows 8 unless you're really looking for it.

They'll probably end up fixing bug 1 as they're tweaking and changing the UI itself so they've probably all seen it in the process of making and testing things. We'll just wait for beta to come and see if it's fixed but since it doesn't happen on all windows it really is minor.

Those two bugs have been around for a long time. Also, UI tearing is more noticable on applications that do its own DWM calls (e.g. DwmExtendFrameIntoClientArea) such as Chrome and Firefox.

Button flickering (colors are a bit off):

http://i.imgur.com/XaFku.gif

UI tearing:

http://i.imgur.com/qS22s.png (normal window; barely noticable)

http://i.imgur.com/A1Fwy.png (Explorer)

http://i.imgur.com/ovGzp.png (Chrome)

http://i.imgur.com/3Ly1H.png (Firefox)

1st one I can't even reproduce in windows 7...

2nd one I've been complaining about since windows vista's beta where DWM was announced... it's always been marked as "by design" by microsoft...... every beta build I'd resubmit it and get it as "by design" all the way from longhorn up to 7's rtm....

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

watch really carefully and the X button kind of gets selected and unselected once every few seconds.

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

There is nothing wrong with the registry. Stop disabling stuff like UAC and you won't have any issues with the registry, ever.

There is a much larger bug called the Registry, that's the bug that really needs fixed. Tried running Windows 95 on a new machine under XP? It's crazy fast. MS is and has been going the wrong direction for quite a while now. The extended library situation back in the day, would be a crazy amount faster now because of multiple CPU's, GPU's, and the size of memory. What's in memory now? MS bloat in the name of security. The Windows registry should have been separated, and fully protected from 3rd party programs years ago.

for the 10 millionth time the registery is not a problem, whats the alternative? config files? the registry is a transactional database, it can support concurrent usage, changes, and is better with corruption and can self recover from it.... all things a text config file can not do

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

these problems only happen when DWM is running in "aero" mode

You mean here

post-14624-0-24466400-1325866853.jpg

I left it there a good 30 seconds never saw it flicker, then again why in the world would you hover your mouse there for more than a fraction of second in the first place?

I have never seen this, nor if I did would I more than likely give it a second thought.. Seem pretty nit picky to me ;)

Not showing hover or not working when you click it would be an issue - it flickers "sometimes" if you hover your mouse there long enough -- not so much ;) How do you know its just not a mouse issue, or detection of mouse location problem -- maybe the mouse is right at the border of selection and is moving from on and off the threshold?

I'm not saying that I think it's a huge problem (in fact, I use Device Manager daily and have never noticed this), but I was merely admitting it's existence :) And I know it's not a mouse issue or detection of location problem because (1) my cursor stays in the same place (2) this doesn't happen with any other windows. Try turning on Aero and try it, i think it might only happen in Aero.

  • 3 weeks later...
for the 10 millionth time the registery is not a problem, whats the alternative? config files? the registry is a transactional database, it can support concurrent usage, changes, and is better with corruption and can self recover from it.... all things a text config file can not do.

Bro, no use explaining the facts to some people. There is nothing wrong with the registry, as you've stated, with the only thing wrong have been third parties abusing the registry (using it as the dumping ground for random sh-t that doesn't need to be in the registry) and Microsoft themselves admitting that they failed to give clear guidelines on how the registry should be used and what shouldn't be put in there.

What I would like to see is for third parties to have better uninstallers and file tracking functionality so that when you uninstall their software it completely removes all the files and registry changes made - that is one thing I'd like to see Microsoft really emphasise when it comes to Windows 8 application certification. To attack the registry as justmike does is simply attacking a symptom rather than the real source of the problem.

In reference to Zimmedon's post - they're just a side affect of GDI's crappiness which can only be fixed by Microsoft moving their Common Control/Dialogue infrastructure from GDI to Direct2D/DirectWrite; don't hold your breath for that to happen given that Microsoft is focused on Metro at the moment.

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

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!