Build 23516 – Missing Taskbar Bug

Anonymous
2023-08-04T17:55:32+00:00

Hello Windows Insiders!

Build23516 was released to the Dev Channel this week. in our reviews of incoming feedback, a bug has been logged that we wanted to share insights on. See below for details.

Who: Windows Insiders on Dev Channel Build 23516

What:  Taskbar may be “missing” on boot after installing this build

Why:  (Investigation is underway)

Additional information:

As we have attempted to reproduce this issue, it has proven to be inconsistent.  Many users have not hit this issue, while others have it on some device reboots, but not others.

Workarounds:

There are three possible workarounds possible for this scenario, each detailed below.

  1. If your taskbar is missing, allow the computer to sit idle for 5-6 minutes.  Users have reported hearing an audible ding notification after which time the Taskbar reappears.
  2. Reboot the device.  This has not proven to be a fully reliable workaround, but it has been noted as successful from some users.
  3. Lastly, you may choose to roll back from this build to the prior build.  This bug was not present in the prior Dev Channel build (23511). To roll back your device if the task bar is missing, please follow these steps:
    • Click the lock screen to display the login page.
    • Select the on-screen Power Button in the lower-right corner.
    • Hold the Shift key and **** select Restart.
      • (The device will reboot and enter the Windows Recovery Environment)
    • On the "Choose an option" screen, select Troubleshoot
    • Select Advanced options
    • Select Uninstall updates
    • Select Uninstall latest feature update
      • If your device has BitLocker enabled, you will be prompted for the recovery key. Input the key and click Continue.
    • On the next screen select Uninstall feature update
    • The uninstall process will now begin.

We appreciate your patience as we investigate this issue.  Please share any additional insights you may have either in the Feedback Hub or here in this thread.

Thank you as always,

  • The Windows Insider Team
Windows Insider program | Windows Insider preview | Personalization and accessibility

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

62 answers

Sort by: Oldest
  1. Anonymous
    2023-08-16T01:35:03+00:00

    I don't know if it is just me but after updating to the latest build, the bug disappeared. It is normal again.

    Which latest Build? 23521?

    This thread specifically says 23516, I have not seen this reported in 23521 yet. 😎🤷‍♂️

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2023-08-16T09:38:35+00:00

    Which latest Build? 23521?

    This thread specifically says 23516, I have not seen this reported in 23521 yet. 😎🤷‍♂️

    He said the issue was resolved by upgrading to build 23521. A viable solution to the issue.

    I started having this issue as soon as 23516 update installed. It effected both home and professional. I usually just grumbled and launched Firefox to get my work done, and eventually (once as long as 10 minutes) it would finally decide to show up. I didn't notice if it would come back if I opened file explorer. I didn't stress too much, just figured it was a buggy dev release and the next would resolve the issue. Which it did. :)

    Was this answer helpful?

    0 comments No comments
  4. Paul Chou 1,471 Reputation points
    2023-08-16T09:57:17+00:00

    The solution to the issue is to update to the latest Dev channel build.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-08-16T10:14:21+00:00

    我更新了23521,已经修复了

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments