How do disable transparency in Windows 8's taskbar?


Recommended Posts

There is no transparency on Window borders or the Taskbar in Windows 8 RTM... If you're using a preview the option controlling opacity is where it was in Windows 7, Personalization/Window Color.

If you're actually wanting to ENABLE transparency on the Taskbar and Window borders in Windows 8 RTM: http://www.intowindows.com/enable-aero-glass-in-windows-8/

There is no transparency on Window borders or the Taskbar in Windows 8 RTM... If you're using a preview the option controlling opacity is where it was in Windows 7, Personalization/Window Color.

There is transparency in the Win8 Taskbar... [snipped]

Edited by Denis W
  • Like 2

Here's your solution for an opaque Taskbar.

Go to c:\windows\resources\themes\

Copy your .theme file someplace else

Under the key [VisualStyles] change the pointer to Aero.msstyles to point to AeroLite.msstyles

Double click your .theme file

Now your Taskbar is no longer translucent.

This also changes other aspects of the UI though.

Yea I don't understand why the taskbar was left transparent, I can't think of any reason you would want it to be, error or purposely left ?

It is explained in the extremely detailed Jensen Harris 'Creating the Windows 8 user experience' post, Building Windows 8 blog.

My theme is synced from the RP when transparency was OFF, and the transparency is still here in the taskbar with RTM [snipped]

[snipped]

Use AeroLite.msstyles, as my synced theme from RP did.

Go to c:\windows\resources\themes\

Copy your .theme file someplace else

Under the key [VisualStyles] change the pointer to Aero.msstyles to point to AeroLite.msstyles

Double click your .theme file

Now your Taskbar is no longer translucent.

screen_20120830b.jpg

Edited by Denis W

It is explained in the extremely detailed Jensen Harris 'Creating the Windows 8 user experience' post, Building Windows 8 blog.

You mean this extremely detailed explanation ?

"The taskbar continues to blend into the desktop wallpaper"

The full quote was this:

We applied the principles of ?clean and crisp? when updating window and taskbar chrome. Gone are the glass and reflections. We squared off the edges of windows and the taskbar. We removed all the glows and gradients found on buttons within the chrome. We made the appearance of windows crisper by removing unnecessary shadows and transparency. The default window chrome is white, creating an airy and premium look. The taskbar continues to blend into the desktop wallpaper, but appears less complicated overall.

Also they said that it was an extremely detailed post (which it is), not an extremely detailed explanation. :p

[snipped]

Use AeroLite.msstyles, as my synced theme from RP did.

Go to c:\windows\resources\themes\

Copy your .theme file someplace else

Under the key [VisualStyles] change the pointer to Aero.msstyles to point to AeroLite.msstyles

Double click your .theme file

Now your Taskbar is no longer translucent.

screen_20120830b.jpg

:o What have you done to windows 8 ?

Edited by Denis W

:o What have you done to windows 8 ?

The funny thing is, this has been my theme since install on Aug 6. I thought this was what everyone else was seeing too, as I knew the RTM UI was going to be different than RP. Ooops.

I have to say though, I like the translucent Taskbar and the window buttons more than the "Lite" theme. I'm going with it now.

If you go to personalize settings you can set the window colour and transparency.

If you mean 'just the taskbar', then i'm sorry i don;t know.

There is no option anywhere in Windows 8 to set transparency. Another feature removed from this awesomely great operating system!!

There is no transparency on Window borders or the Taskbar in Windows 8 RTM... If you're using a preview the option controlling opacity is where it was in Windows 7, Personalization/Window Color.

If you're actually wanting to ENABLE transparency on the Taskbar and Window borders in Windows 8 RTM: http://www.intowindo...s-in-windows-8/

There is a slight transparency in the taskbar in Windows 8 RTM. But there is no way to adjust it's transparency or remove it.

My theme is synced from the RP when transparency was OFF, and the transparency is still here in the taskbar with RTM [snipped]

I believe the reason my theme synced to AeroLite instead of Aero is that I didn't just have transparency turned off, but was using a "Basic" theme in RP.

When I heard that the RTM was going to disable Aero (which turned out not to be all that true) I turned off Aero in the RP to see what it would be like. I wasn't all that disappointed and just never switched back.

Edited by Denis W

Read my previous post with screenshot.

Word. That's pretty interesting. Of course, I was mainly talking about how there's no setting anywhere that let's you switch off the slight transparency in the Taskbar.

:o What have you done to windows 8 ?

He switched to Aero Lite theme in Windows 8. This theme is ugly, because it makes the scroll bars look ugly, the close/minimize/maximize buttons look ugly, and everything else look ugly. The ribbon itself is ugly. The Aero lite is for the server version of Windows. It can also be synced to RTM if you have been using Aero lite in the RP version. The method he showed is way to complicated than the simple steps you can follow to get back this ugly looking Aero lite theme. Bing it (or google it) to see how to enable Aero Lite in Windows 8 RTM.

But seriously, there is no reason you should be using this ugly theme. You are giving up good UI controls in return for an opaque taskbar. Switch to the RTM theme and see how beautiful it looks compared to this server theme.

Also, the taskbar is transparent for eye candy. It follows the digitally authencticaty by being flat and "modern looking". It's not glass, but, rather, it is trying to show the wallpaper while keeping the taskbar vivid. Window boarders work better without transparancy because transparency with overlapping windows look ugly. And the transparency on task bar was intentional according to the MSDN blog.

[snipped]

It wasn't as if I was trying to mislead anyone... It just turned out that I was both wrong and had serendipitously stumbled upon a working solution at the same time :huh:

Maybe a little conversation before making an accusation next time.

He switched to Aero Lite theme in Windows 8. This theme is ugly, because it makes the scroll bars look ugly, the close/minimize/maximize buttons look ugly, and everything else look ugly. The ribbon itself is ugly. The Aero lite is for the server version of Windows. It can also be synced to RTM if you have been using Aero lite in the RP version. The method he showed is way to complicated than the simple steps you can follow to get back this ugly looking Aero lite theme. Bing it (or google it) to see how to enable Aero Lite in Windows 8 RTM.

But seriously, there is no reason you should be using this ugly theme. You are giving up good UI controls in return for an opaque taskbar. Switch to the RTM theme and see how beautiful it looks compared to this server theme.

Also, the taskbar is transparent for eye candy. It follows the digitally authencticaty by being flat and "modern looking". It's not glass, but, rather, it is trying to show the wallpaper while keeping the taskbar vivid. Window boarders work better without transparancy because transparency with overlapping windows look ugly. And the transparency on task bar was intentional according to the MSDN blog.

Totally agree.

Edited by Denis W

It wasn't as if I was trying to mislead anyone... It just turned out that I was both wrong and had serendipitously stumbled upon a working solution at the same time :huh:

Telling someone "There is no transparency on Window borders or the Taskbar in Windows 8 RTM..." Is wrong, but someone who was reading, might think you were right, and then tell someone. Therefor "misleading others".

Telling someone "There is no transparency on Window borders or the Taskbar in Windows 8 RTM..." Is wrong, but someone who was reading, might think you were right, and then tell someone. Therefor "misleading others".

I didn't say that I wasn't wrong. I was wrong and of course that could be misleading.

You could simply say, "That's wrong", without an attack though. Not only was I not wrong because I "didn't know what I was talking about", the reason I was wrong was the solution.

It's just about common respect and manners, or as my grandfather used to say, decorum.

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!