Search box (Taskbar) on Windows 11 Build 22621.1344

petle

New Member
Hallo zusammen

Kann die Einstellung für den SuchfeldTaskbarModus (0,1,oder 2 nicht mehr ändern hat bis zum Build 2261.1265 immer zuverlässig funktioniert. Ist dies ein Bug im NTlite oder hat Microsoft wieder Umstellungen gemacht?
 
Please translate to English when posting.
Hello everyone Can't change the setting for the search field taskbar mode (0,1,or 2) always worked reliably up to build 22621.1265. Is this a bug in NTlite or has Microsoft made changes again?

February 28, 2023—KB5022913 (OS Build 22621.1344) Preview
New!
This update improves the search box experience on the taskbar. As you type in the search box, search results now appear in the search flyout box. You can also change the search experience you want for your taskbar by going to Settings > Personalization > Taskbar. For commercial customers, this update adds a new policy for IT administrators to manage how the search box on the taskbar appears in your organization. For more information, see Customizing search on the Windows 11 taskbar.

The registry key works the same as before. NTLite is missing dword:00000003 for recent W11 builds.
 
I installed 22621.1344 from UUP dump, and tested the Search (Taskbar) setting.

1. NTLite does correctly set SearchboxTaskmode, in the Default user's NTUSER.DAT
2. User account provisioning now blocks this setting for new users.

For this to work, NTLite has to switch from HKCU to a HKLM-based GPO (which forces it for all users, with no individual choices).
https://www.elevenforum.com/t/add-or-remove-search-button-on-taskbar-in-windows-11.1197/

Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"SearchOnTaskbarMode"=dword:00000001

ValueDescription
0Hide.
1Search icon only.
2Search icon and label.
3 (Default)Search box.

nuhi?

UPDATE: Just to be clear, HKCU SearchboxTaskmode still works after your account is created, like in Post-Setup (User). I haven't checked how far back the new policy became effective.
 
Last edited:
Mod note: Merging dupe question.

Ive tried multiple times so Im wondering if this setting changed in 22H2.

In NTLite, I set the choice to ICON (along with other settings) but this one particular setting never works properly.

I did a snapshot of what key windows changes when using the Settings App:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search

Here is the actual line of my preset that I think should be setting the icon...

<Tweak name="Search\SearchboxTaskbarMode">1</Tweak>

There is not enough info in ntlite.log to see if it actually was applied to the image. All I can see is one line indicating it is applying tweaks.

Is there anyway to turn on more verbose logging?

Is there anyway to see what each NTLite setting actually changes?

Thanks
 
<Tweak name="Search\SearchboxTaskbarMode">1</Tweak>
Is there anyway to see what each NTLite setting actually changes?
Every tweak is a registry change, and name matches the last part of the actual key's path. If you searched online using those words, it's easy to match what NTLite is updating.
 
I just see my question merged with this thread and it definitely seems like the same issue.

petele responded that "its working fine now", but i dont know what the fix was.

Did ntlite get updated or is he saying to add a line to the user portion of the post-setup phase?
 
I added this line to the system portion of post processing to set searchtaskbar mode as described above but it appears to be ignored.
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Search" /v SearchboxTaskbarMode /d 1

I also cant get it to work by using the searchtaskbarmode tweak.
Any suggestions?
 
You have two choices:
Post-Setup (Machine) -> reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Search" /v SearchOnTaskbarMode /t REG_DWORD /d 1
Post-Setup (User) -> reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Search" /v SearchboxTaskbarMode /t REG_DWORD /d 1

SearchboxTaskbarMode must be set during your first logon, to work.
 
Last edited:
Thanks for the info. I tried both choices verbatim. The key is created successfully but it isnt being applied.

Is there anything else I need to do other than set the key correctly in post-setup phase?

Additionally, I thought policies were applied at account creation and then every X hours when gpupdate runs. Is that not correct? I was even taught that gpupdate /force would trigger both machine and user policies to update immediately. However this isnt appear to work for me.

Thanks.
 
Last edited:
Oops, my bad! I copied the wrong line before editing. The current HKCU command has been tested and works in real-time.
 
Back
Top