Jay’s Zero‑Drift Windows 11 Install Method

The reason im posting this is, this is as close to a windows 2000 pro install as you can get in windows 11.

This guide describes a deterministic Windows 11 installation method that produces a pristine, drift‑free OS every time.

Why this method works
• Windows drifts because Setup.exe hydrates cloud identity, Store frameworks, and OEM provisioning
• WinPE + DISM removes all mutation vectors
• WinNTSetup gives pre‑boot control and offline user creation
• First‑boot servicing locks the OS into a stable identity
• The result is a clean, reproducible, identity‑free baseline


Deterministic Windows 11 Install Guide
A clean, reproducible, identity‑free installation method using WinPE, a Pro‑only WIM, and WinNTSetup.

1. Boot Into a Clean WinPE Environment
Start from WinPE because it provides:
• no identity
• no cloud sync
• no Store provisioning
• no background tasks
• no OEM services
• no profile state
This ensures the install begins from a zero‑noise environment.

2. Prepare a Pro‑Only WIM
Export only the Windows 11 Pro edition from the ISO:

(Your index may differ depending on the ISO.)
A Pro‑only WIM removes:
• Home edition
• N editions
• OEM variants
• consumer provisioning packages
• cloud‑identity defaults
This collapses the edition decision tree into one deterministic path.

3. Create and Mount a New VHD/VHDX
Inside WinPE:

This gives you a clean, empty universe with no OEM partitions or leftover metadata.

4. Launch WinNTSetup
Configure WinNTSetup with:
• Source: your Pro‑only WIM
• Destination: the mounted VHD/VHDX
• Boot drive: your EFI partition
Enable:
• unattended setup
• offline local user creation (RID 1000)
• skip OOBE
• disable OneDrive
• disable Store auto‑install
WinNTSetup will:
• apply the WIM directly
• build the boot chain
• inject your unattend.xml
• create the user offline
• remove OneDriveSetup.exe
• avoid OOBE entirely
This produces a clean, identity‑free Windows before it ever boots.

5. Offline User Creation (RID 1000)
Your unattend.xml should:
• create a local user
• assign RID 1000
• skip Microsoft account setup
• skip OOBE
• skip privacy screens
This guarantees:
• the same SID
• the same profile path
• the same registry baseline
Every time.

6. First Boot
Boot the VHD normally.
Because of your upstream steps:
• no OOBE
• no Microsoft account
• no Store hydration
• no OneDrive
• no cloud sync
• no consumer provisioning
• no background experiments
You land directly on a pure Windows 11 Pro desktop.

7. Windows Update Timing Window (Critical)
This is the part most people don’t know.
During first boot, Windows Update is already:
• scanning hardware
• staging drivers
• applying the servicing stack
• applying the cumulative update
• updating WinRE
• updating .NET
• finalizing the component store
By the time you reach the desktop, the cumulative update is often 60–90% complete.
Your rule:
Open Windows Update immediately.
Let the cumulative finish.
Reboot as soon as it completes.
This seals:
• the servicing identity
• the update channel
• the component store baseline
• the kernel personality
• the driver model
Rebooting at this moment prevents:
• Store hydration
• cloud identity hooks
• inbox app provisioning
• background tasks
• A/B experiments
• consumer experience packages
This is the step that prevents any drift from happening.

8. Post‑Install (Optional but Clean)
After the first reboot:
• apply your registry personality
• set power plan
• install drivers manually
• disable consumer experience
• disable suggested apps
• configure GPU settings
These do not introduce identity drift.

9. Snapshot or Backup
Once the system is stable:
• take a full system backup
• or clone the VHD
• or create a sector‑level clone
This becomes your genesis image.

Who this method is for
• power users
• sysadmins
• people who reinstall Windows often
• people who want a clean, stable OS
• people who hate drift, bloat, and identity hydration

Well that certainly was ... something.

@Ghot will award you 10 points for using “hydrate” and “mutation vectors” in a first post.

This ignores forced OOBE updates.

I have a sudden urge to hydrate myself. brb...

But here's five points for sort of filling out your computer specs.





Here's some other things that you may find useful...

pseymour said:

