Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Windows 11, version 22H2 known issues and notifications
In this articleFind information on known issues and the status of the rollout for Windows 11, version 22H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter. The Windows release health hub is always evolving. Take our short survey and let us know how we can improve. Current status as of October 4, 2022 (PT) We are entering a new phase of the rollout for Windows 11, version 22H2 and we are increasing its availability to all who check for updates on eligible Windows devices. Note that, if we detect that your device might have an issue, such as an application incompatibility, we might put a safeguard hold in place and not offer the update until that issue is resolved. Information regarding safeguard holds is available below on this page. Users who are interested in experiencing the latest feature update can choose to do so by opening Windows Update Settings and selecting Check for updates. If your device is ready, you will see the option to Download and install. For more information on this update experience, watch this video. Known issuesThis table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Issue detailsNovember 2022Lower than expected performance in some games
Some games and apps might experience lower than expected performance or stuttering on Windows 11, version 22H2. Affected games and apps are inadvertently enabling GPU performance debugging features not meant to be used by consumers. To safeguard your upgrade experience, we have applied a compatibility hold on devices affected by this issue from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard IDs are 41766570 and 41990091. Workaround: If you are already on Windows 11, version 22H2 and are experiencing this issue, you might be able to resolve it by updating your games and gaming related apps to the latest version available. If you are unsure how to update the games and apps you have installed, you will need to consult the developer of those games and apps but most will update automatically through the store they were purchased from or directly when opening them. Next steps: We are working on a resolution and will provide an update in an upcoming release. Note: We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. Affected platforms:
Audio might be out of Sync when capturing video via Xbox Game Bar
The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay to a video file. You are more likely to encounter this issue when using the "Record last 30 seconds" feature when “Record in the background while I’m playing game” is enabled in Xbox Game Bar. Developer Note: Apps which capture or process video files using the same underlying Windows libraries or APIs as Xbox Game Bar might also be affected by this issue. To safeguard your upgrade experience, we have applied a compatibility hold on devices which have previously used the capture feature in the Xbox Game Bar app from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41584256. Resolution: This issue was resolved in KB5018496. If you have already upgraded to Windows 11, version 22H2, installing KB5018496 will resolve this issue. Note: KB5018496 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. The safeguard hold is estimated to be removed in mid-November 2022. Note: We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. Affected platforms:
October 2022Domain join processes may fail with error "0xaac (2732)"
Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy." This issue originates with the October 2022 security updates ( KB5018427) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. Home users of Windows are unlikely to experience this issue. Next steps: Please see KB5020276 to understand the designed behavior. We have added insights to this KB, and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated once those changes have released. Affected platforms:
SSL/TLS handshake might fail
Microsoft has received reports that after installing KB5018427, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures. Note for developers: Affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, your app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails. If you are experiencing issues, please use feedback hub to file a report following the below steps:
For additional information, see Send feedback to Microsoft with the Feedback Hub app. Resolution: This issue was resolved in KB5018496. Note: KB5018496 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. Affected platforms:
Possible issues caused by Daylight Savings Time change in Jordan
On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Starting at 12:00 a.m. Friday, October 28, 2022, the official time will not advance by an hour and will permanently shift to the UTC + 3 time zone. The impact of this change is as follows:
Symptoms if no update is installed and the workaround is not used on devices in the Jordan time zone on October 28, 2022 or later:
Workaround: You can mitigate this issue on devices in Jordan by doing either of the following on October 28, 2022, if an update is not available to resolve this issue for your version of Windows:
Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Jordan. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if done incorrectly. Resolution: This issue was resolved in KB5018496. Note: KB5018496 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. Affected platforms:
Provisioning packages might not work as expected
Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note: Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue. Workaround: If you can provision the Windows device before upgrading to Windows 11, version 22H2, this will prevent the issue. Next steps: We are presently investigating and will provide an update in an upcoming release. Affected platforms:
September 2022Some installed printers might only allow default settings
Microsoft has found an issue when an installed printer uses Microsoft IPP Class Driver or Universal Print Class Driver and is installed on a Windows device with connectivity issues to the printer. Windows needs connectivity to the printer to identify all the features of the printer. Without connectivity, the printer is set up with default settings and in some scenarios might not get updated once connectivity to the printer is restored. You might be affected by this issue if your printer is unable to use printer specific features such as color, two-sided/duplex printing, paper size or type settings, or resolutions higher than 300x300dpi. Currently, installed printers in this state will carry this issue forward when upgraded to Windows 11, version 22H2. To safeguard your upgrade experience, we have applied a compatibility hold on Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver from being offered Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41332279. Workaround: If you have an affected installed printer, you can use the below workarounds or wait for your device to be mitigated automatically. A troubleshooter has been released which will automatically download and resolve this issue on affected devices. Restarting your device and checking for updates might help the troubleshooter apply sooner. For more information, see keeping your device running smoothly with recommended troubleshooting. To mitigate the safeguard manually and allow your Windows device to upgrade to Windows 11, version 22H2, you can remove or remove and reinstall any printers using Microsoft IPP Class Driver or Universal Print Class Driver which you have installed. Once you have removed any affected installed printers, you should be able to upgrade to Windows 11, version 22H2. For instructions on how to remove and reinstall printers, please see Download printer drivers in Windows. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help it to offer sooner. Next steps: We are working on a resolution and estimate the safeguard will be removed in mid-November. Important Notes:
Note We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. Affected platforms:
Copying files/shortcuts using Group Policy Preferences might not work as expected
After installing , file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings in Group Policy Editor. Workaround: To mitigate this issue, you can do ONE of the following:
Resolution: This issue was resolved in KB5018427. Installation of KB5018427 prevents and resolves this issue but if any workaround was used to mitigate this issue, it will need to be changed back to your original configuration. Affected platforms:
August 2022Update might fail to install and you might receive a 0x800f0922 error
When attempting to install , it might fail to install, and you might receive an error 0x800f0922. Note: This issue only affects the Security update for Secure Boot DBX () and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022. Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install . Next steps: We are presently investigating and will provide an update in an upcoming release. Affected platforms:
November 2021Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11. Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. The affected driver will be named Intel® Smart Sound Technology (Intel® SST) Audio Controller under System Devices in Device Manager and have the file name IntcAudioBus.sys and a file version of 10.29.0.5152 or 10.30.0.5152. Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue. To safeguard your upgrade experience, we have applied a compatibility hold on devices with affected Intel SST drivers from being offered Windows 11, version 22H2 or Windows 11, version 21H2. If your organization is using Update Compliance, the safeguard IDs are:
Workaround: To mitigate the safeguard, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. This issue is resolved by updating the Intel® Smart Sound Technology drivers to a version 10.30.00.5714 and later or 10.29.00.5714 and later. Important: Later versions refer to just the last part of the version number. For addressing this issue, 10.30.x versions are not newer than 10.29.x versions. Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Next Steps: If you encounter this safeguard hold and an updated driver is not yet available, you will need to contact your device manufacturer (OEM) for more information. Note We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. Affected platforms:
Which of the following wireless security protocols has been discouraged?WEP is an older standard and is not recommended because of its vulnerabilities. WPA was designed as an interim replacement for WEP, and WPA2 was introduced as the official standard that offers the strongest security of the three.
Which of the following is the most secure security protocol for wireless networks?When choosing from among WEP, WPA, WPA2 and WPA3 wireless security protocols, experts agree WPA3 is best for Wi-Fi security. As the most up-to-date wireless encryption protocol, WPA3 is the most secure choice.
Which of the following wireless technologies enables the identification and tracking of tags attached to objects?RFID technology is the wireless use of electromagnetic fields to transfer data for the purposes of automatically identifying and tracking tags attached to objects.
Which of the following is a wireless security best practice?Four Best Practices for WiFi Security. Choose a Wise SSID Name. Make sure that your SSID doesn't call attention to your organization. ... . Separate Your Private Network from Your Guest Network. ... . Uniquely Connect Users to Your Wireless Network. ... . Per User (or Group) Network Segmentation with VLANs.. |
Which of the following wireless technologies is not recommended and should not be used due to its known vulnerabilities?
zusammenhängende Posts
Urheberrechte © © 2024 toptenid.com Inc.
