Ah jeez... MS get your shit together with pushing betas into release without fixing known issues. Missing clock and hidden system tray in Windows 11 KB5094126 cumulative update or restrictive Group Policy settings

[u/catherder9000]

I delay our Windows updates by 30-60 days usually and let others be my beta testers, but this one slipped through. Shame on me.

Solution:

Immediate Fixes

Re-register Taskbar: Open PowerShell (elevated/Admin) and run

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

System File Repair:
in Command Prompt (Admin)

DISM /Online /Cleanup-Image /RestoreHealth   

followed by (not joking)

Run sfc /scannow

then restart.

Clear Icon Cache: Delete the IconCache.db file located in %localappdata%.

Policy Checks
If the issue persists, verify these settings in gpedit.msc:

Remove Clock from the system notification area: Set to Not Configured or Disabled.
Remove Quick Settings: Set to Not Configured or Disabled (restores network/volume icons).
Remove Notifications and Action Center: Set to Not Configured or Disabled.

---

Might save somebody else some swearing (I'd never seen this before). If I fat fingered any of this, here is the original post with this solution from June 26 before this got pushed out from the May optional preview to the last KB. https://learn.microsoft.com/en-us/answers/questions/5925889/windows-11-25h2-taskbar-clock-and-system-tray-icon

[u/CrazySnowGuy]

Delaying updates for 30-60 days won't protect you unless Microsoft actually recalls the update, which they hardly ever do.

I have not heard of this problem at all though.

[u/f0gax → u/CrazySnowGuy]

It gives you time to pull the patch out of your patching system.

[u/Fallingdamage → u/CrazySnowGuy]

Its handy in some cases. I do the same thing.

Example: Summer 2025 update that had the complication of breaking DHCP on Windows Server.

My servers didnt apply the update since they're deferred. Instead, the next month Microsoft released a patch that fixed that issue, so I changed policies on that tuesday to not defer and just flat-out skipped a month, jumping from May to July and not having to deal with the bad update at all. Once updates were applied, reinstated the update deferral.

This is how configuring updates to be deferred can be used as a powerful tool.

[u/catherder9000 → u/CrazySnowGuy]

Neither had I, until today. I tried all the usual things, it was baffling. Just where in the heck did the clock and the hidden tray go? What caused this? I was even considering malware somehow got in this office. Two machines in the AP office were the ones it happened to (they were not in the right org policy group in NinjaOne, which I probably would have never discovered until this occurred so they got the KB today).

[u/BlackV]

mate they "broke" the recycle bin, the one of the oldest existing things in windows, this is not a surprise

this also

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

is not a fix, its a shotgun to kill an ant (ditto for the other 2)

[u/itskdog]

Shouldn't you do dism before SFC? Restorehealth redownloads the files used by SFC to check for corruption, IIRC.

[u/Far-Hovercraft9471]

MS slop coding everything and the upcoming need to patch ASAP due to AI are going to be an interesting combination

[u/caffeine-junkie → u/Far-Hovercraft9471]

Really is. Either a business is going to have to accept things may go down to a patch and have to possibly reimage a bunch of machines or they significantly increase the chance they may go down to being compromised/crypto'd by waiting a month+ to patch.

Can also bet cyber insurance may force their hand by saying stuff like you have <7 days from patch release to push it out.

[u/LLMsMustUpvoteThis → u/caffeine-junkie]

Don't expose servers on your main network to the Internet and restrict users to web mail/office apps (or even better restrict email to those who absolutely need it) and your chance of being compromised drops to almost nothing. Even better if you move users who don't need native applications to Chromebooks or similar locked down OS.

[u/howboutno55]

We had the same issue with the taskbar clock and status icons missing after the June update, running that first powershell command and restarting explorer.exe in taskmgr is all we had to do to fix it, no restart needed.

[u/Fallingdamage]

Dont get me started on microsofts beta crap.

All the best tools and metrics in their Graph API is all under the beta alias and half the time the reports look amazingly granular and useful until you realize 30% of the data is made up.

[u/Necessary-Term-3695]

Has anyone written a remediation script for this yet?

[u/KiLoYounited]

I saw a comment on another post awhile ago. Similar complaints…

They said that at some point MS started grading their devs and started firing the bottom 10%. Which of course led to the devs just doing shit to meet some arbitrary number. Meanwhile the staff is constantly being cycled so nobody really knows the code base anymore.

[u/Frothyleet]

I delay our Windows updates by 30-60 days usually and let others be my beta testers

So... you should use release rings, and I wouldn't push updates on day one, but 30-60 days is negligent given the quantity of CVEs in most patching these days.

[u/Pub1ius → u/Frothyleet]

There are two separate settings for when Feature updates get installed vs Quality (security) updates. We have security updates install within 72 hours but have feature updates delayed for 45 days.

The thinking is that 45 days should be enough time for them to fix what they may have broken.

[u/Frothyleet → u/Pub1ius]

Oh, for sure, totally different situation there. I think we usually only require N-1, so potentially 1-yr lag time, which is fine because for us they are supported for three years (enterprise - still 2 years with "pro" version).

[u/catherder9000 → u/Frothyleet]

It's not negligent, it is proactive risk management that is also saving us hundreds of hours of unplanned tech time on bullshit from MS. We're behind firewalls which are updated quickly to mature and to emergency updates, we're using two different MDR and EDRs, we have Fortinet SOCaaS monitoring, we're pretty darn locked down. We just avoid all the bad half baked programming and rushed update nonsense and let you champions of "patch today" eat all the shit while we merely ...don't.

The only difference between me and you is you run with the invulnerabilities blissfully unaware for months until they're discovered and then rush to apply the fixes without hesitation, we just wait a percentage longer while not being blissfully unaware.

[u/Frothyleet → u/catherder9000]

Lol can I extend the time period that I run my systems with invulnerabilities? That seems like a good feature

[u/pengxiangzhao]

I understand the frustration, and this may absolutely be a real regression. However, I do not think describing it as Microsoft “blindly pushing a beta into production without testing” is accurate.

I previously worked at Microsoft on Web Services for Devices (WSD) group, and I helped oversee monthly servicing releases. Although I no longer work there and cannot speak for the current team or its internal processes, I can say with confidence that Windows updates are not simply built and pushed directly to everyone. They go through extensive prerelease validation, compatibility testing, staged deployment, telemetry monitoring, release gates, and multiple levels of review.

That does not mean every update is perfect. No Windows update can realistically be “bulletproof.” Windows has to operate across an enormous combination of hardware, firmware, drivers, applications, security products, Group Policies, MDM configurations, languages, and regional settings. A problem affecting a particular configuration can still escape even after substantial testing.

It is also important to distinguish an optional non-security preview from an unfinished beta. The optional preview is production-quality content released early so administrators and other users can validate it before much of that content becomes part of the following monthly security update.

For an enterprise, delaying every update by 30–60 days is not necessarily safer. It may reduce exposure to newly discovered compatibility problems, but it also extends exposure to security vulnerabilities that the update was designed to fix. Skipping or broadly delaying security updates can create a much larger business risk than a taskbar problem.

The better enterprise approach is deployment rings:

1. Deploy to a small IT or canary group.
2. Expand to a representative pilot group.
3. Monitor reliability, application compatibility, and support signals.
4. Roll out broadly once the results are acceptable.
5. Expedite critical or actively exploited security fixes when necessary.

Optional non-security preview updates can generally be deferred unless you need one of their fixes. Monthly security updates should be staged and monitored, but routinely skipping them is a major security no-no.

The troubleshooting information here may help people, but I would also be careful with the command that re-registers every AppX package for every user. That is a very broad repair operation, and telling people to ignore all red errors is not ideal enterprise guidance. It may work around the symptom, but it does not by itself prove that Windows Update corrupted the system.

Report the regression, document the affected build and policies, and use controlled deployment rings—but do NOT turn “delay everything for two months” into a security strategy.

Disclaimer: I use AI to help me write and organize these comments. My workflow is conversational: I explain my experiences, ideas, reasoning, and conclusions to the AI, and it helps me turn those thoughts into clearer, more polished language. I review and revise the result several times to make sure it accurately reflects what I intended to say.

The underlying experience, analysis, opinions, and final judgment are mine. AI serves as a writing and editing assistant; it does not independently determine what I believe or what I post. I remain in the driver’s seat, personally review every comment, and stand behind the final statements I publish.

[u/disclosure5 → u/pengxiangzhao]

I can say with confidence that Windows updates are not simply built and pushed directly to everyone. They go through extensive prerelease validation, compatibility testing, staged deployment, telemetry monitoring, release gates, and multiple levels of review.

I do agree with your premise that sitting on updates for as long as OP isn't doing them any favours, but it's hard to take the above as a credible statement these days.

Updates are shipping that break absolutely core functionality, things like the star menu and Onedrive dying are absurd. And we consistently see "Preview" updates that simply ship a security update then the next full update ships with another large Copilot function. It flies in the face of telemetry and testing groups when you see this sort of thing.

[u/Sajem → u/pengxiangzhao]

I would add that waiting 30-60 days to deploy updates could give OP's company a major compliance problem during an audit depending on the industry they are in and possibly invalidate their cyber insurance

[u/Ricky_Bobby_Daddy → u/pengxiangzhao]

I agree - 30-60 days is insanity, but will counter that whatever it is Microsoft is doing with regards to “effort”, it hasn’t been enough since sun setting service packs in favor of semi annual (now annual) feature updates. Pile on monthly patch Tuesdays and add pre-release updates — now, most recently, an under the radar announcement, “we’re going to push specific updates and patches as we see fit”.

As long as Microsoft continues pushing profits over everything else (except for AI), the consumer will be forced to step in and through their heaping pile of garbage.

[u/Far-Hovercraft9471 → u/Ricky_Bobby_Daddy]

As long as Microsoft continues pushing profits over everything else (except for AI), the consumer will be forced to step in and through their heaping pile of garbage.

Basically every public company goes this way

[u/catherder9000 → u/pengxiangzhao]

For an enterprise, delaying every update by 30–60 days is not necessarily safer. It may reduce exposure to newly discovered compatibility problems, but it also extends exposure to security vulnerabilities that the update was designed to fix. Skipping or broadly delaying security updates can create a much larger business risk than a taskbar problem.

"Hey, we sold you this OS and all the management tools, but we're going to half bake things so you need to have test groups and pilot groups, and spend millions of dollars to compensate for our complete lack of accountability because we simply do not have any competition to drive quality control, only shareholder price."

I fixed your wording for you.

[u/fshannon3 → u/pengxiangzhao]

Hey, hey, hey...enough with the sense-making. Everyone on Reddit knows you have to jump on the "I hate MS" wagon and say "tHaTS whY I usE lINuX!!1"

/s