Let's name your device

Phearin

New Member
Messages
24
Reaction score
2
Hi Team,

Currently, I am working on the Windows 11 24H2, yet there are a lots of changing comparing to previous version 23H2.
As browse in the forum, we found some answer related topic about windows.old, and also found sth mentioned about the windows update at the end of OOBE too.
Another new thing, we want to bypass the Let's name your device screen. Does NTlite has any tweak to resolve that?

View attachment 14137

Thanks,.
Phearin
 
I´ll follow this thread with same question. Could you please share the answer to ""Windows Update in OOBE"?
 
1. W11 24H2's default Setup client in WinPE considers a clean install as an "upgrade" experience.

It will always create an empty Windows.old. After a normal install, you can remove this annoyance. Where it breaks things, is when you sysprep and Windows finds the Windows.old folder. To revert WinPE Setup to the legacy client, use Settings / System / Boot/Setup

2. "Let's name your device" can be skipped by providing the ComputerName in Unattended mode.

3. Skip 24H2's forced OOBE Update by applying this reg file from Registry:
Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent]
"DisableCloudOptimizedContent"=dword:00000001
 
3. Skip 24H2's forced OOBE Update by applying this reg file from Registry:
Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent]
"DisableCloudOptimizedContent"=dword:00000001
Just to point that the same tweak is called "Cloud optimized content (Programmable Taskbar)" in the NTLite - loaded image - Settings page.
 
You shouldn't name it "Programmable Taskbar" because it's more like a generic Content Delivery Manager block. This mostly supersedes the 10-15 other CDM reg keys if you didn't want to get specific about blocking individual content feeds.

By leaving the Taskbar off the description, then it's easier to explain that's the right setting in non-Taskbar use cases.
 
The story seems to have went:
  • Windows 10 20H2: Initial implementation with Programmable Taskbar feature
  • Windows 11 21H2: Formal Policy CSP integration
  • Windows 11 23H2: Expanded cloud content controls through related policies like DisableConsumerAccountStateContent
Now it is known as Programmable Taskbar policy, which I named both "Cloud optimized content (Programmable Taskbar)".

Shared impressions here, here and here.
Feel free to comment if there is a better name, feedback is appreciated.
 
The first published articles may be for tweaking the Taskbar, but nowhere in the ADMX template or the CSP does it mention Taskbar. I believe it's just a moniker that different tech sites used, and they ended up copying each other.

Here's we what know DisableCloudOptimizedContent impacts in 24H2:
- disables Spotlight feeds (wallpaper, News & Interests, themed Search icon in taskbar)​
- disables pinning of most default apps & all suggested apps to Start Menu, or the "English (World)" bug​
- disables OOBE Updates​
- disables pinning of Outlook (New) to Taskbar​

My point is the feature list will probably grow longer on each successive Windows release, and labeling it "Taskbar" undersells the other points.
 
nuhi In Group Policies, it's called "Cloud Optimized Content"
Perhaps you could use this name

This option being used for W10 and 11, need a name that suits both OS, for the moment
 
Returning to the request, on the Unattended page, you can specify the name
Or by including this registry key in the Registry page
Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName]
"ComputerName"="your_name"

For the Windows.old directory, in addition to what was been said, by removing the winre component and old setup, it will not be created at installation (but you should not need this component of course)
 
Last edited:
1. W11 24H2's default Setup client in WinPE considers a clean install as an "upgrade" experience.

It will always create an empty Windows.old. After a normal install, you can remove this annoyance. Where it breaks things, is when you sysprep and Windows finds the Windows.old folder. To revert WinPE Setup to the legacy client, use Settings / System / Boot/Setup

2. "Let's name your device" can be skipped by providing the ComputerName in Unattended mode.

3. Skip 24H2's forced OOBE Update by applying this reg file from Registry:
Code:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent]
"DisableCloudOptimizedContent"=dword:00000001
garlin Thank you for your information tips sharing. It works. Yet, I wasn't understand there is minor issue of this page. Unless we clicked try
again then the system will continue. What was issue at this stage?

View attachment 14148
 
OOBE Zero Day Patch (ZDP) is a last-minute update downloaded to improve the OOBE experience. If you have this problem some component may have been incorrectly removed.

Please attach your preset (after removing any user passwords or license key).
 
garlin Thank you for your information tips sharing. It works. Yet, I wasn't understand there is minor issue of this page. Unless we clicked try
again then the system will continue. What was issue at this stage?

View attachment 14148
Make sure to keep OOBE compatibility turned on, it will lock needed components from removal.
 
OOBE Zero Day Patch (ZDP) is a last-minute update downloaded to improve the OOBE experience. If you have this problem some component may have been incorrectly removed.

Please attach your preset (after removing any user passwords or license key).
garlin I think I might have done sth wrong with the step. However, I tried to used old preset from previous version, and it is working fine. Thank you for your input.
 
Back
Top