You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As many of you probably know, Windows 11 is usually shipped with a lot of limitations, cloud integrations, telemetry components, advertisements, placeholders, and preinstalled bloat that many power users and deployment engineers don’t actually want.
I know that some of these limitations can be bypassed through autounattend.xml, and some of the bloat can be removed during installation.
However, after researching many existing unattended/debloat projects, I noticed that a lot of them are not truly native solutions anymore.
Many projects:
download third-party tools,
run external debloat scripts,
install additional applications,
or rely heavily on post-install hacks.
That is NOT my goal.
My goal is to build a mostly native and clean Windows deployment approach using:
official Windows setup passes,
native unattend functionality,
supported policies,
registry-based deployment methods,
and built-in Windows tools as much as possible.
The purpose is to:
reduce manual post-install work,
automate repetitive tweaks,
speed up deployment on different systems,
and create a reusable, reliable, and lightweight Windows 11 installation workflow.
Current Testing Environment
Windows 11 24H2
Virtual machine testing
Custom autounattend.xml
Native registry/policy tweaks
No third-party debloat applications
The XML itself loads correctly and all setup phases execute successfully.
Features That Worked Successfully
Hardware Requirement Bypasses
Local account creation
OOBE online-account bypass
AutoLogon
EULA skipping
OneDrive / Provisioned App Cleanup
Mostly successful:
OneDrive setup executables removed
Teams removed
Outlook mostly removed
Several Store placeholders prevented from auto-installing
Widgets / News / Taskbar Cleanup
Widgets are no longer visible
News/Feeds appear disabled
Fast Startup
Successfully disabled
Many Registry Policies
A large number of privacy and policy-related registry entries were written successfully.
Features That Did NOT Fully Work
This is the interesting part.
Some tweaks successfully changed registry values, but the actual Windows behavior did NOT change accordingly.
Driver Download Disable
The related registry values exist, but Windows still appears willing to download drivers automatically.
sysdm.cpl still showed the setting enabled until I manually changed it.
Explorer LaunchTo = This PC
Registry values exist, but File Explorer still opens to Home / Quick Access instead of This PC.
SmartScreen Disable
The registry keys were applied, but SmartScreen still remains enabled in Windows Security.
Telemetry Disable
Telemetry-related registry values exist, but services like DiagTrack are still running.
Consumer Features / Cloud Content
The related policies exist, but it is difficult to verify whether Windows internally still delivers recommendations, cloud content, suggested apps, etc.
Windows Feeds / Widgets Packages
Widgets are visually disabled, but small placeholder packages still remain under Installed Apps.
Feedback Hub
Feedback Hub still remained installed.
Edge Removal
I understand Edge is now deeply integrated into the OS, but I am still researching whether there is a deployment-safe/native way to:
remove Edge,
prevent reinstall,
while avoiding WebView2 breakage.
Start Menu Binary Tweaks (VisiblePlaces)
I tested binary Start Menu tweaks, but they appear inconsistent or ignored in 24H2.
Main Question
It seems many older Windows tweak methods still write registry values successfully, but no longer fully affect actual Windows behavior in modern Windows 11 builds.
So my main question is:
Which of these features are still realistically achievable:
natively,
cleanly,
reliably,
and deployment-safe
through:
autounattend.xml
native Windows setup passes
official policy-based configuration
provisioning
DISM
or supported Microsoft deployment methods
I would really appreciate feedback, ideas, testing results, or collaboration from people who are actively working on:
Windows deployment,
unattended installation,
debloating,
enterprise imaging,
MDT/Sysprep,
or modern Windows 11 customization.
My goal is not to create another “aggressive debloat script,” but rather to build a clean, stable, reusable, and mostly native Windows 11 unattended deployment setup.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
As many of you probably know, Windows 11 is usually shipped with a lot of limitations, cloud integrations, telemetry components, advertisements, placeholders, and preinstalled bloat that many power users and deployment engineers don’t actually want.
I know that some of these limitations can be bypassed through autounattend.xml, and some of the bloat can be removed during installation.
However, after researching many existing unattended/debloat projects, I noticed that a lot of them are not truly native solutions anymore.
Many projects:
That is NOT my goal.
My goal is to build a mostly native and clean Windows deployment approach using:
The purpose is to:
Current Testing Environment
The XML itself loads correctly and all setup phases execute successfully.
Features That Worked Successfully
Hardware Requirement Bypasses
These worked correctly:
OOBE / Setup Automation
These also worked:
OneDrive / Provisioned App Cleanup
Mostly successful:
Widgets / News / Taskbar Cleanup
Fast Startup
Many Registry Policies
A large number of privacy and policy-related registry entries were written successfully.
Features That Did NOT Fully Work
This is the interesting part.
Some tweaks successfully changed registry values, but the actual Windows behavior did NOT change accordingly.
Driver Download Disable
The related registry values exist, but Windows still appears willing to download drivers automatically.
sysdm.cpl still showed the setting enabled until I manually changed it.
Explorer LaunchTo = This PC
Registry values exist, but File Explorer still opens to Home / Quick Access instead of This PC.
SmartScreen Disable
The registry keys were applied, but SmartScreen still remains enabled in Windows Security.
Telemetry Disable
Telemetry-related registry values exist, but services like DiagTrack are still running.
Consumer Features / Cloud Content
The related policies exist, but it is difficult to verify whether Windows internally still delivers recommendations, cloud content, suggested apps, etc.
Windows Feeds / Widgets Packages
Widgets are visually disabled, but small placeholder packages still remain under Installed Apps.
Feedback Hub
Feedback Hub still remained installed.
Edge Removal
I understand Edge is now deeply integrated into the OS, but I am still researching whether there is a deployment-safe/native way to:
Start Menu Binary Tweaks (VisiblePlaces)
I tested binary Start Menu tweaks, but they appear inconsistent or ignored in 24H2.
Main Question
It seems many older Windows tweak methods still write registry values successfully, but no longer fully affect actual Windows behavior in modern Windows 11 builds.
So my main question is:
Which of these features are still realistically achievable:
through:
WITHOUT heavily relying on:
Looking for Collaboration / Ideas
I would really appreciate feedback, ideas, testing results, or collaboration from people who are actively working on:
My goal is not to create another “aggressive debloat script,” but rather to build a clean, stable, reusable, and mostly native Windows 11 unattended deployment setup.
Thanks in advance.
This is my autounattend.xml file:
`
true 1 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassTPMCheck /t REG_DWORD /d 1 /f 2 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassSecureBootCheck /t REG_DWORD /d 1 /f 3 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassRAMCheck /t REG_DWORD /d 1 /f 4 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassCPUCheck /t REG_DWORD /d 1 /f 5 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassStorageCheck /t REG_DWORD /d 1 /f 6 reg.exe add "HKLM\SYSTEM\Setup\LabConfig" /v BypassDiskCheck /t REG_DWORD /d 1 /f 1 reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE" /v BypassNRO /t REG_DWORD /d 1 /f 2 reg add "HKLM\Software\Policies\Microsoft\Windows\OneDrive" /v DisableFileSyncNGSC /t REG_DWORD /d 1 /f 3 cmd /c if exist %SystemRoot%\System32\OneDriveSetup.exe del /f /q %SystemRoot%\System32\OneDriveSetup.exe 4 cmd /c if exist %SystemRoot%\SysWOW64\OneDriveSetup.exe del /f /q %SystemRoot%\SysWOW64\OneDriveSetup.exe 5 PowerShell -NonInteractive -WindowStyle Hidden -Command "Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -like '*Outlook*'} | Remove-AppxProvisionedPackage -Online" 6 PowerShell -NonInteractive -WindowStyle Hidden -Command "Get-AppxPackage -AllUsers *Outlook* | Remove-AppxPackage -AllUsers" 7 PowerShell -NonInteractive -WindowStyle Hidden -Command "Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -like '*Teams*'} | Remove-AppxProvisionedPackage -Online" 8 PowerShell -NonInteractive -WindowStyle Hidden -Command "Get-AppxPackage -AllUsers *Teams* | Remove-AppxPackage -AllUsers"All reactions