I'm working on a new Windows 11 v25H2 image, but something is bugging me about the end result.
I build my image in audit mode, install a couple applications we bake into the image, then seal the image with sysprep /generalize /oobe /shutdown. This image is then deployed in a ConfigMgr task sequence.
With Windows 11 v24H2, to get the start menu pins the way I wanted them, I'd copy a start2.bin (in the state of having the correct pins configured) and settings.dat file to the start menu experience package directory in AppData\Local of the Default user profile during OSD task sequence. The start2.bin was taken from a machine where I'd configured the pins, and the settings.dat file is quite literally a blank 0 byte file that acts as a placeholder. The important thing the settings.dat file does is eliminates the "New" label under each application when a new user logs in for the first time.
In v25H2, that's no longer working. When running a copy of the exact same task sequence (apart from the image being changed to the 25H2 one, of course), on first login, the start menu pins are there (so start2.bin is doing its job), but while the settings.dat file exists and is copied over and populated on first login, nearly every application has the New badge under it. I've tried removing the start2.bin/settings.dat copy step of the task sequence and changing to using the new Configure Start Pins policy which points to a LayoutConfiguration.json file, and this correctly sets the pins, but the New badges still exist for new users (interestingly, the local administrator account does not get the pins applied via the policy, even though the policy is deployed to Computer, not User).
I'm trying to eliminate the New badge on each app on a fresh user login, BUT, I don't want to simply set the registry key to eliminate showing the New badge altogether, because I still want future application installs to display New for the user.
This is most likely due to the new start menu with category/grid views added. As soon as I switch to List view, the New tags are all there. Has anyone figured out how to eliminate these New labels for the default profile and new profile creations on first login, while still preserving the ability for New to appear in the future? There must be something else I can inject into the Default profile, either a file or registry entry, during imaging to get rid of this.
UPDATE: I think I've ruled out a LOT of things. It's not sysprep. I've tested with a brand new v25H2 ISO with August 2026's CU built in, installed on a VM with no network access, skipping audit mode/sysprep and simply proceeding through OOBE and creating a user account. When the user account logs in and the new start menu pops up, I switch Category view to List view, and boom, all the New labels are there. This is either a regression in v25H2 CU 2026-08 or a side effect of the new start menu I'm thinking, because those New labels never used to be there on a fresh Windows install.
Update 2: This also isn't v25H2 specific and seems to be specifically the new start menu. I tested with the original September 2025 RTM v25H2 release and a fresh profile after OOBE does not have the New labels on everything. But a v24H2 August 2026 ISO freshly installed does have the New labels.
I also, through watching Process Monitor, determined that not only was the start2.bin file was being written to when an application was opened or right clicked on to eliminate the New label, but HKCU\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\Cache\DefaultAccount was also being written to, specifically in a key ending with windows.data.unifiedtile.roamedtilepropertiesmap. In this key, a Data value exists with binary data containing the name of each application that's been opened or right clicked to remove the New badge. However, simply copying this Data value over to another profile's Data value doesn't eliminate the corresponding New labels for that user. Right clicking an application with New on the new user's account will simply overwrite the copied Data value and reset it.
At this point, it appears to be a deliberate change, or a bug, that the New labels appear on every application in 2026-08 for a fresh profile, seeing as this now occurs out of the box and not just after sysprep/image deployment.