-->
- Windows Cannot Start Mapping On The Adapter Not Connected Wirelessly
- Windows Cannot Start Mapping On The Adapter Not Connected Router
See a list of known issues that have been resolved for Windows 10, version 2004 and Windows Server, version 2004 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.
Reinstall Network Adaptor. Your network adaptor establishes your connection to a network. Update Network Drive. If the network adapter is visible in the Device Manager, you can also try updating it.Sometimes, the issue is due to a bug in the driver version installed on your system.
Resolved issues
| Summary | Originating update | Status | Date resolved |
| Stop error when plugging in a Thunderbolt NVMe SSD Devices using Thunderbolt SSDs may receive a stop error 'DRIVER_VERIFIER_DMA_VIOLATION (e6)' when plugging an SSD in. | OS Build 19041.488 KB4571744 2020-09-03 | Resolved KB4586853 | 2020-11-30 14:00 PT |
| Issues when using Microsoft IME for Japanese or Chinese languages Users of the Microsoft IME for Japanese or Chinese languages might have issues. | N/A | Resolved KB4586853 | 2020-11-30 14:00 PT |
| Domain controllers in your enterprise might encounter Kerberos authentication issues Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020. | OS Build 19041.630 KB4586781 2020-11-10 | Resolved KB4594440 | 2020-11-19 10:00 PT |
| Certificates may not be present after updating to a newer version of Windows 10 Devices in a managed environment using update management tools or ISO images might lose certificates when updating. | OS Build 19041.546 KB4577063 2020-10-01 | Resolved | 2020-11-17 14:11 PT |
| Local Security Authority Subsystem Service (lsass.exe) might fail on some devices Affected devices might receive a critical system process error and the device might restart. | N/A | Resolved KB4565503 | 2020-07-14 10:00 PT |
| When installing incorrectly formatted third-party drivers, you might receive an error You might receive, “Windows can’t verify the publisher of this driver software” or other errors. | OS Build 19041.572 KB4579311 2020-10-13 | Resolved | 2020-10-20 10:06 PT |
| Certain WWAN LTE modems might not be able to connect after waking from sleep Affected WWAN LTE modems might show no internet and be unable to connect. | N/A | Resolved KB4577063 | 2020-10-01 10:00 PT |
| Dragging with the mouse in some apps might cause issues for some IME users Users of the Microsoft IME for Chinese and Japanese might receive an error or the app might stop responding or close. | N/A | Resolved KB4571744 | 2020-09-03 14:00 PT |
| Issue with older drivers for Nvidia display adapters (GPU) You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00. | N/A | Resolved KB4568831 | 2020-07-31 10:00 PT |
| Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting | N/A | Resolved KB4568831 | 2020-07-31 10:00 PT |
| Difficulty connecting to more than one Bluetooth device Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device. | N/A | Resolved KB4568831 | 2020-07-31 10:00 PT |
| Variable refresh rate not working as expected on devices with Intel iGPU Enabling VRR on affected devices will not enable the VRR for games using Direct X 9. | N/A | Resolved KB4568831 | 2020-07-31 10:00 PT |
| Stop error when plugging or unplugging a Thunderbolt dock Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dock | N/A | Resolved KB4565503 | 2020-07-16 17:07 PT |
| Outlook closes unexpectedly or you might receive an error when attempting to open An example of an error you might receive is, 'Outlook couldn't start last time.' | OS Build 19041.388 KB4565503 2020-07-14 | Resolved | 2020-07-15 15:43 PT |
| Issues using ImeMode property to control IME mode for individual text entry fields Some IMEs for certain langauges might have issues using the ImeMode property with certain apps. | N/A | Resolved KB4565503 | 2020-07-14 10:00 PT |
| Print spooler might error or close unexpectedly when attempting to print Certain printers might be unable to print after taking updates released June 9, 2020. | OS Build 19041.329 KB4557957 2020-06-09 | Resolved KB4567523 | 2020-06-18 10:00 PT |
| No mouse input with apps and games using GameInput Redistributable Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input. | N/A | Resolved | 2020-06-12 17:06 PT |
| Error when attempting to open any Microsoft Office application You might receive the error: Windows cannot find 'c:program filesmicrosoft officerootoffice16winword.exe' | OS Build 19041.329 KB4557957 2020-06-09 | Resolved External | 2020-06-12 17:06 PT |
Issue details
November 2020
Stop error when plugging in a Thunderbolt NVMe SSD | ||
| Status | Originating update | History |
| Resolved KB4586853 | OS Build 19041.488 KB4571744 2020-09-03 | Resolved: 2020-11-30, 02:00 PT Opened: 2020-11-05, 07:01 PT |
An incompatibility issue has been found with Windows 10, version 2004 or Windows 10, version 20H2 when using an Thunderbolt NVMe Solid State Disk (SSD). On affected devices, when plugging in a Thunderbolt NVMe SSD you might receive a stop error with a blue screen and 'DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified.' Affected Windows 10 devices will have at least one Thunderbolt port and any currently available version of the driver file stornvme.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers from being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard IDs is 29991611. Affected platforms:
Resolution: This issue was resolved in KB4586853 and the safeguard hold has been removed as of December 11, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 20H2 or Windows 10, version 2004 is offered. | ||
Domain controllers in your enterprise might encounter Kerberos authentication issues | ||
| Status | Originating update | History |
| Resolved KB4594440 | OS Build 19041.630 KB4586781 2020-11-10 | Resolved: 2020-11-19, 10:00 PT Opened: 2020-11-14, 01:39 PT |
After installing KB4586781 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting:
Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments. Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB4594440. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594440, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4594440 is not available from Windows Update and will not install automatically. | ||
October 2020
Certificates may not be present after updating to a newer version of Windows 10 | ||
| Status | Originating update | History |
| Resolved | OS Build 19041.546 KB4577063 2020-10-01 | Resolved: 2020-11-17, 02:11 PT Opened: 2020-10-30, 05:16 PT |
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated. Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps. Workaround: If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. Affected platforms:
Resolution: This issue is now resolved when using the latest feature update bundles and refreshed media. Feature update bundles were released November 9, 2020 for Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. Refreshed media was released November 3, 2020 on Volume Licensing Service Center (VLSC) and Visual Studio Subscriptions (VSS, formerly MSDN Subscriptions). For information on verifying you're using the refreshed media, see How to address feature update refreshes in your environment. If you are using or creating custom media, you will need to include an update released October 13, 2020 or later. Note If you are updating to Windows 10, version 20H2, this is only resolved with the feature update bundle released November 9, 2020. Refreshed media is not yet available on VLSC or VSS. Refreshed media for VLSC and VSS will be released in the coming weeks to address this issue and another known issue that requires a media refresh. Please check the known issue here for the status of the remaining Windows 10, version 20H2 known issue. | ||
When installing incorrectly formatted third-party drivers, you might receive an error | ||
| Status | Originating update | History |
| Resolved | OS Build 19041.572 KB4579311 2020-10-13 | Resolved: 2020-10-20, 10:06 PT Opened: 2020-10-13, 09:37 PT |
When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when one or more of the following is present in a driver package:
Affected platforms:
Next steps: If this happens you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue. | ||
August 2020
Issues when using Microsoft IME for Japanese or Chinese languages | ||
| Status | Originating update | History |
| Resolved KB4586853 | N/A | Resolved: 2020-11-30, 02:00 PT Opened: 2020-08-31, 12:12 PT |
Users of the Microsoft IME for Japanese or Chinese languages might experience issues when attempting various tasks. Input may have issues, you may receive unexpected results or you may be unable to enter text. For a list of specific issues, see KB4564002. Affected platforms:
Resolution: All IME issues listed in KB4564002 were resolved in KB4586853. | ||
Certain WWAN LTE modems might not be able to connect after waking from sleep | ||
| Status | Originating update | History |
| Resolved KB4577063 | N/A | Resolved: 2020-10-01, 10:00 PT Opened: 2020-08-31, 11:42 PT |
After waking from sleep or hibernation, certain WWAN LTE modems might show no internet in the Network Connectivity Status Indicator (NCSI) in the notification area and might be unable to connect to the internet. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected WWAN LTE modems drivers installed from being offered Windows 10, version 2004 until the issue has been resolved. If your organization is using Update Compliance, the safeguard ID is 28428232. Workaround: To mitigate this issue if you are already on Windows 10, version 2004, you can enable then disable Airplane mode. To do this, you can select the Start button, type airplane mode and select it. In the settings dialog, toggle Airplane mode on then off again. You should now be able to connect as expected. Affected platforms:
Resolution: This issue was resolved in KB4577063 and the safeguard hold has been removed as of October 15, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. | ||
July 2020
Dragging with the mouse in some apps might cause issues for some IME users | ||
| Status | Originating update | History |
| Resolved KB4571744 | N/A | Resolved: 2020-09-03, 02:00 PT Opened: 2020-07-14, 09:06 PT |
Users of the Microsoft IME for Chinese and Japanese in some apps such as Microsoft Excel, might receive an error or the app might stop responding or close when attempting to drag with the mouse. Affected platforms:
Resolution: This issue was resolved in KB4571744. If you are experiencing other IME issues, please see KB4564002 for information on symptoms, workaround steps and currently resolved issues. | ||
Outlook closes unexpectedly or you might receive an error when attempting to open | ||
| Status | Originating update | History |
| Resolved | OS Build 19041.388 KB4565503 2020-07-14 | Resolved: 2020-07-15, 03:43 PT Opened: 2020-07-15, 03:22 PT |
Microsoft Outlook might close unexpectedly or you might receive an error when attempting to open the app. An example of an error you might receive is, 'Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?' You might also see an event in the Event Viewer, as listed in the article linked below. Affected platforms:
Workaround: As an alternative, on your Windows 10 device you can use the Office365 on the web (OWA), also known as webmail. Outlook mobile is also unaffected. There is no workaround for this issue for the Outlook app on Windows 10 until the resolution is deployed to your device. We do not recommend using the command to revert to an earlier version. Resolution: This Outlook issue has been resolved and will be deployed automatically to your device. This issue was not related to any update for Windows and no update for Windows is needed. We expect this issue to be completely resolved for all affected users by July 15, 2020 at 3:30 PM PST (10:30 PM UTC). You may also need to attempt to open Outlook a few times before it will be fully refreshed and open as expected. For more information, please see the support article, Active Investigation into Outlook Crashing on Launch and this twitter thread. | ||
June 2020
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices | ||
| Status | Originating update | History |
| Resolved KB4565503 | N/A | Resolved: 2020-07-14, 10:00 PT Opened: 2020-06-24, 12:46 PT |
The Local Security Authority Subsystem Service file (lsass.exe) might fail on some devices immediately after login with the error message in system event log Wininit event 1015 is logged with the text, “A critical system process, C:WINDOWSsystem32lsass.exe, failed with status code c0000008. The machine must now be restarted.' c0000008 is an invalid handle error related to Credential Manager (VaultSvc) Service. Affected platforms:
Resolution: This issue was resolved in KB4565503. Note If you are receiving an LSASS failure on Windows 10, version 20H2, while 'Your PC will automatically restart in one minute' is displayed for both issues, it is a different error code (status code C0000374, a heap corruption issue) and a different issue. Please see You might receive an error when accessing the sign-in options or users MMC snap-in. | ||
Print spooler might error or close unexpectedly when attempting to print | ||
| Status | Originating update | History |
| Resolved KB4567523 | OS Build 19041.329 KB4557957 2020-06-09 | Resolved: 2020-06-18, 10:00 PT Opened: 2020-06-12, 04:06 PT |
After installing KB4557957, certain printers may be unable to print. Print spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF. Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB4567523. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4567523, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4567523 is not available from Windows Update and will not install automatically. | ||
Error when attempting to open any Microsoft Office application | ||
| Status | Originating update | History |
| Resolved External | OS Build 19041.329 KB4557957 2020-06-09 | Last updated: 2020-06-12, 05:06 PT Opened: 2020-06-12, 04:18 PT |
We have received reports that some users are unable to open apps after installing KB4557957, especially Microsoft Office apps. Affected users might also receive an error, such as, 'Windows cannot find 'c:program filesmicrosoft officerootoffice16winword.exe' Make sure you typed the name correctly, and then try again.' Affected platforms:
Resolution: This issue has been resolved by Avast. This issue only affected devices with certain versions of Avast or AVG applications and was addressed with an update to their respective products. For more information on this, please see Avast's forum post here. Note No update is needed for Windows or Microsoft Office to address this issue. | ||
May 2020
Issue with older drivers for Nvidia display adapters (GPU) | ||
| Status | Originating update | History |
| Resolved KB4568831 | N/A | Resolved: 2020-07-31, 10:00 PT Opened: 2020-05-27, 12:09 PT |
Nvidia and Microsoft have found incompatibility issues with certain versions of Nvidia display adapter drivers and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions might receive a stop error with a blue screen or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Nvidia display drivers drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 24803238. Affected platforms:
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. | ||
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present | ||
| Status | Originating update | History |
| Resolved KB4568831 | N/A | Resolved: 2020-07-31, 10:00 PT Opened: 2020-05-27, 12:09 PT |
An incompatibility issue was found with apps or drivers using certain versions of aksfridge.sys or aksdf.sys and Windows 10, version 2004 (the Windows 10 May 2020 Update). When an affected version of aksfridge.sys or aksdf.sys is present, Windows 10, version 2004 might fail to install or might fail to start after updating. Affected file versions are up to 1.8.0.* for aksfridge.sys or up to 1.51.* for aksdf.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with an affected version of aksfridge.sys from being offered Windows 10, version 2004 or Windows Server, version 2004. If your organization is using Update Compliance, the safeguard ID is 24858586. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. | ||
Difficulty connecting to more than one Bluetooth device | ||
| Status | Originating update | History |
| Resolved KB4568831 | N/A | Resolved: 2020-07-31, 10:00 PT Opened: 2020-05-27, 12:22 PT |
Realtek and Microsoft have found incompatibility issues with certain versions of drivers for Realtek Bluetooth radios and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Realtek Bluetooth radio drivers might be unable to connect or pair with more than one Bluetooth device at a time after updating. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Realtek Bluetooth radio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25692458. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows Server, version 2004 is offered. | ||
Variable refresh rate not working as expected on devices with Intel iGPU | ||
| Status | Originating update | History |
| Resolved KB4568831 | N/A | Resolved: 2020-07-31, 10:00 PT Opened: 2020-05-27, 12:13 PT |
Intel and Microsoft have found incompatibility issues when using a monitor with Variable refresh rate (VRR) plugged into an Intel integrated graphics processing unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for games using Direct X 9. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004. If your organization is using Update Compliance, the safeguard ID is 26251417. Affected platforms:
Resolution: This issue was resolved in KB4568831 and the safeguard hold has been removed as of August 13, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. | ||
Stop error when plugging or unplugging a Thunderbolt dock | ||
| Status | Originating update | History |
| Resolved KB4565503 | N/A | Resolved: 2020-07-16, 05:07 PT Opened: 2020-05-27, 12:18 PT |
Intel and Microsoft have found incompatibility issues when Windows 10, version 2004 (the Windows 10 May 2020 Update) is used with certain settings and a Thunderbolt dock. On affected devices, you might receive a stop error with a blue screen when plugging or unplugging a Thunderbolt dock. Affected Windows 10 devices will have at least one Thunderbolt port, have Kernel DMA Protection enabled and Windows Hypervisor Platform disabled. To verify your Kernel DMA Protection settings, please see How to check if Kernel DMA Protection is enabled. To verify your Windows Hypervisor Platform settings, select Start, type turn windows features on or off and select it. When the Windows Features dialog opens, find the setting for Windows Hypervisor Platform. If it is note checked, then Windows Hypervisor Platform is disabled. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004. Affected platforms:
Resolution: This issue was resolved in KB4565503 and the safeguard hold has been removed as of July 16, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. | ||
Issues using ImeMode property to control IME mode for individual text entry fields | ||
| Status | Originating update | History |
| Resolved KB4565503 | N/A | Resolved: 2020-07-14, 10:00 PT Opened: 2020-05-27, 12:18 PT |
Some apps utilize the ImeMode property to control the IME (Input Method Editor) mode for individual text entry fields to increase typing efficiency. Some IMEs in Windows 10, version 2004 (the May 2020 Update) might have issues using the ImeMode property with certain apps. For example, the input mode will not switch automatically to Full-width Katakana mode, Full-width Alphanumeric mode, or Full-width Hiragana mode. Affected platforms:
Resolution: This issue was resolved in KB4565503. | ||
Windows Cannot Start Mapping On The Adapter Not Connected Wirelessly
No mouse input with apps and games using GameInput Redistributable | ||
| Status | Originating update | History |
| Resolved | N/A | Resolved: 2020-06-12, 05:06 PT Opened: 2020-05-27, 12:11 PT |
An incompatibility issue was found with some apps and games using GameInput Redistributable and Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected apps or games might lose mouse input. Note GameInput Redistributable might be bundle with apps and games and might be silently installed during the installation of that app or game. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with GameInput Redistributable from being offered Windows 10, version 2004. Affected platforms:
Resolution: After further investigation, we have found that this issue does not affect any version of GameInput Redistributable in use. The safeguard hold has been removed. Please note, it can take up to 48 hours before the update to Windows 10, version 2004 (the Windows 10 May 2020 Update). | ||