Have Back Classic Start Menu In Windows 7 With This Tool!


Recommended Posts

Jeez can't people just let the classic start menu die already?

I don't even like the classic start menu but I thought I would post this because I always see so many people here saying how they would love to be able to use the classic start menu in Windows 7 :)

I don't even like the classic start menu but I thought I would post this because I always see so many people here saying how they would love to be able to use the classic start menu in Windows 7 :)

Yeah, I wasn't taking a shot at you with my post, it was just a general statement.

Attached File(s)

Attached File screen.bmp ( 800.65K ) Number of downloads: 19

Attached File classic_start_menu_for_windows_7_1.bmp ( 256.77K ) Number of downloads: 11

And since when have screenshots in BMP format been a good idea? Oh that's right, NEVER! I'll give this a miss thanks.

Oh and if you want to use a system that looks and feels like 2000/XP, then use 2000/XP. Simples.

Strange... the fan boys are all declaring anyone who wants to continue using the classic menu is a fool and yet so many of us would still like it there. Its almost as if we don't care what the fan boys think and just want something that works for us. :blink:

It's 2009. If you still want the classic Start menu, then stick with XP or Vista.

Also, looking at the site:

The innovative, high-tech version of Windows Start menu introduced in Windows 7 is not necessarily welcome by experienced users of previous Windows editions. The lack of choice resulting from Microsoft's removal of classic Start menu from Windows 7 leaves many computer users frustrated. Seven Classic Start enables the familiar look and feel of the classic Start menu found in Windows XP and Vista for users of Windows 7.

You're obviously not very "experienced" if you aren't capable of doing things in a new (and even better) way. I don't know why people even bother with newer OS if all they want to do is use their old computing habits from 15-20 years ago.

I think the new start menu isn't so bad. But I also want to have back the good old classic menu.

But you can emulate the classic start menu in Windows 7.

So you have the features of the new menu AND the classic start menu side by side.

  • Features of the new menu:
  • recent opened programs
  • pinned programs
  • jumplists
  • special links (right area of start menu)
  • search bar
    Bad in new menu:
  • All programs: louvre opened menu
  • Reduced space for "All programs" menu by start menu, often scrolling is needed
  • Search bar without "history"

--------------------------------------------------------------------------------

  • Features of classic menu:
  • Laterally opened menu without mouse click
  • Menus uses full screen height
    Bad in classic menu:
  • No recent opened programs
  • No jumplist
  • No search bar

You're obviously not very "experienced" if you aren't capable of doing things in a new (and even better) way. I don't know why people even bother with newer OS if all they want to do is use their old computing habits from 15-20 years ago.

What defines a "better way"?

If I can accomplish tasks via the command line much faster than you can do them via a GUI (and often things you CAN'T do without having a specialized tool for it), does that mean your "new" way is improved and better just because it's "easier" or "flashier"?

If people are content using the classic start menu, why deprive them something that has worked for them for so long? Just implement it alongside the new way of doing things and you'll please both sides of the fence.

Yeah, stupid people. Having their own opinions, what's wrong with them. They should like what they're told to like.

You are allowed to have your own opinion, so long as the resident fanboi's agree with it...otherwise you become a fair target....

People can have whatever they like you freakin start menu Nazi's lol.

Right on brother...fight the power...

Strange... the fan boys are all declaring anyone who wants to continue using the classic menu is a fool and yet so many of us would still like it there. Its almost as if we don't care what the fan boys think and just want something that works for us. :blink:

OMG, the noive....

I run Windows in Classic Mode, and have since WinXP, why, because it frees up RAM that can better be used elsewhere, and the OS tends to be a lot faster because it doesn't have to render all the desktop bells & whistles. So, yes if there is a way to also run the Start Menu in Win7 in Classic Mode as well, then yes, I'll definately be looking into that as I don't like how they force you to use the new menu.

i know some friends that might be interested in this, dont understand why though. They are always complaining that windows needs to act more like OSX so I showed them Windows 7. The first thing they asked though is about the classic start menu?

Just curious though, would there be any way to used XP mode to add in the xp classic start menu?

I run Windows in Classic Mode, and have since WinXP, why, because it frees up RAM that can better be used elsewhere, and the OS tends to be a lot faster because it doesn't have to render all the desktop bells & whistles. So, yes if there is a way to also run the Start Menu in Win7 in Classic Mode as well, then yes, I'll definately be looking into that as I don't like how they force you to use the new menu.

Actually, wrong. Aero mode in Windows Vista and Windows 7, especially when running with a DX10 card and WDDM1.1 drivers is fully GPU accellerated and utilises VRAM instead of system ram, and equally, GPU for GUI rendering. It will be a lot faster rendering the bells and whistles than not. You're using MORE ram in classic mode.

Actually, wrong. Aero mode in Windows Vista and Windows 7, especially when running with a DX10 card and WDDM1.1 drivers is fully GPU accellerated and utilises VRAM instead of system ram, and equally, GPU for GUI rendering. It will be a lot faster rendering the bells and whistles than not. You're using MORE ram in classic mode.

With Aero running:

2j62rh5.png

Without Aero running:

rri5qg.png

Do you want to revised your statement?

Not particuarly. Do you want to go and research Windows Memory Management?

So you're saying there is NO System Memory overheard running Aero, and the load is purely absorbed by the VRAM on the video card?!

I think you might be wrong mate!

Random article from Google here.. many more like it:

http://exo-blog.blogspot.com/2007/03/vista...at-cpu-hog.html

I love how people QQ about windows memory use when like every off the shelf unit has 3gb or more ram now. RAM is so cheap its silly to QQ over memory use. If you're using classic mode you may as well stick with windows 2000 or 9x, ohh and turn superfetch off as well because it uses too much memory to practically let your most frequently used apps load almost instantly. Seriously just buy more ram and use the OS as it was intended or dont waste your time upgrading.

I love how people QQ about windows memory use when like every off the shelf unit has 3gb or more ram now. RAM is so cheap its silly to QQ over memory use. If you're using classic mode you may as well stick with windows 2000 or 9x, ohh and turn superfetch off as well because it uses too much memory to practically let your most frequently used apps load almost instantly. Seriously just buy more ram and use the OS as it was intended or dont waste your time upgrading.

I've got 6GB of RAM, DDR3 RAM is still not cheaper, of course I plan on getting another 6GB for a total of 12GB or 18GB for a total of 24GB, yes Aero may run fast, but not running Aero Windows does tend to run faster.

This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • 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.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR 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!