Well that certainly was ... something.

Click to expand...

Did he really mean Windows 2000......like 26 years ago 2000??? The one for servers that hasn't been supported in 16 years?
Pssst what is identity hydration?

glasskuter said:

Did he really mean Windows 2000......like 26 years ago 2000??? The one for servers that hasn't been supported in 16 years?
Pssst what is identity hydration?

Click to expand...

Seems like not a typo, since there hasn't been a version with the year on it since that one. There was a version for desktops, but I don't know why someone would want that in whatever year this is.

And I have no idea what some of those terms are, including that one. :)

Reading (and trying to understand) the OP took me longer than a standard Rufus clean install does ....

EDIT

Re-reading makes me suspicious that it was maybe AI generated ..... ?

This Produces one of the Cleanest and most Default Installs you can ask from windows.
Store Apps install as 3rd party apps and so does onedrive, it doesnt take over the OS.

Overkill.

Jayzorg12 said:

The reason im posting this is, this is as close to a windows 2000 pro install as you can get in windows 11.

Click to expand...

I like the intention but I have mucho questions about using even parts of this for myself. Also I have to ask. How do YOU use this method? Are you an IT professional or consultant?

Jayzorg12 said:

This guide describes a deterministic

Click to expand...

What do you mean by deterministic? As opposed to "random" or "stochastic?

Jayzorg12 said:

Windows 11 installation method that produces a pristine, drift‑free

Click to expand...

What is windows "drift?"

Jayzorg12 said:

OS every time.

Why this method works
• Windows drifts because Setup.exe hydrates cloud identity,

Click to expand...

hydrates? cloud identity?

Jayzorg12 said:

Store frameworks, and OEM provisioning

Click to expand...

how do these affect a windows install?

Jayzorg12 said:

• WinPE + DISM removes all mutation vectors
• WinNTSetup gives pre‑boot control and offline user creation
• First‑boot servicing locks the OS into a stable identity
• The result is a clean, reproducible, identity‑free baseline


Deterministic Windows 11 Install Guide
A clean, reproducible, identity‑free installation method using WinPE, a Pro‑only WIM, and WinNTSetup.

1. Boot Into a Clean WinPE Environment
Start from WinPE because it provides:
• no identity
• no cloud sync
• no Store provisioning
• no background tasks
• no OEM services
• no profile state
This ensures the install begins from a zero‑noise environment.

Click to expand...

What constitutes noise?

Jayzorg12 said:

2. Prepare a Pro‑Only WIM
Export only the Windows 11 Pro edition from the ISO:

(Your index may differ depending on the ISO.)
A Pro‑only WIM removes:
• Home edition
• N editions
• OEM variants
• consumer provisioning packages
• cloud‑identity defaults
This collapses the edition decision tree into one deterministic path.

Click to expand...

Why is this necessary? If you are installing a pro version normally, the installer ensures that your install is free of N Editions, etc., etc.

Jayzorg12 said:

3. Create and Mount a New VHD/VHDX
Inside WinPE:

This gives you a clean, empty universe with no OEM partitions or leftover metadata.

4. Launch WinNTSetup
Configure WinNTSetup with:
• Source: your Pro‑only WIM
• Destination: the mounted VHD/VHDX
• Boot drive: your EFI partition
Enable:
• unattended setup
• offline local user creation (RID 1000)
• skip OOBE
• disable OneDrive
• disable Store auto‑install
WinNTSetup will:
• apply the WIM directly
• build the boot chain
• inject your unattend.xml

Click to expand...

Where in this process do you create your unattend.xml? Not trolling here, just uninformed.

Jayzorg12 said:

• create the user offline
• remove OneDriveSetup.exe
• avoid OOBE entirely
This produces a clean, identity‑free Windows before it ever boots.

5. Offline User Creation (RID 1000)
Your unattend.xml should:
• create a local user
• assign RID 1000
• skip Microsoft account setup
• skip OOBE
• skip privacy screens
This guarantees:
• the same SID
• the same profile path
• the same registry baseline
Every time.

