Recommended Posts

So why does it slows down?

You keep claiming that the registry slows down without providing any evidence for it. I have no idea what answer you are looking for.

As I said, there are still programs that don't support it. One of this is also Visual Studio which doesn't support installing DLLs without administration rights.

What? Obviously you can't install shared system-wide components without administrator rights.

Obviously there are some, otherwise older programs wouldn't run.

I have no idea what this is supposed to mean. New and old programs mostly use the same APIs. There have been some minor additions and changes here and there, but not in a way that let's you remove anything without breaking modern software.

I don't know about anyone else but I never had any problems running applications when I used XP.The only time I ever had a problems was when I switched from XP to Vista.

I had all kinds of issues with XP back when it was still in beta. The early days of XP was ify as well. There were driver issues, stability issues... though neither was really Microsoft's fault. It was more issues with application developers believing they should have free reign of the system. It got significantly better even before SP2. With SP2 came a list of modifications to make XP more secure. A number of reasonable issues were addressed in XP sp3 as well.

As for Vista, I really never had any issues. It was rather resource intensive on light hardware, and there were minor issues (network copying), but again, it was mostly third party vendor issues with poor drivers and application design. I think it took a while for them to catch up. They have with Win7. Microsoft also did its part by improving the overall look and feel Vista with Win7. Less services, incremental start ups (elect).

You keep claiming that the registry slows down without providing any evidence for it. I have no idea what answer you are looking for.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

What? Obviously you can't install shared system-wide components without administrator rights.

Visual Studio is used for application developing, why would I need to install system-wide components? I need them to be installed in user space which is obviously not supported with Windows.

I had all kinds of issues with XP back when it was still in beta. The early days of XP was ify as well. There were driver issues, stability issues... though neither was really Microsoft's fault. It was more issues with application developers believing they should have free reign of the system. It got significantly better even before SP2. With SP2 came a list of modifications to make XP more secure. A number of reasonable issues were addressed in XP sp3 as well.

As for Vista, I really never had any issues. It was rather resource intensive on light hardware, and there were minor issues (network copying), but again, it was mostly third party vendor issues with poor drivers and application design. I think it took a while for them to catch up. They have with Win7. Microsoft also did its part by improving the overall look and feel Vista with Win7. Less services, incremental start ups (elect).

it was beta what do you expect?When i switched from 98 to XP it was flawless for me.And i was running a P2 2.33mghz processor :p it was slow but did the job.

So? I'm sure some people preferred the look of system 7 on the early Macintoshes, does this mean that apple should have made it so people can switch MACOSX Snow Leopard to look like System 7?

The difference is that OS X and System 7 are completely different operating systems. Windows is the same from the first release of NT (and further back) to today. They simply added the themeing service in XP, and added the DWM in Vista. These are all layers sitting on top of each other. To get Classic, you simply remove two of the layers. It's the ultimate fallback, not just another theme. If they were to redesign Windows today with no focus on compatibility, this would all go, but that's asking for a lot more than just "replacing the Classic appearance with Basic." It would be a major breaking architectural change.

There's a time where certain outdated and ugly things must be laid to rest, to remove unnecessary outdated foundation to allow a more efficient (and better looking) foundation to take its place.

I think you're getting a little carried away here. What you are talking about is making changes that are purely visual and have no other impact on the OS at all.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

It's not my job to tell you what you are talking about, you should know that yourself. You want to claim the registry slows down, you have to provide evidence of this.

Visual Studio is used for application developing, why would I need to install system-wide components? I need them to be installed in user space which is obviously not supported with Windows.

It could have been designed to install all shared components locally, and disable the various functionality that requires administrative rights, but what's the point. It accomplishes nothing of value.

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

You mean those very same people who go and download registry cleaners that do nothing? Yup I really trust their evidence.

As I said, there are still programs that don't support it.

I would assume that this has to do with shoddy code. Before Vista every application developer thought they could code their applications with admin rights, since pretty much 99% of XP accounts were admins. When Vista came about and started making prompts, most applications started acting funny.

So? I'm sure some people preferred the look of system 7 on the early Macintoshes, does this mean that apple should have made it so people can switch MACOSX Snow Leopard to look like System 7? There's a time where certain outdated and ugly things must be laid to rest, to remove unnecessary outdated foundation to allow a more efficient (and better looking) foundation to take its place.

Apple has an easy way with Mac. It's usershare isn't anywhere near as big as Windows. Sure MS can re-design windows to make it look different but think about the problems that would cause. You had the media and even people on this forum (and others) up in arms about vista because a few shortcuts were moved around.

If they finally got rid of the classic theme, it means they rewrote the foundation and a much better look, without requiring a service, has taken its place. Imagine that, a nice looking theme that does not require a service to run!

And replace the service with what exactly?

The difference is that OS X and System 7 are completely different operating systems. Windows is the same from the first release of NT (and further back) to today. They simply added the themeing service in XP, and added the DWM in Vista. These are all layers sitting on top of each other. To get Classic, you simply remove two of the layers. It's the ultimate fallback, not just another theme. If they were to redesign Windows today with no focus on compatibility, this would all go, but that's asking for a lot more than just "replacing the Classic appearance with Basic." It would be a major breaking architectural change.

I think you're getting a little carried away here. What you are talking about is making changes that are purely visual and have no other impact on the OS at all.

Yes and no. Aqua is a theme (like Luna and the default Win7 theme). It runs atop the Quartz Compositor (like the Desktop Windows Manager), which is the windowing system for OS X. I believe you could simply remove the ability for the end user to select the Classic UI theme. It would still be there, but unavailable. The issue, however, would become more complex if there were driver issues.

Yes and no. Aqua is a theme (like Luna and the default Win7 theme). It runs atop the Quartz Compositor (like the Desktop Windows Manager), which is the windowing system for OS X. I believe you could simply remove the ability for the end user to select the Classic UI theme. It would still be there, but unavailable. The issue, however, would become more complex if there were driver issues.

Yeah, why don't they just make it so only safe mode and servers can use this theme? Have the ability to use it disabled in normal Windows client. Then they can totally break how things look in it further without a big worry.

That way I won't have to see that ugliness used in a modern OS nearly as much in people's screenshots/videos.

Yeah, why don't they just make it so only safe mode and servers can use this theme? Have the ability to use it disabled in normal Windows client. Then they can totally break how things look in it further without a big worry.

That way I won't have to see that ugliness used in a modern OS nearly as much in people's screenshots/videos.

I don't know what screenshots / videos you're looking at but I haven't seen any that show Windows 7 classic theme. And why disable it?

If people want to use it, it's THEIR choice. Not yours. And its not like someone won't use a UXTHEME patch and put it right back anyways.

I don't know what screenshots / videos you're looking at but I haven't seen any that show Windows 7 classic theme. And why disable it?

If people want to use it, it's THEIR choice. Not yours. And its not like someone won't use a UXTHEME patch and put it right back anyways.

I've seen it on various IRC locales, on Youtube, and even on the desktop threads here on Neowin occassionally. Windows 7 and classic theme do not mix, and honestly 15 years is a very long time in the world of technology, to keep the SAME EXACT LOOK around for so long.

I've seen it on various IRC locales, on Youtube, and even on the desktop threads here on Neowin occassionally. Windows 7 and classic theme do not mix, and honestly 15 years is a very long time in the world of technology, to keep the SAME EXACT LOOK around for so long.

Yet again, why the hell do you care if someone else likes that theme and wants to use it? Did you make Windows? Did you pay for their computer and their software?

Yeh they could completely re-write it and design an entire new classic theme. But why? It wouldn't be able to use many "special effects," if any, since that is all done by DWM, it may cause compatibility issues etc. You have a perfectly good working shell working on top of it, so might as well leave something as trivial as a classic look that less than 1% of the world uses and focus on other more important things.

---

Here's an example. I hate the font you use, but I'm not telling you which one to use since its your account and I don't own Neowin.

I agree with others, who cares if the classic theme is still in there.Its not mandatory that you have to use it,it doesn't ship with the classic theme being the first thing you see when you turn on your new machine.The more options the better.Maybe i'll want to use it just for old times sake,I've tried it out in 7 and it doesn't look quite like the actual classic theme but its close enough.I don't like the classic theme myself and I wouldn't use it unless I had to but I don't want it gone just because I don't use it. The more options the better.

But Microsoft will need to do it in the future. What is the point of keep up with the NTFS since 1993 and updated framework. Where is the research work that they have been doing with

?

Why would they need to start from scratch in the future. They could rewrite certain parts of the OS (And I would expect them to do this), but I see no *Need* to start from scratch...

Well, if it was gone, then colleges and workplaces could no longer FORCE their users to use classic theme against their will like they have been with XP... and I sure don't wanna be stuck on a machine for the majority of the day forced to the classic look because the admin was a total jerk who wants to make everyone deal with his plain ideology. No classic theme in Windows = no more forcing users to have to use it.. which means I won't have to deal with it if I end up in a place like that!

People say that the registry causes system to slow down. So if you say that registry is not the cause, then what is?

These same people are usually trying to sell you, or have been lured by a company trying to sell you, a registry optimization product.

Which is completely useless and can actually wreck your registry on some occasions.

The registry is NOT slow. It's only weakness is that it's centralized. But that's also its strength.

Well, if it was gone, then colleges and workplaces could no longer FORCE their users to use classic theme against their will like they have been with XP... and I sure don't wanna be stuck on a machine for the majority of the day forced to the classic look because the admin was a total jerk who wants to make everyone deal with his plain ideology. No classic theme in Windows = no more forcing users to have to use it.. which means I won't have to deal with it if I end up in a place like that!

Are you aware of a situation where this is actually occuring with Windows 7? I ask because I've never heard of this, nor can I imagine an IT person doing this when the standard UI is much easier for them to just set up...

But Microsoft will need to do it in the future.

I agree that such a thing would be exciting, but i cannot genuinely think when it would become feasible or at least economically viable for Microsoft. That said, it isn't difficult to envisage a scenario where they will need to develop an Operating System that is designed to harness the power of the Internet as opposed to the colossal amount if ram your Computer has.

Are you aware of a situation where this is actually occuring with Windows 7? I ask because I've never heard of this, nor can I imagine an IT person doing this when the standard UI is much easier for them to just set up...

In my experience, when dealing with NT, 2000 & XP workstations it became necessary in some situations to force the Classic theme for certain Groups of users alone with the Classic Start Menu to avoid compatibility issues. The gap has only become more apparent between older Operating Systems and Windows 7 as time progresses.

If windows 7 is such a huge hit and takes the place of everyones xp machine, then windows 8 could be marketed as a power user OS.

Well, Windows 7 is being labeled as a "Minor" release. Windows 8 will be "Major", as Microsoft has stated they plan on alternating Major / Minor releases... I would love to know what's planned for Windows 8... *drools*

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

    • No registered users viewing this page.
  • 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
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!