Recommended Posts

After using the Universal Theme Patcher on my new laptop (running Windows 7 Ultimate 64-bit SP1) it seems that 3rd party visual styles/themes are not being applied to all applications, or in some cases only partially applied. I'm using the Gaia09 visual style, but this happens with any visual style I use, including the standard Aero style.

I've attached an image to show what I mean. On the left is Google Chrome with the Open dialog box opened. Except for the back/forward buttons in the location bar, it appears that the VS is being applied completely. On the right is Notepad++. The window frames around the main application and the Open dialog are using the VS, but the interior elements are not - they look like they're using the Classic theme. System-wide, this seems to be the case with many applications: they're either completely styled, or only their window borders and min/max/close buttons are being styled.

I've tried using the Universal Theme Patcher to patch both 64-bit and 32-bit system files. I've also tried the UxStyle Core service, and even TuneUp Utilities' built-in 3rd party theme support. After multiple patching and restoring attempts, I ran SFC /scannow to replace any affected system files, rebooted, repatched, etc. still without any luck.

I'd appreciate any help!

post-186066-0-45941200-1352466160.jpg

you call that the classic elements problem ^^

the dialog on the right side is coded to use the windows 2000 style instead of the aero style, this is a decision by the coder of the application.

Edit: seems it doesn't use windows 2000 style on my notepad++, you sure that you have the latest version of notepad++?

Thanks for responding! I do have the latest version of Notepad++. The problem that I showed in the screenshot doesn't just apply to NP++, but it was just the easiest example I could give. I've attached another screenshot that shows a side-by-side comparison of my new system and old system. Almost every application on my new system uses the Windows 2000 style for open & save dialog boxes. Both systems have the same patched themeservice.dll, themeui.dll, uxtheme.dll and explorer.exe files in the right locations - I copied the ones from the old system over to me new one in an attempt to fix this.

I've also run sfc /scannow to replace any *corrupted* Windows files. After replacing the patched ones with the originals, even if I just use the built in Windows 7 Aero theme, many applications STILL use the Win 2000 style. This is driving me nuts!

post-186066-0-96080000-1352990173.jpg

This topic is now closed to further replies.
  • Posts

    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!