Do you use category view in the control panel?


Do you use category view in the control panel?  

99 members have voted

  1. 1. Do you use category view in the control panel?

    • Yes
      23
    • No
      44
    • No, how worthless!
      32
  2. 2. Start Screen and Category View

    • I like the Wndows 8 start screen and I also like category view
      18
    • I like the Windows 8 start screen but dislike category view
      24
    • I dislike both the WIndows 8 start screen and category view
      40
    • I dislike the WIndows 8 start screen but I like category view
      8


Recommended Posts

Dislike Category View on Control panel. It's one of the first things I change on non-Domain PC's along with showing file extensions.

I do like Start screen though. I like the WinKey + type name of something functionality.

In XP and Vista category view was an abomination, they finally got it right in Windows 7 IMO, and keep it that way now. To be honest though the only thing I do in the control panel any more is uninstall stuff, so it might just be apathy causing me not to use it. If I can't find a control panel activity I'll normally just use the search bar and it pops straight up, so the category view is basically a non-issue.

I am freaked out by any list that I have to read. I always open start menu, and keep typing until what i want is the first item, and Enter.

And thats precisely the reason I hate the start screen. I just want to see one item, but it smacks my eyes with a screenful of flashy and colorful crap.

I am freaked out by any list that I have to read. I always open start menu, and keep typing until what i want is the first item, and Enter.

And thats precisely the reason I hate the start screen. I just want to see one item, but it smacks my eyes with a screenful of flashy and colorful crap.

Classic view with small icons. I like to see everything. I like know where everything is and have gotten used to the location of everything over the years. I don't like having to hunt down items. :)

Nope, that's the first thing I change on a new installation of Windows. On my own machines as well as friends'. It's easier to provide support that way. :)

Negative... I don't like task-oriented navigation... I prefer "Icon view". As messy as it is, I find it easier to get to the setting I want to change that way. I think it's just how my mind is organized... When I think of changing something, my mind fits it into what overall category it goes into... If I was more task-oriented, and maybe not necessarily as used to navigating through the more advanced menus, or simply had no idea which setting grouping it was in, I might use the "category view" setting... But I'm not. :-p

I've always disliked category view because it was retarded, then got a job doing phone support, I flipping HATE IT, it's practically impossible to walk someone through it, so I always made them change it

Yeah, I barely ever navigate in the control panel at all and just use search (open Control Panel and ctrl-E in Vista, winkey in 7, win-W in 8) for everything. Neither of the views was/is very good.

Although it's kind of funny that the older, flatter icon view IMO actually matches their current ("Metro") design direction more than the hierarchical category view.

On every machine, category view is the first thing to go. I find it totally worthless. My feeling is "Please don't hide stuff from me, I want to see everything"

The thing is, is that if you know what you're looking for then why are you even clicking on the control panel? Using the search feature is faster than hunting through a list. However, if you are unsure of what something is called you have the option of taking a stab at searching for it or filtering out options using the category view.

  • Like 1

Don't like category view, never did. For me it always took longer to find things. And I also don't really like the start screen. Biggest thorn in my side with it is settings search. In Win 7 I can just type the name of the applet, like mouse, hit enter and I'm there. In 8 I have to type it, arrow down to get to settings and then click mouse, very cumbersome and annoying to do something that used to be so simple.

This is why I use Startisback on Windows 8 :p

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

    • 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
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • 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!