See a list of known issues that have been resolved for Windows Server 2022 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page. Resolved issuesIssue detailsNovember 2022
Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1. After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected: When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1": While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved. Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected. Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically. Cumulative updates: Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above. Standalone Updates: Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above. Affected platforms:
After installing KB5018485 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN). Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected. Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device. Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. Affected platforms:
October 2022
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 KB5018485. Note: KB5018485 will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install. Affected platforms:
Microsoft has received reports that after installing KB5018421, 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 the out-of-band update KB5020436. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB5020436, search for it in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note KB5020436 is not available from Windows Update and will not install automatically. Affected platforms:
September 2022
IT administrators who utilize Windows Server Update Services (WSUS) might notice that the Windows September 2022 preview update, known as the 'C' release, is listed among the updates available from WSUS. This listing is an error. Preview updates are generally available for manual importing via the Microsoft Update Catalog and Windows Updates. This issue might also affect the installation of the September 2022 Cumulative Update Preview for .NET Framework, which is also generally available via Windows Update and Microsoft Update Catalog. For more information on .NET Framework September 2022 Cumulative Update Preview updates, see the KB articles listed on the .NET blog for the September 2022 Cumulative Update Preview. Home users of Windows are unlikely to experience this issue. WSUS is commonly utilized by technology administrators to deploy Microsoft product updates in managed environments. Workaround: The Windows September 2022 preview release was made available via Microsoft Update Catalog. We recommend IT administrators to use this release channel moving forward. Please note: In environments where WSUS is configured to auto-approve updates and also auto-decline superseded content, the Windows September 2022 Security update may subsequently be auto-declined and auto-expired from the client view. If this occurs, see the guidance for reinstating declined updates. Then run an update synchronization within Microsoft Endpoint Configuration Manager, or update management environments. Environments configured to only take security updates should not reflect these symptoms. Resolution: The Windows September 2022 preview release was removed from WSUS. We recommend IT administrators use the Microsoft Update Catalog to download and install updates in their environments. As always, we recommend the installation of the latest Windows security updates for all devices (the October 2022 security monthly release, KB5018421, or later). Affected platforms:
After installing KB5017316, 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 KB5018421. Installation of KB5018421 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:
Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10. Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:
Workaround: This issue is now resolved in KB5017381 but you should undo the workaround, if it is still being used. You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:
To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:
Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly. Resolution: This issue was resolved in KB5017381. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017381 will not change the "Automatically adjust clock for Daylight Saving Time" setting. Affected platforms:
July 2022
After installing updates released June 14, 2022, or later ( KB5014678), PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to: “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”. Note: Environments which use non-encrypted PSCredential properties will not experience the issue. DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows. Resolution: This issue was resolved in KB5015827. Affected platforms:
June 2022
After installing KB5014021 and later updates, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note: Sites affected by this issue call window.focus. Resolution: This issue was resolved in KB5016693. Affected platforms:
After installing KB5014678, Windows devices might be unable to use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects. Workaround: To mitigate the issue and restore internet access on the host device, you can disable the Wi-Fi hotspot feature. For instructions, please see Use your Windows PC as a mobile hotspot. Resolution: This issue was resolved in KB5014665. Affected platforms:
After installing KB5014678, Windows Servers which are using the Routing and Remote Access Service (RRAS) might be unable to correctly direct internet traffic. Devices which connect to the server might fail to connect to the internet, and servers can lose connection to the internet after a client device connects. Workaround: This issue is resolved in the latest Windows security update. If it's not possible to install the latest Windows updates on an affected server, the issue can be avoided by temporarily disabling the NAT feature on the RRAS server. For steps and guidance on this, note the ability to uncheck the "Enable NAT on this interface" option described on step 7 of the article Enable and Configure NAT. Resolution: This issue was resolved in KB5014665, and updates released June 23, 2022 or later. We recommend you install the latest security update for your device. Affected platforms:
|
Which of the following tasks are typically performed following a windows server 2022 installation?
Postagens relacionadas
direito autoral © 2024 aprendervalor Inc.
