Windows 11 users finally have movement on three interface requests that have followed the operating system since its original launch: more control over the taskbar position, a Start menu that can be made less intrusive, and a Windows Search experience that can stay focused on local content instead of web suggestions. According to Windows Latest, the changes are included with the optional KB5120998 preview update and are beginning to roll out through Microsoft’s usual staged feature process.
For IT teams and power users, the headline is not simply that these options exist. The more practical point is that they may already be present in the update payload even if they do not appear immediately after installation. Microsoft is using Controlled Feature Rollout, which means some PCs will see the controls right away while others will wait for Microsoft to enable them remotely. That creates a familiar advisory question: should you wait, or should you manually enable the switches on selected machines?
What is new in KB5120998
The first major change is taskbar repositioning. Windows 11 removed the familiar ability to place the taskbar on different screen edges, forcing most users into a bottom-aligned workflow. KB5120998 starts restoring that flexibility, including the ability to move the taskbar to other sides of the display. This is especially useful for ultrawide monitors, developers who prefer vertical space for code, and users who built years of muscle memory around side-mounted taskbars.
The second change is a more manageable Start menu. Windows Latest reports that Microsoft is adding size and layout controls so users can reduce how much screen space the Start menu consumes. The updated configuration also gives users more granular control over sections such as pinned items, recent content, and the all-apps view. For smaller laptops and shared-screen work, this is more than cosmetic: a Start menu that dominates the display can interrupt meetings, demos, and remote support sessions.
The third improvement is Windows Search cleanup. The update adds controls to remove Bing web results and Microsoft Store suggestions from Search, allowing the box to return only local apps, settings, and files when the toggles are disabled. This is likely to be the most valuable change for many business users. Local search is often used as a launcher or quick configuration tool, and web fallbacks can be distracting when a user simply wants Device Manager, a document, or a control panel setting.
Rollout behavior: do not assume every PC will look the same
KB5120998 is an optional preview update, not a mandatory Patch Tuesday release. Optional previews are commonly used to validate fixes and feature changes with a broader audience before they are rolled into a future cumulative update. Even after installation, Microsoft can keep individual feature flags disabled while it monitors reliability data.
That means administrators should expect mixed behavior across a fleet. One test laptop may show the new taskbar and Start settings immediately, while another fully updated device remains unchanged. This is not necessarily a failed installation. It is Microsoft’s staged rollout model at work.
For managed environments, the safest approach is to treat KB5120998 as a pilot candidate. Install it first on a small set of representative Windows 11 devices, confirm application compatibility, validate help desk documentation, and only then decide whether to broaden availability. Enthusiasts can move faster, but production systems should still have a rollback plan.
About manual enablement with ViVeTool
Windows Latest describes a ViVeTool-based method for enabling the feature flags early. The reported commands include a master feature ID, vivetool /enable /id:61161244, plus an additional command using IDs 62353331,62762248,61754985. This works by toggling feature switches that are already included in the installed Windows build; it is not the same as installing unofficial system files.
Even so, IT departments should be careful. ViVeTool is useful for lab validation and enthusiast testing, but it bypasses the pace Microsoft selected for the rollout. Feature IDs can change, interactions can differ by build, and support teams may not want undocumented switches enabled across business devices. If you use this method, limit it to test hardware or clearly identified pilot users, document what was changed, and keep the matching disable command available.
A practical compromise is to use ViVeTool only to evaluate documentation, screenshots, and training needs before Microsoft enables the same features broadly. That gives administrators an early look without turning a staged consumer rollout into an unmanaged enterprise change.
What to check after enabling the features
After installing the update or enabling the flags, review taskbar behavior first. Windows Latest notes that some combinations are still limited: the smaller taskbar variant and Search box behavior may depend on whether the taskbar remains at the top or bottom. If you move the taskbar to the side, verify pinned apps, notification area behavior, flyouts, tooltips, and multi-monitor layouts before calling the configuration stable.
Next, test Start menu settings on both large and small displays. The most useful configuration for a desktop workstation may not be ideal for a 13-inch laptop. Users who frequently present or record their screens should also look for privacy-related options such as hiding profile details from Start.
Finally, evaluate Search with web and Store suggestions disabled. In a business context, this cleaner mode can reduce accidental web launches and keep user intent local. However, some users may rely on web search from the taskbar, so communicate the difference before standardizing the setting.
Bottom line
KB5120998 looks like one of the more user-visible Windows 11 preview updates in recent memory because it addresses daily workflow friction rather than only background fixes. A movable taskbar, a less oversized Start menu, and a local-first Search box are all practical quality-of-life improvements.
For enthusiasts, the update is worth testing as long as you understand the staged rollout and the risks of manually enabling hidden flags. For IT teams, the better path is measured validation: pilot the optional update, document the new controls, and wait for broader rollout before making it a standard configuration.
Source: Windows Latest source