Project Zenith Explained: Recreate Microsoft’s Windows 11 Developer Setup on Existing PCs

What Project Zenith is​

Microsoft announced Project Zenith on September 4, 2026, as a preconfigured Windows 11 experience for developer-class PCs. The Windows Developer Blog post, written by Logan Iyer, calls it a ready-to-code, distraction-free Windows experience. It is aimed at devices with 64 GB or more of unified memory and 250 GB/s or more of memory bandwidth.

Several outlets agree on the framing:

• 4sysops says it is not a separate Windows edition. It is a hardware-specific software bundle that OEMs ship on new developer-class machines.
• WinBuzzer likewise says Microsoft describes a device experience, not a separate Windows edition.
• It will launch first on AMD's Ryzen AI Halo devices, and reach other systems over the coming months.

The "normal people aren't allowed" part is a fair reading of the hardware gate. 4sysops notes that Microsoft has not published a list of supported models or a way to enable the experience on existing PCs. The How-To Geek piece also says RTX Spark devices are expected. The Microsoft post I could check names only AMD's Ryzen AI Halo, so treat RTX Spark as unconfirmed. Windows Central also says other chipmakers such as RTX Spark are expected to follow.

Pricing and dates are also missing. Microsoft has not disclosed pricing or a release date beyond the AMD Ryzen AI Halo debut, and has not named the first OEMs.

What Microsoft says it changes​

Microsoft's announcement lists specific defaults:

• File Explorer: it shows file extensions, hidden files, the full path in the title bar and the details pane. Long-path support is enabled.
• Turned off: recently used files and folders, sync provider tips, Start menu tips and account notifications.
• Search and Start: Command Palette is enabled.
• Taskbar: Windows Terminal and Visual Studio Code are pinned.
• Preinstalled tools: a set spanning languages and runtimes, source control and productivity tools.

Microsoft's post does not give a full tool inventory. Windows Central, citing The Verge, says GitHub Copilot, PowerToys, WinAppCLI and Windows Dev Skills will also be preinstalled. That is secondhand, so don't treat it as an official list.

The hardware pitch is local AI. Microsoft says developers can run 30B+ parameter models locally and unmetered, which reduces reliance on metered cloud tokens. That is Microsoft's claim. WinBuzzer points out that actual speed and memory use depend on the model and software.

None of this is a removal of preinstalled apps or a privacy cleanup. It is mostly a set of settings toggles plus extra software. "Bloat-free" is a stretch.

The public route: Windows Developer Config​

Microsoft's open-source WindowsDeveloperConfig repository on GitHub gives existing PCs a similar starting point. Its README says setups can be launched from any PowerShell window, elevated or not. It offers two main commands:

irm [[CmdletBinding()]](https://aka.ms/devconfig/standard/setup.ps1) | iex
irm [[CmdletBinding()]](https://aka.ms/devconfig/full/setup.ps1) | iex

Standard installs a long list of tools:

• Windows Terminal, PowerShell 7, Git, GitHub CLI and GitHub Copilot CLI
• VS Code, .NET SDK 10, Python 3.14 with uv, and Node.js LTS with nvm
• Coreutils for Windows, Windows App CLI, Oh My Posh and PowerToys

It also sets PowerShell 7 as the default terminal profile and uses Cascadia Mono NF as the default font. Windows settings it changes include dark theme, long paths, File Explorer defaults, Start and Search settings, and Do Not Disturb. It also installs WSL and Ubuntu.

Full includes everything in Standard. It adds Developer Mode, Sudo, widgets off, Edge policies, extra Start, Search and system tray settings, and Remote Desktop enabled with firewall settings applied.

The repository also has separate options that are not part of Standard or Full: WSL Comfort, single-language workloads, and local AI tooling.

Practical cautions​

• Restart: the README warns the PC may restart, because WSL needs virtualization turned on. Save your work first. A scheduled task resumes setup after you sign back in. If nothing happens after a couple of minutes, re-running the command is documented as safe.
• Virtualization: if the WSL install fails, the README points to virtualization (VT-x or AMD-V) being disabled in BIOS/UEFI. In a VM, it points to nested virtualization not being exposed by the host.
• Remote Desktop: the Full setup enables it. On a general-purpose machine, that is a security decision you should make deliberately.
• Piping to iex: this runs downloaded code. Read the documentation first, and consider using it on a test machine.
• Not a clone of Zenith: the README does not claim to reproduce Zenith exactly. It also doesn't document removing preinstalled apps, disabling telemetry, or touching BitLocker or Windows Update. That is what third-party debloaters do.

Who should care​

• Developers on ordinary hardware: Windows Developer Config gets you most of the way with the standard or full setup. It is documented as re-runnable.
• Everyone else: How-To Geek's author recommends third-party tools such as Chris Titus's WinUtil for debloating instead. That is one writer's opinion, and those tools carry their own risks. His point that Microsoft's scripts add developer software that non-developers don't need is accurate.
• IT admins: 4sysops says to wait for clearer OEM availability and Intune guidance. Those aren't published yet.

Bottom line​

Zenith is a hardware-tied, developer-focused configuration, not a bloat-free Windows for everyone. For most readers, the useful news is that Microsoft's own Windows Developer Config repository approximates it on existing PCs. For non-developers, it brings more software than they want. Microsoft's own post says Windows is becoming faster, calmer and more polished, with more control over experiences. Whether that control reaches non-developer users in the same preconfigured form is still an open question.