Windows 11 Build 22000.194 is now rolling out to the testers who are in the Windows Insiders Beta Channel. As the Beta channel is in its final stage of development, targeting the release, it adds some minor changes and improvements.
The build comes as a cumulative update (KB5005635) and adds the TPM requirement for Virtual Machines (VM). That means you will be blocked from updating to the latest version of Windows 11 if your VM doesn't support TPM.
With the release of Windows 11 Build 22000.194, Microsoft now adds the TPM (Trusted Platform Module) Requirement for everyone. Going forward, you will no longer be able to install Windows 11 on virtual machines without TPM 2.0.
So, the VMs that currently doesn't have TPM support won't get the new Windows 11 cumulative updates.
If you are using Hyper-V, Microsoft suggests you create your VMs as a Generation 2 VM in order to run Windows 11 on those virtual devices. Running Windows 11 in VMs in other virtualization products from vendors such as VMware and Oracle will continue to work as long as the hardware requirements are met
, says Microsoft.
Microsoft adds the following new improvements and fixes to the latest Windows 11 Build 22000.194 (KB5005635), rolling out to the Windows Insiders in the Beta Channel:
- 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.
- Mitigated an issue that was resulting in subtitles not appearing when expected in certain apps, particularly Japanese language subtitles.
- 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.
- Fixed a crash with certain connected devices that could result in not being able to use Bluetooth.
- Fixed an issue that was causing certain PCs to bugcheck during modern standby.
- 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.
The latest cumulative update (KB5005635) still has few known issues detailed below:
- 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.
- 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.
- The Taskbar will sometimes flicker when switching input methods.
- 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).
- 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.
Thank you for visiting our website!
We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.
We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.