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
Copy file name to clipboardExpand all lines: docs/about.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,10 @@ To see the improved end-user experience, check out the [Results](https://stealth
17
17
18
18
Supporting Windows 10, Windows 11, and Windows Server 2016–2025, this tool works for both physical PCs and virtual machines (e.g., Azure Virtual Desktop, Windows 365). While primarily aimed at provisioning gold images for PCs or virtual desktops, it can also be applied to Windows Server infrastructure roles.
19
19
20
+
::: info
21
+
Windows PowerShell only is supported - typically during operating system deployments, there should be no strict requirement for PowerShell 6 or above. While the solution will work OK on PowerShell 6+, no testing is done on those versions.
22
+
:::
23
+
20
24
Windows Enterprise Defaults has been tested on Windows 10 (1809 and above), Windows 11, Windows Server 2016-2025. All scripts should work on any future versions of Windows; however, you should test thoroughly before deployment in production.
21
25
22
26
## Usage
@@ -28,9 +32,3 @@ The solution is intended for operating system deployment via various methods, in
28
32
* Executed in a virtual machine image pipeline using [Azure Image Builder](https://docs.microsoft.com/en-us/azure/virtual-machines/image-builder-overview) or [Packer](https://www.packer.io/) when building a gold image
29
33
* Imported into the Microsoft Deployment Toolkit as an application for use during Lite Touch deployments - [Create a New Application in the Deployment Workbench](https://docs.microsoft.com/en-us/mem/configmgr/mdt/use-the-mdt#CreateaNewApplicationintheDeploymentWorkbench)
30
34
* Or even run manually on a Windows PC or virtual machine gold image if you're not using automation at all
31
-
32
-
## Supported PowerShell
33
-
34
-
::: info
35
-
Windows PowerShell only is supported - typically during operating system deployments, there should be no strict requirement for PowerShell 6 or above. While the solution will work OK on PowerShell 6+, no testing is done on those versions.
Copy file name to clipboardExpand all lines: docs/custom.md
+50-50Lines changed: 50 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,60 +133,60 @@ Importing a default Start menu is implemented with the following JSON; however,
133
133
134
134
For Windows 10 or Windows 11, the Start menu layout to import, is specified with the `Windows10` or `Windows11` property; while for Windows Server, the Start menu layout is specified by the presence or not of a specified Windows feature - in the example below a specific layout is imported is the Remote Desktop Session Host role is installed.
Copy file name to clipboardExpand all lines: docs/feature.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,11 @@ When `Install-Defaults.ps1` runs, it copies the project files to `C:\WINDOWS\Sys
11
11
12
12
When a feature upgrade completes (e.g. Windows 11 23H2 to Windows 11 24H2), `success.cmd` is executed. This will re-run `Install-Defaults.ps1` and explicitly run `Remove-AppxApps.ps1` in [targeted mode](https://stealthpuppy.com/defaults/appxapps/#targeted-package-list). This removes a set of AppX applications that are often reinstalled during a feature update.
13
13
14
-
```batch
14
+
::: code-group
15
+
```batch [success.cmd]
15
16
@ECHO OFF
16
17
SET SOURCE=C:\WINDOWS\System32\update\run\f38de27b-799e-4c30-8a01-bfdedc622944
Copy file name to clipboardExpand all lines: docs/machine.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ Machine specific settings are implemented to configure the local Windows OS with
15
15
16
16
Enables the Windows Search and Audio services if the Remote Desktop Session Host role is enabled. This uses a specification in the JSON that will enable a list of services, if a specified Windows feature is enabled:
17
17
18
-
```json
18
+
::: code-group
19
+
```json [Machine.Server.json]
19
20
"Services": {
20
21
"Feature": "RDS-RD-Server",
21
22
"Enable": [
@@ -24,12 +25,14 @@ Enables the Windows Search and Audio services if the Remote Desktop Session Host
24
25
]
25
26
}
26
27
```
28
+
:::
27
29
28
30
## Windows 10 and Windows 11
29
31
30
32
* Disables the following features that are not used on most end-user desktops: `Printing-XPSServices-Features`, `SMB1Protocol`, `WorkFolders-Client`, `FaxServicesClientPackage`, `WindowsMediaPlayer`. A set of features to disable can be listed in the JSON as shown below.
31
33
32
-
```json
34
+
::: code-group
35
+
```json [Machine.All.json]
33
36
"Features": {
34
37
"Disable": [
35
38
"Printing-XPSServices-Features",
@@ -40,14 +43,16 @@ Enables the Windows Search and Audio services if the Remote Desktop Session Host
40
43
]
41
44
}
42
45
```
46
+
:::
43
47
44
48
::: warning
45
49
WindowsMediaPlayer is included by default with the expectation that you are deploying an alternative, modern media player, such as VLC Player. Removal of the Windows Media Player may affect some media playback features.
46
50
:::
47
51
48
52
Removes the following capabilities that are not used on most enterprise end-user desktops: `App.Support.QuickAssist~~~~0.0.1.0`, `Media.WindowsMediaPlayer~~~~0.0.12.0`, `XPS.Viewer~~~~0.0.1.0`. Capabilities to remove can be listed in the JSON as below:
49
53
50
-
```json
54
+
::: code-group
55
+
```json [Machine.All.json]
51
56
"Capabilities": {
52
57
"Remove": [
53
58
"App.Support.QuickAssist~~~~0.0.1.0",
@@ -56,14 +61,16 @@ Removes the following capabilities that are not used on most enterprise end-user
56
61
]
57
62
}
58
63
```
64
+
:::
59
65
60
66
## Windows 10 19041 and above
61
67
62
68
Windows 10 2004 (10.0.19041) and above will include the following configuration changes:
63
69
64
70
Removes the following capabilities that are not used on most end-user desktops: `Microsoft.Windows.PowerShell.ISE~~~~0.0.1.0`, `Microsoft.Windows.WordPad~~~~0.0.1.0`, `Print.Fax.Scan~~~~0.0.1.0`, `Print.Management.Console~~~~0.0.1.0`. Capabilities to remove from a specific Windows build, or higher, can be listed in the JSON as below:
65
71
66
-
```json
72
+
::: code-group
73
+
```json [Build.All.json]
67
74
{
68
75
"MinimumBuild": "10.0.19041",
69
76
"Capabilities": {
@@ -75,3 +82,4 @@ Removes the following capabilities that are not used on most end-user desktops:
Copy file name to clipboardExpand all lines: docs/profile.md
+47-22Lines changed: 47 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ layout: doc
5
5
6
6
Customising the default user profile is an important step in configuring the default environment that will user see at first sign-in.
7
7
8
-
Configuring the default profile allows the administrator to reduce noise for the end-user while still allowing them to customise their environment afterwards. This is a better approach that enforcing settings via Group Policy and this will also work for Azure AD joined scenarios.
8
+
Configuring the default profile allows the administrator to reduce noise for the end-user while still allowing them to customise their environment afterwards. This is a better approach that enforcing settings via Group Policy, and will work for Entra joined scenarios.
9
9
10
10
The approach used by these scripts is to make changes directly to the default user profile found at `C:\Users\Default`. When users sign into Windows for the first time, their profile starts as a copy of the default profile, thus it will pick up the customisations.
11
11
@@ -25,29 +25,54 @@ Imports a Start menu and taskbar layout (`Windows10StartMenuLayout.xml` or `Wind
25
25
26
26
These settings are imported into the default profile via direct file copies. The source file and destination are defined in the JSON sources as in the examples below. Here Windows 10 and Windows 11 default Start menu and taskbar layouts are defined in the included files and are copied to the specified destination.
Imports registry settings in the default profile to support Windows running in a virtual machine, typically VDI scenarios. This includes disabling transparency effects, windows animations, and disabling background applications.
Copy file name to clipboardExpand all lines: docs/registry.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
---
1
+
---
2
2
layout: doc
3
3
---
4
4
# Registry Settings
@@ -47,7 +47,6 @@ layout: doc
47
47
| HKLM: \Software \Policies \Microsoft \Windows \CloudContent | DisableWindowsConsumerFeatures | 1 | Disables the Microsoft Windows consumer features |
48
48
| HKLM: \Software \Policies \Microsoft \Windows \CloudContent | DisableCloudOptimizedContent | 1 | Disables the customisation of the taskbar with additional shortcuts (e.g. new Outlook) |
49
49
50
-
51
50
**Computer level settings for Windows client editions.**
52
51
53
52
| Minimum build | Maximum build | Type |
@@ -168,8 +167,8 @@ layout: doc
168
167
| ---- | ---- | ----- | ---- |
169
168
| HKCU: \Software \Microsoft \Windows \CurrentVersion \Explorer \Wallpapers | BackgroundType | 0 | Sets the desktop background type to a picture |
0 commit comments