Microsoft、Copilotのバグのため一部のPCでのWindows 11バージョン23H2の展開を停止

重要なポイント

• Microsoft has confirmed an issue with Copilot on multi-monitor setups in the latest preview build, causing desktop icons to move unexpectedly and decrease productivity.
• Compatibility hold applied to PCs with multi-monitor setups, restricting access to Windows 11 version 23H2.
• Microsoft is working on a fix for the bug, but no timeline has been provided yet.

Following the release of some Windows 11 features in advance back in September, Microsoft began rolling out version 23H2 of its latest operating system almost a month ago. これらのリリースの重要なコンポーネントの1つは副操縦士です。レドモンドの技術会社は improving further そしてまた making available in Windows 10. Sometimes, new versions of Windows also break existing capabilities - as we learned a few days ago - and now, Microsoft has confirmed another issue in the latest preview build.

On its Windows release health dashboard, Microsoft has

了解しました that preview OS build 19045.3758 - which was rolled out yesterday - causes problems when using Copilot in multi-monitor configurations. Desktop icons may move unexpectedly across monitors and become misaligned, which can lead to a decrease in productivity. Since this is a fairly annoying bug, Microsoft has decided to restrict Copilot access to PCs which have been used in multi-monitor setups before and has also withheld the availability of Windows 11 version 23H2 on such machines.

This has been done by applying a compatibility hold, with IT admins also requested to check against safeguard ID 47615939ビジネスレポートのWindowsアップデートで、使用されているデバイスのコンプライアンスステータスを確認するために 組織。 In addition, Microsoft has recommended users not to manually update to Windows 11 version 23H2 on affected devices through the Media Creation Tool (MCT) or 他のメカニズム, until the compatibility hold is in effect.

Affected client versions of Windows include Windows 11 version 22H2 and 23H2, along with Windows 10 version 23H2. Microsoft has assured users that it is working on a fix that will be offered in an "upcoming release", but no tentative timelines have been offered yet. It is also important to note that this bug is present in a preview build, so there's a chance that it will be resolved before December's Patch Tuesday release.