KB5101650 Missing Clock? Fix Windows 11 Tray Policies

If the clock, notification area, or network/volume/battery cluster disappeared after installing Windows 11 update KB5101650, first document the symptom and audit the effective user policy in the affected user’s session. This service procedure covers Windows 11 versions 24H2 and 25H2 on locally managed, domain-managed, and MDM-managed PCs; as of July 18, 2026, Microsoft had not classified a missing tray as a known KB5101650 issue.
Similar-looking clock and system-tray symptoms can have different causes, so use the following decision tree to separate a configured restriction from a Windows shell or update interaction.

What Microsoft currently acknowledges​

Microsoft’s Windows 11, version 24H2 release-health page documents the Dell/Intel compatibility hold involving KB5101650. As of July 18, 2026, the page did not list a missing clock, missing notification area, or vanished network/volume/battery cluster as a known issue for the update.
That leaves three cases to test:

1. A documented policy is hiding the component.
2. A managed configuration is interacting with the updated system.
3. The Windows shell is not displaying the component correctly.

Gather the following evidence once, before changing policy or uninstalling anything:

• Whether KB5101650 is installed
• Windows version and OS build
• Affected user
• Hardware model
• Exact missing elements
• Effective-policy report
• Assigned GPO or MDM profile, if identified
• Result after an approved policy change, Explorer restart, or rollback

For multiple PCs, note which are affected and whether each has KB5101650. This is the point at which to compare affected and unaffected systems; repeated cautions about correlation are unnecessary later in the procedure.

Start with the exact symptom​

Use the visible symptom to choose the first policy to inspect.

Symptom	Inspect first
Clock alone is missing	Remove Clock from the system notification area
The notification area is hidden	Hide the notification area
Quick Settings cannot be opened from the taskbar	Remove Quick Settings
Only network, volume, or battery is missing	The corresponding removal policy, where supported
Quick Settings opens with a restricted layout	The separate Simplify Quick Settings policy
Entire taskbar is blank, frozen, or repeatedly reloads	Windows Explorer and shell troubleshooting
Only one user is affected	Effective user policy and that user’s assigned configuration
Multiple users are affected	Shared configuration and Windows shell troubleshooting

Microsoft commonly uses notification area for the tray region in policy names and descriptions.

Confirm the update and record the build​

1. Press Windows key + R.
2. Enter:

winver

1. Select OK.
2. Record the Windows version and OS build.
3. Open Settings > Windows Update > Update history.
4. Expand Quality Updates.
5. Confirm whether KB5101650 is installed.
6. Record its installation date.

Also record the computer name, Windows edition, hardware model, affected user, and precise symptom. For example, distinguish “clock missing” from “clock present, but clicking it does nothing.”

Generate the effective policy report as the affected user​

The report must be generated in the affected user’s sign-in session. Do not launch Command Prompt with another administrator’s credentials: doing so can make %USERPROFILE% and the reported user context refer to the administrator rather than the affected user.
For the affected user’s normal user-policy results, elevation is not required:

1. Sign in as the affected user.
2. Open Start.
3. Type cmd.
4. Open Command Prompt normally.
5. Run:

gpresult /h "%USERPROFILE%\Desktop\gp-report.html" /scope user

1. Wait for confirmation that the report was saved.
2. Open gp-report.html from the affected user’s desktop.
3. Search for:

• Remove Clock from the system notification area
• Hide the notification area
• Remove Quick Settings
• Remove the networking icon
• Remove the volume control icon
• Remove the battery meter

1. Also search for clock, notification area, Quick Settings, network, volume, and battery.
2. Record any displayed policy source information.

Elevation is needed when an authorized administrator must collect computer-scope information that the standard user cannot access. In that case, first preserve the affected user’s non-elevated user report. Then, from an elevated Command Prompt, generate a separate computer report:
gpresult /h "%PUBLIC%\Desktop\gp-computer-report.html" /scope computer
If alternate administrator credentials are required for elevation, do not treat that elevated process as a report of the affected user’s identity.

Optional RSoP check​

Resultant Set of Policy can provide another view where it is available:

1. While signed in as the affected user, press Windows key + R.
2. Enter:

rsop.msc

1. Select OK.
2. Allow the console to gather data.
3. Review the displayed user settings for the Start menu, taskbar, notification area, clock, and Quick Settings.
4. Compare the result with the HTML report.

Inspect the documented user policies​

Where Local Group Policy Editor is available:

1. Press Windows key + R.
2. Enter:

gpedit.msc

1. Select OK.
2. Go to:

User Configuration > Administrative Templates > Start Menu and Taskbar

1. Locate the policies associated with the observed symptom.
2. Record whether each policy is Enabled, Disabled, or Not Configured.

For the documented clock policy, enabling Remove Clock from the system notification area removes the clock from the system notification area. Disabling it or leaving it not configured allows the clock to appear.
For the documented notification-area policy, enabling Hide the notification area hides that area, including its notification icons. Disabling it or leaving it not configured allows the notification area to be shown.
Microsoft’s Start policy reference provides the supported scope, editions, and behavior for Start and taskbar-related policy settings. Use the entry for each policy rather than assuming that similarly named clock, icon, and Quick Settings controls have identical requirements.
Treat the names as diagnostic signposts:

• For a missing clock, inspect Remove Clock from the system notification area.
• For a hidden tray region, inspect Hide the notification area.
• For a missing Quick Settings entry point, inspect Remove Quick Settings.
• For one missing status indicator, inspect the corresponding policy if it is present and supported on the affected Windows edition.

A setting shown as Not Configured in Local Group Policy Editor means only that the local policy is not configured there. Use the effective-policy report and the organization’s management console to determine the applied configuration.

Simplify Quick Settings is a separate control​

Simplify Quick Settings is a separate GPO/CSP-controlled setting. Consider it only when Quick Settings still opens but presents a restricted layout. Do not use it to explain a missing clock or an entirely absent notification area unless the organization’s policy records identify that setting.

Correct an identified policy through management​

If the effective report identifies a configured restriction, determine whether it is intentional before changing it.
For a domain-managed PC:

1. Give the effective-policy report to the Group Policy administrator.
2. Identify the GPO shown as supplying the setting.
3. Confirm the intended configuration for the affected user.
4. Apply any approved correction through the organization’s Group Policy management system.
5. Limit the initial change to designated test users or systems.
6. Verify the result on an affected test PC.

For an MDM-managed PC:

1. Open the organization’s device-management platform.
2. Find the policy or profile assigned to the affected user or device.
3. Review the taskbar, Start, Quick Settings, and user-interface restrictions.
4. Confirm whether the restriction is intended.
5. Apply an approved correction to a limited test assignment.
6. Verify the effective result on the test PC.

Do not try to override an organizational setting through an endpoint registry edit or an undocumented package change.

Refresh policy and verify every component​

After an approved policy correction:

1. Sign in as the affected user.
2. Open Command Prompt.
3. Run:

gpupdate /force

1. Wait for processing to finish.
2. Sign out and sign back in.
3. Restart Windows if the interface has not refreshed.
4. Verify each item separately:

• Clock
• Notification-area application icons
• Network indicator
• Volume indicator
• Battery indicator, where applicable
• Quick Settings entry point
• Quick Settings contents

1. Generate a new user-scope report:

gpresult /h "%USERPROFILE%\Desktop\gp-report-after.html" /scope user

1. Retain both reports and record the result.

If the corrected policy is reflected in the new report and the missing component returns, document the incident as a configuration result or configuration interaction.

Use a second account to narrow the scope​

If organizational policy permits, test another authorized account on the same PC:

1. Sign out of the affected account.
2. Sign in with the comparison account.
3. Check the clock, notification area, network, volume, battery, and Quick Settings.
4. Generate that account’s user-scope gpresult report.
5. Record differences between the two effective reports.

If the symptom occurs for one account but not the other, focus on their effective user configurations. If both accounts have the symptom, continue with shell troubleshooting and review shared management settings.
Do not create an unmanaged local administrator solely for this test unless the organization authorizes it.

Test Windows Explorer​

If the effective policy does not account for the symptom, restart Windows Explorer and observe the result:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Find Windows Explorer under Processes.
3. Right-click Windows Explorer.
4. Select Restart.
5. Wait for the desktop and taskbar to reload.
6. Test all previously missing components.
7. Record whether the components returned and whether they remained available.

Also record the presence of relevant taskbar customization, shell replacement, kiosk, desktop-management, or endpoint-hardening software. Do not disable security or management software without authorization.
An Explorer restart result is evidence for the escalation packet; by itself, it does not identify the underlying cause.

Perform an approved rollback test​

If the organization approves uninstalling KB5101650 on a test device, use the supported Settings route:

1. Preserve the current OS build and effective-policy reports.
2. Open Settings.
3. Select Windows Update.
4. Select Update history.
5. Select Uninstall updates.
6. Locate KB5101650.
7. Select Uninstall.
8. Restart when prompted.
9. Run winver and record the resulting build.
10. Verify every previously missing tray component.
11. Generate another affected-user policy report.
12. Record whether the symptom changed.

Removing an update removes the fixes delivered by that update, so the decision and test scope should follow the organization’s servicing and security procedures.
If KB5101650 is not offered for removal, do not use undocumented package manipulation. Escalate through the organization’s Windows servicing process or Microsoft support.

Build a compact escalation packet​

Provide these fields to the desktop, policy, servicing, or Microsoft support team:

Field	Required detail
Update	KB5101650 and installation date
Windows	Edition, version, and full OS build
Affected user	User identifier and whether other users reproduce it
Policy result	Relevant entries from the before-and-after gpresult reports
Managed assignment	Assigned MDM profile or GPO identified in management records
Hardware	Manufacturer and model
Missing elements	Clock, notification area, network, volume, battery, Quick Settings, or entire taskbar
Explorer test	Whether restart changed the symptom and for how long
Rollback result	Before/after build and whether each element returned
Reproduction	Exact sign-in and verification steps

Include screenshots where permitted, but do not substitute screenshots for build numbers and policy reports.

Frequently Asked Questions​

Does a missing clock prove that KB5101650 broke Explorer?​

No. As of July 18, 2026, Microsoft had not listed a missing clock or notification area as a known KB5101650 issue. Check the documented user policies and collect shell and rollback results before classifying the incident.

Should administrators pause KB5101650 everywhere?​

Use the organization’s servicing process and the evidence from representative systems. Check Microsoft’s current release-health page, effective policy, affected hardware, and controlled test results before making a deployment-wide decision.

Why should gpresult be run without elevation first?​

The affected user’s standard session provides the correct user identity for a user-scope report. Running an elevated Command Prompt with alternate administrator credentials can report the administrator’s context instead. Elevate separately only when computer-scope access requires it.

Where are the clock and notification-area policies?​

Open Local Group Policy Editor and go to:
User Configuration > Administrative Templates > Start Menu and Taskbar
The relevant documented settings include Remove Clock from the system notification area and Hide the notification area.

What evidence should be retained?​

Keep the KB number, Windows version and build, affected user, before-and-after policy reports, assigned MDM or GPO profile, hardware model, exact missing elements, Explorer restart result, and before-and-after rollback result.

---

References​

1. Primary source: learn.microsoft.com
   
   

   List of the Policy Settings To Configure the Windows Taskbar | Microsoft Learn

   Learn about the CSP and GPO policy settings to configure the Windows taskbar.

   learn.microsoft.com
2. Independent coverage: support.microsoft.com
   
   

   KB5017130: Managing Windows 11 “System requirements not met” message in your organization | Microsoft Support

   KB5017130: Managing Windows 11 “System requirements not met” message in your organization

   support.microsoft.com
3. Primary source: WindowsForum
   
   

   Windows 10 Clock Update: Missing Seconds and Windows 11's Reintroduction Effort | Windows Forum

   In a recent update to Windows 10, users have noticed a subtle yet significant change: the removal of the clock displaying seconds in the Calendar flyout...

   windowsforum.com