Another design glitch in Windows 8?


Recommended Posts

Hmm. I wonder why it's not being seen more often then if it's purely a Metro IE problem. I'm not saying you're wrong, but one would think if it's a Windows or Metro IE specific issue we'd see more reports here. I think we've had only one repro so far in this thread.

the fact that it is indeed just one pixel might be why

it's one of those things that you most likely won't notice but if you notice it once you'll begin to lookout for it and notice it almost every time

  • Like 1

the fact that it is indeed just one pixel might be why

it's one of those things that you most likely won't notice but if you notice it once you'll begin to lookout for it and notice it almost every time

Definitely a possibility. I'll keep my eyes peeled to see if I ever spot it.

Definitely a possibility. I'll keep my eyes peeled to see if I ever spot it.

Yeah I'm curious too why others haven't seen it! I'm using the official RTM release.

Like I said, it doesn't *always* appear, so that could explain it. And yeah, it's tough to catch a small pixel like that... especially on 1920x1080 resolutions.

  • 4 weeks later...
  • 1 month later...

OP, I am experiencing this exact same problem on my brand new surface RT. At first I freaked out and thought it was a dead pixel, but soon realized the white pixel only appeared in ie, and only occasioinally at that. If you can figure out how to reproduce it consitently please share here and/or with Microsoft so that we can get this fixed.

Nope it's not a graphics card driver issue. Fully closing IE and opening it again made it disappear. It's definitely caused by IE, seems to be extremely random that's all.

1280 x 800. Could be an ad control but I don't think southparkstudios has many third-party advertisements.

Ok, you realize it still could be a graphic card driver, or your graphics card hitting a limit where artifacts are appearing?

The entire Windows 8 UI is 3D GPU accelerated, and IE10 pushes the GPU even more shoving through additional computing and rendering through your GPU.

(Saying that you restarted IE10 and it is still appears so you know it isn't a GPU driver would be analogous to someone telling a mechanic that their car isn't the problem because it doesn't make the thumping sound when it is parked.)

I've seen something similar to it, but never in the 'chrome' of a window. Generally it's been on the site itself and was a 1px item used for tracking purposes on websites. It was present in the actual site content area though...not in the chrome.

So it must be a fairly random bug of some sort....since I still have yet to see it on my machine and I've been looking.

  • 6 months later...

Sorry to bump an old thread, but I also am seeing this same pixel in the bottom left corner. I am currently using IE10 and it is only in IE10. Every other application does not have this white pixel shown, meaning it's not a dead pixel on my screen.

  • 6 months later...

I am pretty sure it is the Metro IE because sometimes it happens to me IN THE SAME PLACE or sometimes a little bit above the back arrow. When I run any other application such as a game that uses full screen and has a black background the glitch (stuck pixel) is not present.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      592
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!