6. First Boot
Boot the VHD normally.
Because of your upstream steps:
• no OOBE
• no Microsoft account
• no Store hydration
• no OneDrive
• no cloud sync
• no consumer provisioning
• no background experiments
You land directly on a pure Windows 11 Pro desktop.

7. Windows Update Timing Window (Critical)
This is the part most people don’t know.
During first boot, Windows Update is already:
• scanning hardware
• staging drivers

Click to expand...

What if you want to use drivers from AMD/Intel, your motherboard vendor, your other component vendors rather than MS drivers?

Jayzorg12 said:

• applying the servicing stack
• applying the cumulative update
• updating WinRE
• updating .NET
• finalizing the component store
By the time you reach the desktop, the cumulative update is often 60–90% complete.
Your rule:
Open Windows Update immediately.
Let the cumulative finish.
Reboot as soon as it completes.
This seals:
• the servicing identity
• the update channel
• the component store baseline
• the kernel personality
• the driver model
Rebooting at this moment prevents:
• Store hydration

Click to expand...

???

Jayzorg12 said:

• cloud identity hooks

Click to expand...

???

Jayzorg12 said:

• inbox app provisioning
• background tasks
• A/B experiments

Click to expand...

I wasn't aware that MS is doing A/B testing with Windows installs

Jayzorg12 said:

• consumer experience packages
This is the step that prevents any drift from happening.

8. Post‑Install (Optional but Clean)
After the first reboot:
• apply your registry personality
• set power plan
• install drivers manually
• disable consumer experience
• disable suggested apps
• configure GPU settings
These do not introduce identity drift.

9. Snapshot or Backup
Once the system is stable:
• take a full system backup
• or clone the VHD
• or create a sector‑level clone
This becomes your genesis image.

Click to expand...

I like the idea of a genesis image. How do you use this image to do actual installs for users?

Jayzorg12 said:

Who this method is for
• power users
• sysadmins
• people who reinstall Windows often
• people who want a clean, stable OS
• people who hate drift, bloat, and identity hydration

Click to expand...

I'm not a sysadmin but I do Identify with the other categories.

How do I use the install? I like an identity free windows 11, in my opinion windows comes with alot of hooks to it, i dont like them, and no im just a user like you. #2 I guess i call windows installs chaotic, sometimes this happens.. sometimes this fails, i wanted a default install. #3 Drift, drift to me is what windows does when things like Windows Backup stops working or other apps, its when your identity clashes with system files. #4 Noise: Again just trying to take it back to default, what is default in windows.. and what i'snt you might be surprised. #5 the Pro only was a persional choice but it does factor in to the method, it stop windows from hydrating excess files. The Unattended i use is on my Github, and if people want it ill post it. #7 Drivers, you can add any drivers you want with winntsetup. #8 I guess i was trying to say it stops update noise. #9 Cloud Identity Hooks, Onedrive is my best example, it digs into the os and if you have drifted far enough can really start affecting other apps.

Hope i covered most? things? feel free to ask anything else.

OP, I'm still stuck on identity hydration. What is that?

Cloud Hydration - I guess the best way to explain this is your login, how you log into windows, it forms server side hydration on Microsoft servers, its how they identify you. Thats how they fill your OS with Their data and that data is taken in bits and chunks from how you filled out Setup.

Jayzorg12 said:

onedrive, it doesnt take over the OS.

Click to expand...

OneDrive doesn't take over the OS, unless the (unsuspecting) user allows it

A user who is unable to control OneDrive certainly would not have the wherewithall to manage an installation at the level of the OP.

I'm having trouble rationalising the complexity of the subject OP, from a contributor who had to ask this ...

That was a while before i learned better, never made a mistake and learned from it? i have :)

Idgat: do you have a question about that or?

Its not really about controlling onedrive, its about what onedrive WANTS to do behind your back.

The reason i posted my install method was it took me quite a while to come up with, and i thought some people here might like a default install like i currently do. Would you like me to explain when and where Defaultuser0 is actually created and why?

First post just reads like a AI generated post to me.

Jayzorg12 said:

its about what onedrive WANTS to do behind your back.

Click to expand...

Onedrive is not even installed on my computer.

All i can really say is Please try it, it doesn't harm anything, the differnce from a normal install is crazy.