[ad_1]
Today, Microsoft is releasing Windows 11 build 22000.194 to the Beta channel. First of all, there’s not much that’s new. Windows 11 is launching on October 5; it’s safe to say that it’s feature-complete. One thing that you’ll find, however, is a bunch of Windows 11 app updates.
These include Snipping Tool, Calculator, and Clock with Focus Sessions. All of these have already been available in the Dev channel for a little while now. But if you’re in the Beta channel, you’ll start to see them show up.
Probably the most notable of them is Clock with Focus Sessions. The whole idea is that you can set times to focus, link it to your Spotify, and it even integrates with Microsoft To Do. The new Snipping Tool is really more of a UX overhaul, not so much offering a bunch of new features over its legacy predecessor.
Of course, Windows 11 build 22000.194 also has a whole bunch of fixes and known issues. Here’s what got fixed:
Windows 11 build 22000.194 Fixes
- Addressed an issue where if you enable then disable a contrast theme, it would lead to artifacts in title bars, in some cases making the minimize/maximize/close buttons hard to see and use.
- Fixed a crash with certain connected devices that could result in not being able to use Bluetooth.
- Mitigated an issue that was resulting in subtitles not appearing when expected in certain apps, particularly Japanese language subtitles.
- Fixed an issue that was causing certain PCs to bugcheck during modern standby.
- Mitigated an issue when typing with certain 3rd party IMEs into the search box in Settings that could result in the candidate window being rendered elsewhere on-screen (not attached to the search box) and/or characters inserted into the search box not displaying.
- We fixed an issue that causes PowerShell to create an infinite number of child directories. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding.
- This build includes a change that aligns the enforcement of the Windows 11 system requirements on Virtual Machines (VMs) to be the same as it is for physical PCs. Previously created VMs running Insider Preview builds may not update to the latest preview builds. In Hyper-V, VMs need to be created as a Generation 2 VM. For more details on the Windows 11 system requirements – see this blog post here.
Here’s what’s still broken:
Windows 11 build 22000.194 Known Issues
[General]
- We’re investigating reports from Insiders in the Beta Channel where after upgrading to Windows 11, they are not seeing the new Taskbar and the Start menu doesn’t work. To workaround this if you are impacted, please try going to Windows Update > Update history, uninstalling the latest cumulative update for Windows, and the reinstall it by checking for updates.
- We’re working on a fix for an issue that is causing some Surface Pro X’s to bugcheck with a WHEA_UNCORRECTABLE_ERROR.
[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.
- System and Windows Terminal is missing when right-clicking on the Start button (WIN + X).
[Taskbar]
- The Taskbar will sometimes flicker when switching input methods.
[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.
- Search panel might appear as black and not display any content below the search box.
[Widgets]
- The widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
- Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.
[Microsoft Store]
- We continue to work to improve search relevance in the Store.
[Windows Sandbox]
- Within Windows Sandbox, the language input switcher does not launch after clicking the switcher icon on the Taskbar. As a workaround, users can switch their input language via any of the following hardware keyboard shortcuts: Alt + Shift, Ctrl + Shift, or Win + Space (the third option is available only if Sandbox is full-screened).
- Within Windows Sandbox, the IME context menu does not launch after clicking the IME icon in the Taskbar. As workarounds, users can access the functionalities of the IME context menu with either of following methods:
- Accessing the IME settings via Settings > Time & language > Language & region > (e.g., Japanese) three dots > Language options > (e.g., Microsoft IME) three dots > Keyboard options.
- Optionally, you may also enable the IME toolbar, an alternative UI, to quickly invoke specific IME functions. Continuing from above, navigate to Keyboard options > Appearance > Use IME toolbar.
- Using the unique set of hardware keyboard shortcuts associated with each IME-supported language. (See: Japanese IME Shortcuts, Traditional Chinese IME Shortcuts).
- Accessing the IME settings via Settings > Time & language > Language & region > (e.g., Japanese) three dots > Language options > (e.g., Microsoft IME) three dots > Keyboard options.
Microsoft also added the requirement for TPM on virtual machines, something that we reported on earlier today. In fact, VMs now have the same requirements as bare metal hardware.
As always, you can get today’s build via Windows Update, as long as you’re on the Beta channel. If you’re not, you can go to the Windows Insider Program tab in Settings to get started.
[ad_2]
Source link