no Windows startup sound after the latest 26300 series build

Question

no Windows startup sound after the latest 26300 series build

Paul Chou 1,456

hi all:

Anyone facing an issue where there is no Windows startup sound after the latest 26300 series build? Also, I had the new Windows 11 Account Control flyout, but also after the latest update, it is gone. No mention that Microsoft removed it.

0 comments

1 answer

Your answer

Answer 1

Alex-L 10,600 Microsoft External Staff Moderator

Hi Paul Chou

I haven't seen any official documentation indicating that the Windows startup sound or the new Windows 11 UAC (Account Control) flyout was intentionally removed from the 26300-series builds. If the changes appeared immediately after updating, they could be a regression, a feature rollback, or a controlled rollout change that was not mentioned in the release notes.

A few questions:

What exact build number are you on now?
Which Insider channel are you using?
Is Play Windows Startup sound still enabled in Control Panel > Sound > Sounds?
Are UAC prompts still appearing, but with the old design, or are they not appearing at all?
Did these changes occur immediately after installing the latest build?

As this is a public forum, no one here have access to any product roadmap to confirm this. If other Insider users upon seeing/finding this post can reproduce the behavior, please consider submitting a report in Feedback Hub (Win + F) and sharing the feedback link here to possibly help determine whether this is a build-specific issue.

Paul Chou 1,456 Reputation points

2026-08-03T10:09:52.31+00:00

The sound issue is gone. I managed to go to the sound settings and click on no sound. Restart Windows and went back and turned on the sound. Restarted Windows again and the sound is back. The account flyout issue is still there. I am at the 26300.9032 build. I think the account flyout occured after applying the new build.
Alex-L 10,600 Reputation points Microsoft External Staff Moderator

2026-08-04T14:34:24.53+00:00

Hi Paul Chou

I'm glad to hear that one of them is now resolved. For the other one, it's worth taking the time sharing the feedback with the corresponding team so that they would be looked at sooner.