Windows 11 known issues and notifications

Find information on known issues and the status of the rollout for Windows 11. 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.

Current status as of October 4, 2021 (PT)

Windows 11 is available for new devices pre-loaded with Windows 11, and eligible new Windows 10 devices.
The Windows 11 upgrade will be offered using a phased rollout which targets eligible new devices first. Availability will be increased over time.
If you are using Windows 10, you can determine if your device is eligible for the upgrade using the PC Health Check app or checking Windows 11 specs, features, and computer requirements. If you have an eligible device, open Windows Update Settings and select Check for updates. Once the upgrade is ready for your device, you will see the option to download and install.
We expect all eligible Windows 10 devices to be offered the upgrade by mid-2022.
For more information on the Windows 11 upgrade experience, watch this video.

    Known issues

    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    Installation of printers might fail when attempted over some network connections
    This issue has been observed in devices which access printers via a print server using HTTP connections
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Custom printing properties might not be correctly provided to print server clients
    This issue will not cause printing operations to fail, but clients might print with default settings only
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Installation of printers via Internet Printing Protocol (IPP) might not succeed
    Affects organizations that share an IPP printer using printer connections
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Receiving a prompt for administrative credentials every time you attempt to print
    This issue affects devices in environments in which the print server and print client are in different times zones.
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Compatibility issues with apps using some non-ASCII characters in their registry keys
    Affected apps might be unable to open and might cause other issues or errors in Windows.
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Some applications on devices that have AMD Ryzen processors might drop performance
    A L3 cache latency issue was observed on devices with AMD Ryzen processors after upgrading to Windows 11
    N/A

    Resolved
    KB5006746
    2021-10-21
    10:00 PT
    Compatibility issues with Intel “Killer” and "SmartByte" networking software
    Internet speeds might be slower than expected on affected devices.
    N/A

    Resolved
    KB5006674
    2021-10-12
    10:00 PT
    Compatibility issues have been found between Oracle VirtualBox and Windows 11
    You might be unable to start Virtual machines (VMs) and you might receive an error.
    N/A

    Confirmed
    2021-10-06
    17:26 PT

    Issue details

    October 2021

    Installation of printers might fail when attempted over some network connections

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-13, 12:34 PT
    Devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers.

    This issue has been observed in devices which access printers via a print server, using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download.

    Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Only the automatic download and installation processes are impacted by this issue.

    Resolution: This issue has been resolved in KB5006746.

    Affected platforms:
    • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

    Custom printing properties might not be correctly provided to print server clients

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-13, 12:28 PT
    Printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only.

    This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Servers which use default print settings and have no custom settings to provide to clients are unaffected.

    Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings.

    Resolution: This issue has been resolved in KB5006746

    Affected platforms:
    • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11, version 21H2
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2

    Installation of printers via Internet Printing Protocol (IPP) might not succeed

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-13, 12:32 PT
    Installation of printers using Internet Printing Protocol (IPP) might not complete successfully.

    Note: IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Resolution: This issue has been resolved in KB5006746.

    Affected platforms:
    • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1809; Windows 11, version 21H2; Windows 10, version 1909
    • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1809; Windows Server 2022; Windows Server, version 1909

    Receiving a prompt for administrative credentials every time you attempt to print

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-15, 17:21 PT
    After installing or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.

    Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
    Resolution: This issue was resolved in KB5006746. If after installing KB5006746 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481).

    Compatibility issues with apps using some non-ASCII characters in their registry keys

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-04, 12:18 PT
    Compatibility issues have been found between apps using some non-ASCII characters in their registry keys or subkeys and Windows 11. Affected apps might be unable to open and might cause other issues or errors in Windows, including the possibility of receiving an error with a blue screen. Important Affected registry keys with non-ASCII characters might not be able to be repaired.
    To safeguard your upgrade experience, we have applied a compatibility hold on these devices from installing or being offered Windows 11. If your organization is using Update Compliance, the safeguard ID for devices with Cốc Cốc browser is 35891494. The safeguard ID for devices with Aplicação Autenticação.gov is 36632506.

    Affected platforms:
    • Client: Windows 11, version 21H2
    Resolution: This issue was resolved in KB5006746. The safeguard hold is estimated to be removed in mid-November.

    Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.

    Some applications on devices that have AMD Ryzen processors might drop performance

    StatusOriginating updateHistory
    Resolved KB5006746N/A

    Resolved: 2021-10-21, 10:00 PT
    Opened: 2021-10-20, 16:34 PT
    Devices with AMD Ryzen processors might experience latency in the L3 cache after upgrading to Windows 11. Some applications sensitive to memory subsystems performance access time might be affected, including diagnostic and benchmarking applications and certain gaming applications.

    Resolution: This issue has been resolved in KB5006746

    Affected platforms:
    • Client: Windows 11, version 21H2

    Compatibility issues with Intel “Killer” and "SmartByte" networking software

    StatusOriginating updateHistory
    Resolved KB5006674N/A

    Resolved: 2021-10-12, 10:00 PT
    Opened: 2021-10-04, 12:23 PT
    Compatibility issues have been found between some Intel “Killer” and “SmartByte” networking software and Windows 11. Devices with the affected software might drop User Datagram Protocol (UDP) packets under certain conditions. This creates performance and other problems for protocols based on UDP. For example, some websites might load slower than others in affected devices, with videos streaming slower in certain resolutions. VPN solutions based on UDP might also be slower.

    Affected platforms:
    • Client: Windows 11, version 21H2
    Resolution: This issue was resolved in KB5006674.

    Compatibility issues have been found between Oracle VirtualBox and Windows 11

    StatusOriginating updateHistory
    ConfirmedN/A

    Last updated: 2021-10-06, 17:26 PT
    Opened: 2021-10-04, 12:18 PT
    Microsoft and Oracle have found a compatibility issue between VirtualBox and Windows 11, when Hyper-V or Windows Hypervisor is installed. You might be unable to start Virtual machines (VMs) and you might receive an error.

    To safeguard your upgrade experience, we have applied a compatibility hold on these devices from installing or being offered Windows 11. If your organization is using Update Compliance, the safeguard ID is 35004082.

    Workaround: To mitigate the safeguard, you will need to remove Hyper-V or Windows Hypervisor until this issue is resolved with an update Oracle plans to release in October 2021. You can check Oracle's progress by monitoring their ticket #20536. If you are no longer using VirtualBox, uninstalling it should also mitigate the safeguard. 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. 

    Affected platforms:
    • Client: Windows 11, version 21H2
    Next steps: Oracle is working on a resolution and is estimated to release a compatible version of VirtualBox in October 2021. 

    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. If you are trying to upgrade to Windows 11, you might encounter an upgrade compatibility hold and receive the message, "VirtualBox. Your PC requires the latest version of this app. Click Learn More for more information on how to update this app.”