Microsoft built a developer-focused configuration of Windows 11 it calls Project Zenith, and the company says it "represents Windows at its best": tips switched off, account notifications silenced, and a quieter File Explorer and Start menu.
The first announced hardware platform for Project Zenith is AMD's Ryzen AI Halo, although Microsoft plans to expand the program to other devices.
That's worth considering before getting excited about a less cluttered Windows 11 for developers. Project Zenith is a real configuration, but its calmer interface settings don't inherently require the high-end hardware Microsoft has chosen for the program. Anyone hoping a Zenith machine will fix Windows 11's clutter problem should know what they're actually paying for first.
Project Zenith isn't a new Windows edition. Windows Central expects Zenith devices to ship with either Windows 11 Home or Pro depending on the OEM, just with different default settings and preinstalled developer tools layered on top.
To qualify for that factory configuration, a PC needs at least 64GB of unified memory and 250GB/s of memory bandwidth, requirements confirmed in Microsoft's September 4 announcement. AMD's Ryzen AI Halo is the first announced platform, with other devices from Microsoft's hardware partners expected in the coming months.
Microsoft hasn't published a comprehensive list of certified models, prices, or shipping dates.
What Project Zenith actually ships, and who can buy it
Zenith is a hardware and software program Microsoft introduced in September for PCs running this modified Windows 11 setup, not a distinct Windows edition.
Microsoft frames it as a fix for a specific complaint: developers have said that preparing a new Windows PC for coding can take hours or even days, and Zenith machines are meant to be ready to code the moment they reach the desktop.
To that end, Zenith devices arrive with preinstalled developer tools spanning source control, coding, and productivity. Microsoft's announcement confirms that Windows Terminal and Visual Studio Code are pinned to the taskbar out of the box.
The company's presentation also identifies tools such as GitHub Copilot, PowerToys, Windows App CLI, and Windows Dev Skills as part of its developer-focused setup.
AMD's Ryzen AI Halo is the first confirmed hardware platform for this configuration, while Microsoft plans to bring the experience to additional OEM and silicon partners.
That matters for how the rest of this gets judged. Zenith is a packaging and hardware qualification decision sitting on top of ordinary Windows 11, which is exactly why it's fair to ask which parts of the package actually require the hardware underneath, and which parts don't.
Windows 11 Project Zenith requirements: what the hardware actually enables
Most of what Zenith changes is mundane.
File Explorer shows file extensions, hidden files, full paths, and the details pane, with long-path support turned on by default. Microsoft also disables recently used files and folders, sync-provider tips, Start menu tips, and account notifications, while enabling PowerToys Command Palette.
These are existing Windows settings or features available through Microsoft's developer tools. None of those interface changes inherently requires 64GB of memory or a high-bandwidth memory controller.
The clearest hardware-specific benefit Microsoft has identified is different.
The 64GB unified memory and 250GB/s bandwidth requirement is intended to enable capable local AI workloads, including models with more than 30 billion parameters.
Logan Iyer, Microsoft's corporate vice president of Windows platform and developer, says running these models locally and without metered cloud tokens can help reduce reliance on paid cloud inference.
That's a real capability tied to hardware resources, although actual model performance still depends on factors such as model size, quantization, memory allocation, and the available compute hardware.
Microsoft has also described security and management features, including OS-enforced identity, Microsoft Execution Containers, and enterprise-grade controls, as part of the broader platform rather than the interface defaults specifically.
The criticism raised by Neowin is worth considering. Not every developer needs to run a 30-billion-parameter model locally, and a 32GB laptop can benefit from a distraction-free setup and bundled development tools too.
Microsoft's hardware threshold makes sense for its targeted local AI workloads. What it hasn't explained is why the unrelated interface defaults, the ones with nothing to do with memory bandwidth, need to remain associated with devices that clear that threshold.
The Windows Dev Config script: a shortcut, not a debloat button
Microsoft hosts its Windows Developer Config tools on GitHub, and they can run on compatible Windows PCs outside the Zenith hardware program.
The repository provides standard and full configurations that install developer tools, adjust Windows settings, and set up Windows Subsystem for Linux with Ubuntu.
Microsoft estimates that a clean installation takes roughly half an hour with a good internet connection, largely because the process downloads and installs applications.
At Build 2026, a Microsoft representative reportedly said the company would consider building similar configuration options directly into Windows 11's Settings app, according to PCMag.
Windows already ships a Developer Mode switch, so a clearly labeled, dedicated preset for a quieter Windows 11 would be a logical extension of the existing controls. Microsoft hasn't announced such a preset for general release.
The GitHub documentation now provides more detail about what the configuration changes and how to undo it.
The current repository describes standard and full setup options, with the full experience enabling additional settings such as Developer Mode, Sudo, Remote Desktop, and changes to Microsoft Edge policies.
It also documents an uninstall action that resets configuration changes and removes installed tools and Ubuntu data. That makes the setup more transparent than an undocumented debloat script, but it doesn't mean every change is harmless or that uninstalling will restore every aspect of a previous installation.
The distinction matters because these scripts do considerably more than silence notifications. They install development software, change system settings, and may enable features that require a restart.
Microsoft's repository describes the configurations as repeatable and provides troubleshooting and removal instructions. However, that documentation doesn't establish that running the scripts produces a machine identical to a factory-configured Zenith PC.
Anyone curious enough to try them should read the current setup instructions, review the standard and full configurations, and back up important data before making system changes.
For a PC used for everyday work, the standard configuration is a less extensive starting point than the full setup, but neither should be treated as a simple one-click clutter-removal tool.
Who should actually care about Project Zenith
Developers who specifically want to run 30-billion-plus parameter models locally and reduce metered cloud costs have a genuine reason to look at Zenith-class hardware as more products become available.
That's a narrower use case than general Windows customization, and it's the part of the program that most clearly depends on the memory and bandwidth specifications Microsoft requires.
Everyone else chasing a quieter File Explorer and fewer notification pop-ups is chasing a setting, not a chip.
Nothing in Microsoft's description of Zenith's interface changes ties those defaults to the hardware tier. Many can already be applied manually, and Windows Developer Config provides a broader automated setup for people who also want development tools.
The detail worth tracking is Microsoft's openness to a native Settings preset. If that ships, it could make the calmer interface configuration accessible without requiring users to run a developer setup script or buy a new PC.
What to do now
Project Zenith is a developer-focused hardware and software program built around ordinary Windows 11 with calmer defaults layered on top.
Microsoft ties its 64GB and 250GB/s hardware threshold to the ability to run large local AI models, a capability that has nothing to do with whether File Explorer shows hidden files.
A publicly hosted configuration tool can apply many of the same developer-oriented settings on other PCs today, with Microsoft now documenting setup options, limitations, and removal procedures.
Don't buy Ryzen AI Halo hardware expecting a transformed desktop if the real goal is less clutter rather than local AI development.
Those are two separate value propositions under the same program, and Microsoft hasn't announced a consumer-facing Settings preset that applies the full Zenith configuration.
If running 30B+ parameter models locally is the actual need, Zenith-class hardware is worth considering as more partners announce devices.
If it isn't, and the goal is just a quieter desktop, start with the Windows settings already available on your PC. If you also want a configured development environment, review Microsoft's Windows Developer Config repository, choose the appropriate setup, and back up your system first.
Either way, watch whether Microsoft follows through on building a native Settings preset. That's the detail that could determine whether Zenith's quieter interface becomes a standard Windows option or remains associated with specialized developer hardware.
Comments
Be the first, drop a comment!