Microsoft today released Windows 11 Dev channel build 22499 that adds the ability to quickly share open app windows on the taskbar directly with Microsoft Teams calls. Microsoft also announced that based on feedback, the Clock app (from version 11.2110.32.0 and higher) now supports signing in with Microsoft work and school accounts.
Regarding the new taskbar quick share option, it works like this:
When you are in a meeting call through Microsoft Teams, simply hover over the apps running on your taskbar and you will see a new button that allows you to share your window with your meeting attendees. When you are done sharing your content, hover over the window again and click Stop Sharing or choose another window and click Share this Window. If you’re presenting a full screen presentation in PowerPoint, simply move your mouse to the bottom and your taskbar will pop up for you to share or stop sharing the presentation without interruption to your attendees.
As has become the norm for new features, not everyone will see it right away, Microsoft states the following regarding availability of the share tool in the taskbar app preview popups:
We are beginning to roll this experience out to a subset of Windows Insiders with Microsoft Teams for work or school installed and ramp it up over time. This means not everyone will see this right away with their Teams calls. We plan to bring this to Chat from Microsoft Teams (Microsoft Teams for home) later.
Other communications applications can also add this capability to their applications. The capability to share your meeting call applies only to your current meeting call.
Here is the complete list of improvements in this build:
- Based on feedback, we are making keyboard focus visuals in Task View and Alt + Tab a little more prominent, so they’re easier to see.
The build also brings a long list of fixes, which is always welcome. As is the case with every build, the company is promising to bring many of these fixes to the publicly available version of Windows 11, but there is no timeline on when that will happen or which fixes will be included specifically. Here are all the fixes:
[Input]
- Clipboard history should be back up and running properly once you’re on this build.
- Clicking gifs in the emoji panel will now actually insert them into supporting apps, unlike in the previous build.
- Updated the backend dictionaries for several languages – the touch keyboard’s text suggestions and autocorrect should be more accurate now.
- If you change your accent color the accents in the emoji panel should follow suit now, instead of getting stuck with the old color.
- Fixed an IME crash that was happening sometimes for people who had chosen to use the previous version of the Pinyin IME.
- Mitigated an explorer.exe crash that was happening sometimes recently related to touch keyboard usage.
[Windowing]
- Made another fix to address an issue where explorer.exe would crash if you pressed ALT + F4 while ALT + Tab was open.
[Settings]
- Fixed a Settings crash that could happen when trying to check remote sound properties while accessing a PC over Remote Desktop..
[Other]
- Fixed an issue that was causing some clipping / unexpected zoom when going through OOBE on some ultrawide monitors.
- The apostrophe in the error message when your fingerprint isn’t recognized on the login screen should display correctly now.
- When taking a screenshot of a UWP app by pressing the New button in Snipping Tool, Snipping Tool should come into the foreground once the snip is done.
- Fixed an issue that was causing some Insider PCs to bugcheck when coming out of sleep recently, with an error message saying “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED”.
- Fixed a deadlock that could happen related to MediaPlaybackCommandManager, resulting in certain apps not being able to play media sometimes.
- Addressed an issue that was causing reports in Reliability Monitor to unexpectedly be blank with just an empty rectangle when going to see more info.
- Did some work to help address an issue resulting in certain games having some lag that was only noticeable when the window was in focus. As a reminder if needed, please refer to the following documentation for filing actionable game perf feedback.
Here are all the known issues:
[General]
- Users updating from Builds 22000.xxx, or earlier, to newer Dev Channel builds using the latest Dev Channel ISO, may receive the following warning message: The build you are trying to install is Flight Signed. To continue installing, enable flight signing. If you receive this message, press the Enable button, reboot the PC, and retry the update.
- We’re investigating an issue where some PCs are unable to install new builds, or other updates. The PC may report an error code 0x80070002. If you are experiencing this issue, please reboot your PC and try again.
- Some devices may bugcheck with error code 0xc1900101-0x4001c when installing this build. If you hit this, after the device rolls back to the previous build, you may want to pause updates until we release a fix.
[Start]
- In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press WIN + R on the keyboard to launch the Run dialog box, then close it.
[Taskbar]
- The Taskbar will sometimes flicker when switching input methods.
- We’re investigating an issue in this build where the clock in the Taskbar can get stuck and not updated, particularly when accessing the PC via Remote Desktop.
[Windowing]
- Hovering your mouse back and forth between different desktops in Task View will result in the displayed thumbnails and content area unexpectedly shrinking.
[Input]
- We’re working on a fix to address reports from some Insiders that the lights on their keyboards, for example for caps lock, are not working properly after upgrading to the previous build.
[Search]
- After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
[Quick Settings]
- We’re investigating reports from Insiders that the volume and brightness sliders aren’t displaying properly in Quick Settings.
The firm has also made available the SDK preview for this build and NuGet packages for those interested. Build 22499 should be available now for Dev channel users via Windows Update, and Microsoft has also made the ISO available to download, you can grab that here.
Oh and Microsoft also announced that they are beginning to roll out the “Shipped Windows 11” badges to Insiders in Feedback Hub in case you were wondering about that.
Update: On Friday Nov 12, Microsoft released build 22499.1010 that did not add anything new and was just Cumulative Update to test the servicing pipeline. That build contains the same features and fixes as this one.