Ways to enable the XP standard "Start menu" (not Classic)


Recommended Posts

In a domain? I dont think you can have it in a domain env. You can use the themes if not locked by group policy but when you add a system to a domain it forces the classic/visualstyled classic menu.

Assumed it was a domain due to it being in Windows NT4/2000/XP Client section, ignore if not in a domain.

It absolutely does NOT.

I wasnt sure hence saying "think" but hey ho whatever floats your boat mate. Nice helpful post btw you must be so proud, the original poster is also grateful for your valuable contribution to his question.

I stand corrected by joel......but unlike him Ill provide you with something thats of value to what you asked (and loosely relevant).

You need to go to User Config > Admin Templates > Start Menu and Taskbar

There is a policy here called "Force Classic Start Menu" It should be Not Configured or set to Disabled so you can use the new XP Start Menu.

Of course this is only "loosely" relevant to the question if it is in a domain profile you are seeing this with (and of course if there is no GPOs set on the server for domain clients configuration or physical appearance).

(perhaps I should have added 4 words and added to my post count....oh wait no im too grown up to give a chuff)

Edited by Mando
I wasnt sure hence saying "think" but hey ho whatever floats your boat mate. Nice helpful post btw you must be so proud, the original poster is also grateful for your valuable contribution to his question.

I stand corrected by joel......but unlike him Ill provide you with something thats of value to what you asked (and loosely relevant).

You need to go to User Config > Admin Templates > Start Menu and Taskbar

There is a policy here called "Force Classic Start Menu" It should be Not Configured or set to Disabled so you can use the new XP Start Menu.

Of course this is only "loosely" relevant to the question if it is in a domain profile you are seeing this with (and of course if there is no GPOs set on the server for domain clients configuration or physical appearance).

(perhaps I should have added 4 words and added to my post count....oh wait no im too grown up to give a chuff)

You said 'think' to the themes, not the XP start menu. Maybe you meant to say otherwise, but your grammar didn't follow your thought.

You're assuming he's in a domain, but those settings could be made on a local policy also. And he said 'enable', not 'that setting I can get to by right-clicking doesn't work, how can I be blocked?'. There is a difference. We have very little information to go on, but you're upset that I corrected your post.

My correction was entirely relevant to the extreme misinformation you posted. I didn't just spout off about something unrelated, like you're trying to make it sound. Since you don't 'give a chuff', I'm sure we won't hear from you again on this matter.

Im not upset, its a forum post for goodness sake, but perhaps a bit of civility in your first reply would have been a thought (especially with you having a respected and worthwhile position in the forums, leading by example) or requesting more information which in hindsight perhaps I should have done myself.

I assumed he was in a domain because its posted in the XP client section and if it was categorised incorrectly it would have been moved no? Id think that was a fairly reasonable and fair assumption to make is it not?

Anyways to O.P Could you clarify what you are trying to do and whether its in a domain env or a local workgroup/stand alone capacity please.

Im not upset, its a forum post for goodness sake, but perhaps a bit of civility in your first reply would have been a thought.

Explain to me how it was uncivil. I didn't call you a name, and I didn't question your intelligence. I just refuted what you said.

Explain to me how it was uncivil. I didn't call you a name, and I didn't question your intelligence. I just refuted what you said.

....and thats ALL you did. You didn't provide any info to correct or clarify why he was wrong. When he argued back, THEN you provided some comments that explained why he was wrong. I think his point is you should of probably provided some details in your 1st post, instead of saying NOPE YOUR'RE WRONG and leaving it at that.

Not trying to have a stab at you Joel, you post many useful posts and responses, but yeah you were a bit short/ blunt in your initial response.

....and thats ALL you did. You didn't provide any info to correct or clarify why he was wrong.

WHY he was wrong? How about, because it's irrefutably wrong? There's no question of an explanation, it's just not correct. The correct answer therefore is the opposite of what he said, basically that Classic mode is NOT forced. Does this really need to be explained?

XP is built on BSD and it's interface was developed by a llama in a basement in Bangladesh. Every month, Microsoft secretly scans your entire PC and downloads any file with certain keywords to a central server in China, and using a new form of compression, fits it all on a 1TB drive, from every computer worldwide. I'm right.

Are you now going to post a long explanation of where I went wrong, or can you point me to a search engine by simply saying, "That's not correct."?

Are you all women here? You hear tones of voice in posts now? :blink:

Are you all women here? You hear tones of voice in posts now? blink.gif

nice sexist remark mate well done. Good to see you hold ladies in such high regard and a sweeping generalisation to the fairer sex). Says it all quite nicely imo. Maybe try the racist card next and we got a full house! (Im not even gonna go near you questioning our sexuality or our gender)

It absolutely does NOT.

^ Didnt realise there was an encoded message that says google search and you will see you are incorrect. How ignorant and stupid of me.

lets just drop it all now please and get back to the original posters request, this will just keep going on and on and on and on and on.............

Oh and it was an Alpaca btw not a LLama (they wouldnt be seen dead touching a windows UI) :o )

Peace out!

6 Years on Neowin and never a tiff (and 0% warn rating which im proud of), I dont want to start now

Edited by Joel
fixed quote tag
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You literally have to do it on a desktop, which is incredibly annoying in our mobile-first world. What???
    • What part of "you can’t really depend on service providers to maintain features forever" is not clear enough?
    • Nope. That lack of surround sound capability (analog) won't fly with me. Sure, I use headphones most of the time, but still.
    • Creative Sound Blaster AE-X PCIe review: your headphones will love it by Steven Parker If you have been reading Neowin for any length of time, you may remember that I reviewed the Sound Blaster Audigy FX Pro back in April. I found it to be an excellent budget sound card, even though it lacked support for formats such as DTS over the included SPDIF port. Anyway, Creative reached out to me again asking if I was interested in reviewing the Sound Blaster AE-X. It is a card mainly targeted at headphone wearers, which I'll get into a bit later. Before we get underway, here is a disclaimer: Creative Labs provided a free sample without any review pre-approval. Here are the full specs of it: Creative Sound Blaster AE-X Dimensions: 179 x 126 x 18 mm Weight: 263g / 9.28 oz Platform: PCI-e DAC: ESS ES9039Q2M Connectivity Options Side: Rear: 1 x HD Audio Front Panel Connector, 1 x ⅛“ Headphone port, 1 x RCA Line-out (Left) port, 1 x RCA Line-out (Right) port, 1 x Coaxial SPDIF-out port, 1 x ⅛“ Mic in/Line-in port, 1 x TOSLINK SPDIF-in port Surround: No DNR / SNR: THD+N: 0.0001% Dynamic Range 130 dB Recording Resolution: PCM up to 32-bit / 192kHz (Stereo) Direct Mode: Line Out (Stereo): PCM up to 32-bit  384 kHz Coaxial SPDIF Out: PCM up to 24-bit 192.0 kHz Headphone Amp: PCM up to 32-bit / 384kHz (Stereo) Native DSD: DSD64, DSD128, DSD256 Output Impedance: 1Ω, Supported Headphone Impedance: 8–600Ω, IEM: 0.5Vrms, Low: 1.5Vrms, Mid: 3Vrms, High: 6Vrms, Maximum output power: 350mW @ 32Ω (High), Maximum output voltage: 6Vrms (High) Front Panel Headphone Amp: PCM up to 32-bit / 192kHz (Stereo) Native DSD: DSD64, DSD128 Output Impedance: 10Ω, Supported Headphone Impedance: 32–300Ω, Maximum output power: 40mW @ 32Ω, Maximum output voltage: 1.9Vrms ASIO: ASIO 2.3 Total Harmonic Distortion: THD+N: 0.0006% Dynamic Range: 114 dB Scout Mode: Yes EMI shielding: No (but it passed all the FCC emission tests) Operating temperature: 0–45°C Input Power: 12V⎓0.5A Warranty: 1 Year (MSRP) Price: $179.99 / £169.99 The Sound Blaster AE-X was announced at the end of May, and it becomes clear that it is mainly for headphone wearers. I should also note that the card does not support DDL/DTS encoding technology, but it is said to support decoding through the coaxial SPDIF port. I was able to test this working with the classic Windows Sound properties, but I could not get a DTS (decode) signal through my Logitech Z906, it defaulted to 3D sound whenever I played DTS content through Plex or Emby. In addition, this card only supports two channels (stereo) over the speakers. The surround support is limited to the Headphone Amp, so before I get underway, what we have here is a card mostly intended for headphone use, especially with its SPDIF In (Toslink) port where you could connect another device like a console. So what about the highlights of this card? The AE-X is powered by the ESS SABRE DAC (ES9039Q2M), which is capable of a 130 dB dynamic range. In addition, it supports 32-bit/384 kHz playback for deeper detail and clarity. The headphone amplifier delivers up to 350 mW @ 32Ω, which admittedly far surpasses standard onboard audio, offering support for studio-grade headphones. DSD256 and ASIO 2.3 are also supported. What doesn't it have? No support for What-U-Hear, Super X-Fi, or the SmartComms Kit No EMI shielding, but it passed all the FCC emission tests (from the FAQ) I also want to make it clear that I am no audiophile. For me, it's purely subjective and it should just "work" out of the box. First impressions As I said in the introduction, I was a bit sad to see that the AE-X only supports stereo output, meaning it would not be on par with my ALC1220 over my speakers, as I mentioned it seems like this card is marketed toward headphone users. Since I am not an avid gamer that would rule me out as a potential customer, but I can still test its capabilities! The card arrived in a nice-looking box, as shown above. It's quite a bit larger than the Audify FX Pro that I reviewed back in April, and at first I thought the covering meant that it was EMI shielded, but it isn't as mentioned above in the highlights section. What's in the box: 1 x Sound Blaster AE-X PCIe card 1 x 3.5 mm CTIA TRRS to Dual TRS Headset Splitter Cable 1 x Quick Start Guide Aside from the Quick Start Guide, which someone at my age (I guess) needs a magnifying glass to read thanks to the tiny fonts, Creative Labs also has the manual online, which first requires you to prove that you're human in order to access it (so I can't direct link it). Anyway, the box is mostly made up of cardboard, and the only plastic in it is the anti-static bag for the card itself. Design Top Bottom The card itself looks pretty cool and actually wouldn't look out of place in an all-white build. There's only one connector, and for some reason it is awkwardly placed on the side (front-facing) that is for the front panel audio connector, which will let you use the headphones through the front PC audio jack. Since the front panel Headphone Amp has fewer capabilities than the rear headphone port, I decided not to use it. Rear of card PCI-e interface The rear of the card is completely open and is normally where you would find the front panel connector. The PCIe interface side is completely covered, which initially made me think it was EMI shielded. I/O panel Side (front-facing) with Front panel connector On the outer rear bracket side we have the TOSLINK SPDIF in, Coaxial SPDIF out, RCA line out (Right), RCA line out (Left), Headphone out, and Mic/Line in ports. On the front facing portion of the card itself is the F-panel connector. Usage Test System Our test system consists of the following: AMD Ryzen 9 9950X3D Gigabyte X870E AORUS MASTER (BIOS F12) Corsair RM1000x (2024) Thermal Grizzly Kyronaut (33x33x0,2mm) 2x 32GB Kingston Fury Beast RGB DDR5 6000MT/s CL36-38-38-80 T-Force Z540 2TB (PCIe Gen5) NVIDIA GeForce RTX 5090 Founders Edition (NVIDIA) Creative Sound Blaster AE-X Windows 11 25H2 Pro I installed the card into the Gigabyte X870E AORUS MASTER which includes the RealTek ALC1220 onboard audio. For our subjective listening tests, I used the Coaxial SPDIF port to my Logitech Z906 speakers. For headphone tests I used the OneOdio Studio Max 2 Wireless DJ Headphones that I reviewed last month. After installing the audio driver, I installed Creative Nexus, which is a relatively new app designed for the latest Sound Blaster cards. Then I discovered the AE-X needed both a driver update from 1.00.15.0001 to 1.01.09.000 and a firmware update from 1.00.06.0000 to 1.00.06.0002, then I was set to go. It should be noted that the card did not work without the driver (not Plug and Play). As you can see above, you can manage the firmware, driver, and inputs via Advanced Settings on the Device tab. By default Nexus enabled "Direct Mode". Upon clicking on Acoustic Engine, the Equalizer can be enabled and set to four different presets, which are: Gaming Music Movies Footsteps Enhancer There's also a dedicated Scout Mode for gamers. I mainly used Tidal and Spotify in the past week to listen to some of my Liked Songs (which now total over 700) in Shuffle mode; there were no pops or interference that I could hear. I also found a 5.1 Surround Music playlist on Tidal that sounded really great over Studio Max 2 headphones. When I reviewed the Audigy FX Pro, I went out and purchased a Logitech Z906 set second-hand for €100 specifically to use with the card, but in this instance all I could get on the AE-X was the 3D output of surround sound through Coaxial SPDIF and although it still sounded great, it isn't quite as good as DTS Interactive via my onboard Realtek ALC1220. Conclusion So what have I learned? The AE-X lacks multi-channel support for 5.1/7.1 setups and drops support for modern surround technologies like Dolby or DTS, functioning strictly as a stereo output device. So to really benefit, you will need Studio-grade headphones to "hear" the benefits of this card. With that being said, I can imagine it will appeal to gamers who are switching between console and PC. By utilizing the SPDIF in port, you could just plug your headphones into the AE-X (front or rear port) and then switch between PC and Console without having to move the headphones to a different port. As I said in the Sound Blaster Audigy review, the EQ in the Creative Nexus app offers safe presets, which allows a user to further tweak the lows, mids, and highs for a personal listening experience. Of course it all depends on the headphones you hook up to it. Speaking of headphones, I kind of wish I had higher-quality Studio-grade headphones to really test this card with; I'm not usually wearing headphones in my day to day duties. The only time I will wear them is if I want to listen to music very late at night and I don't want to disturb my neighbors, so my rating (verdict) is based on this fact. Someone with a PC/Console setup and wears headphone religiously to game, and consume media will benefit much more than I from the high-quality Headphone Amps that are included in the AE-X. Once again, I do feel like Creative could have gone the extra mile to support the S/PDIF port a bit more. Why include it if you're not supporting the main popular digital formats? It seems like the decision was more of a legacy-based one, offering uncompressed 2-channel PCM audio, for users with high-fidelity audio systems and external DACs. Maybe I will be lucky enough to review a card that truly includes all these features in the future. I am sure readers with far more knowledge on audio systems than me will correct me in the comments below. I'll just say I am happy to learn what I don't know! Where to buy The Sound Blaster AE-X is available to purchase now in preorder for $179.99 on the U.S. Creative website, or for £169.99 on the Creative UK website and will start shipping to customers from June 25.
    • $80 or 90%, anything else would be financial suicide one way or another.
  • Recent Achievements

    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • One Month Later
      Genuinetonerink- Dubai earned a badge
      One Month Later
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
    • One Year In
      hhgygy earned a badge
      One Year In
    • Week One Done
      AMV earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      +Edouard
      165
    3. 3
      PsYcHoKiLLa
      88
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      73
  • Tell a friend

    Love Neowin? Tell a friend!