Windows 10 Volume 4 Loop
Summary :
The Unmountable Boot Volume Windows stop code error is a pain. Since it usually keeps you from getting into Windows, you can’t troubleshoot it like you would. Download Windows 10 2) Find the keyboard key to boot to the flash drive: List of PC brands with their corresponding hot-keys If it is a custom computer you can temporarily change the bios boot order to boot to the external flash hard drive. 3) It may take 5 - 10 minutes while the iso loads while viewing the windows icon 4) Select the language. Oct 10, 2019 Automatic Repair is Windows' own repair tool that is available on Windows 10/8. The tool is designed to launch automatically when a start-up problem comes up on Windows system. Normally, by running Automatic Repair, Windows diagnoses the start-up problem (missing or corrupt system files, drivers, registry settings, etc.), fix it and then. The Unmountable Boot Volume Windows stop code error is a pain. Since it usually keeps you from getting into Windows, you can’t troubleshoot it like you would. Using System File Checker in Windows 10. System File Checker is a utility in Windows 10 that checks for problems with files on your computer. To run it, follow these steps: Make sure you've installed the latest updates for Windows 10, and then restart your machine. To find out more, read Update Windows 10. In the search box on the taskbar, type.
Computer is getting stuck on the screen 'Getting Windows ready. Don't turn off your computer' every time you restart? Don't panic! Here are some effective fixes for the getting Windows ready stuck issue in Windows 10/8, as well as a fast disaster recovery solution.
Quick Navigation :
Windows 10 Stuck on Getting Windows Ready
For many Windows 10 and Windows 8 users, it is common to experience unexpected issues with their operating systems. An issue that a lot of them encounter is their computer like Surface Pro 4 getting stuck on a loading screen with a message saying 'Getting Windows ready. Don't turn off your computer', as shown in the following figure:
Users report this issue on forums like Reddit, saying it often happens when they are trying to turn on, turn off or restart/reboot their computers or install Windows operating system.
- Getting Windows ready boot loop, restarting loop, infinite loop, update loop
- Windows 10 update stuck on getting things ready
- Windows 10 install stuck at getting ready
How long does it take for Windows 10 to be ready? In some cases, this process could take more than several hours, which may prove to be a nuisance for many users.
If you also run into the Windows 10 stuck in loop getting Windows ready issue, here we will provide you effective solutions.
Quick Video Guide:
How to Fix Getting Windows Ready Stuck
Simply restarting the computer is often insufficient to get rid of Windows 10 getting ready loop. Fortunately, here are five workarounds you can try out below.
Solution 1: Simply Wait for Some Time
Yes, you read that right. The easiest working fix is to wait for some time. This is actually the method that some of Microsoft's support technicians advise.
When you are prompted with the message 'Getting Windows ready don’t turn off your computer', your system may be processing some tasks in the background such as downloading and installing files, starting a Windows 10 update process, modifying settings of the applications and modules, etc.
The system may take some time to complete these tasks depending on the number of programs installed on your PC. Thus, to let your computer boot properly, the first thing you can do is to wait until the system tasks are finished.
Usually, it is recommended to wait patiently for about 2-3 hours. However, if you still see the screen, you should try other solutions to troubleshoot getting Windows ready Windows 10 loop.
Solution 2: Shut Down Your PC and Power Reset It
Power resetting your PC can clear all the information in the memory, but this won't damage the disk data. This method could help fix certain corruption issues on the computer.
Therefore, power resetting your Windows might fix the getting Windows ready stuck issue.
Here are the instructions to get Windows out of the update loop:
Step 1: Turn off your PC by pressing the power button.
Step 2: Disconnect all peripheral devices including USB flash drives, external hard drives, earphones, etc. Also, unplug the power cable or adapter from your PC.
Step 3: If you are using a laptop and the battery is detachable, remove the battery from the battery compartment.
Step 4: Press and hold the Power button on your computer for about 30 seconds to drain all the remnant charge from the capacitors.
Step 5: Connect the power cable back to the PC or insert the battery into your laptop. However, don not re-plug any of the USB devices.
Step 6: Press the Power button to boot your PC. You can now check whether the Windows 10 stuck in loop getting Windows ready issue is solved.
Solution 3: Perform a System Restore or System Image Recovery
If you have created a System Restore point or system image backup with Windows snap-in tools, you can try using the restore point or image file to restore the PC to a normal statewhen you encounter the getting Windows ready stuck issue.
But how do you perform restoration when your system is stuck on the same screen?
Step 1:Download Media Creation Tool from the Microsoft website. Run it to create a Windows installation media (USB installation drive or CD/DVD disc).
Step 2: Boot the PC from the disc or USB drive. Configure the language, time, keyboard method, and click Repair your computer.
Step 3: Go to Choose an option > Troubleshoot > Advanced options > System Restore.
Step 4: Follow the wizard to finish a system restore to get you out of the Windows 10 getting ready loop.
If you have a system image, choose System Image Recovery under the Advanced options tab. Then, restore your computer to its earlier state using the image backup.
Solution 4: Run System File Checker
If Windows is taking too long to get Windows 8/10 ready or the above methods fail to troubleshoot stuck at getting Windows ready, you can try the System File Checker tool. Sometimes Window's need to get ready for update at every reboot may be caused by the corrupted files on your computer.
Here is how to fix damaged system files:
Step 1: In the same way as above, insert the installation disc or USB drive into your PC and boot it from this drive.
Step 2: Go to Repair your computer, enter the Choose an option screen and choose Troubleshoot.
Step 3: Click Command Prompt in the Advanced options page.
Step 4: After cmd window is opened, type the command: sfc /scannow and press Enter on the keyboard.
Wait patiently until the verification process 100% completes. Then reboot the computer to see whether getting Windows ready Windows 10 loop still exists.
Solution 5: Perform Windows 10 Startup Repair
When your PC is stuck in getting Windows ready every reboot, performing Windows Startup Repair might be able to fix the issue.
This also requires entering the Windows Recovery Environment (WinRE) using the Windows installation disc. In WinRE, navigate to Advanced options and choose Startup Repair: Fix problems that keep Windows from loading.
Windows Automatic Repair not working! Read this post to find how to solve Windows couldn't load correctly and Automatic Repair couldn't repair your PC.
If the repair process results in the error 'startup repair couldn’t repair your PC' or 'automatic repair couldn’t repair your PC', try another solution to fix Windows 10 stuck on getting Windows ready issue.
Solution 6: Uninstall Recently Installed Update in Safe Mode
An erroneous recent update might confuse Windows to get stuck in another update loop, so uninstalling these updates may fix the issue. This will need to be done through the Safe Mode.
Step 1: Access the Advanced options page, then click Startup Settings and press F4 to access the computer Safe Mode.
Step 2: In Windows 10 Safe Mode, right-click Start to choose Control Panel. Then go to Programs and Features.
Step 3: Click View installed update in the left panel. Select the recently installed updates and uninstall them to fix the Windows 10 stuck in loop getting Windows ready issue.
Finally, restart Windows 10 and the computer stuck on getting Windows ready issue should be solved.
Solution 7: Perform a Clean Windows Installation
If none of the above methods can help you out of getting Windows ready stuck issue, the operating system may have unfixable issues. The final solution will be installing a fresh copy of Windows.
Back up Important Files before Windows Installation
Windows clean install will erase some of your personal files. Thus, make sure you have backed up important data from the system partition or the Desktop. Also, have your license key ready.
To back up computer files, we recommend using the free Windows 10 backup software, MiniTool ShadowMaker. It is compatible with Windows 10/8/7 and can help you to back up files, disk, partition or OS with simple clicks. Here, you can start backing up your files by getting its Trial Edition (30-day free use is supported) from the button below.
Step 1: Run MiniTool ShadowMaker Trial Edition.
Step 2: Under the Backup tab, go to Source > Folders and Files to choose the files you want to back up.
Then, select a destination path to store the backup image file. This software specifies a folder for you by default, but you can also specify a location like an external hard drive or USB drive.
Step 3: Click Back up Now to execute the backup task.
Perform a Clean Windows 10 Install
After finishing the file backup, now you can reinstall your Windows 10 to fix getting Windows ready stuck issue.
Step 1: Boot your computer from an installation disc or drive.
Step 2: Choose the language, time format, and keyboard.
Step 3: Click Install now and follow the instructions on the screen.
After the setup process is complete, the problem Windows 10 stuck on getting Windows ready should be completely resolved.
If you are unsure of how to make a refresh copy of Windows, read How to Reinstall Windows 10. If you think it is complicated to make a clean install, you can follow this post to reset Windows 10 instead.
Suggestion: Back up Windows 10 OS to Safeguard Your PC
Regardless of what system issues occur on your computer, system image recovery is a better solution provided that a system image was created beforehand.
Similarly, restoring the PC to a previous state by using the system backup is also a good solution to Windows 10 getting ready loop for a long time
Therefore, after finishing fixing the issue, it is necessary to back up your OS to protect your computer from system corruption. To do this, we highly recommend using MiniTool ShadowMaker as mentioned above.
Step 1: Launch this backup software for Windows 10, click Keep Trial and Connect in This Computer section.
Step 2: Go to the Backup page; system partitions and storage path are selected by default. Start the system backup process by clicking Back up Now.
Bottom Line
Is your computer stuck on getting Windows ready? Take it easy and use the above methods! In case getting Windows ready stuck occurs again, it is best to back up your Windows 10 operating system with MiniTool ShadowMaker.
Overall, feel free to tell us if you have other ways to fix Windows 10 getting ready loop or questions regarding MiniTool software by contacting [email protected] or leaving a comment below.
Getting Windows Ready Stuck FAQ
- Simply wait for some time
- Shut down your PC and power reset it
- Perform a system restore or system image recovery
- Run System File Checker
- Perform Windows 10 Startup Repair
- Uninstall recently installed update in Safe Mode
- Perform a clean Windows installation
- Remove Any USB Peripherals
- Run Windows Update Troubleshooter
- Rename SoftwareDistribution Folder
- Perform a Clean Boot
- Uninstall the Particular Update Causing the Issue
- Run DISM in Safe Mode
- Run Automatic Repair
- Perform System Restore in WinRE
- More details in the post - How to Fix the “Windows Updates Stuck at 100” Issue on Windows 10
See a list of known issues that have been resolved for Windows 10, version 20H2 and Windows Server, version 20H2 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 issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Printing and scanning might fail when these devices use smart-card authentication Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication. | OS Build 19042.1110 KB5004237 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
| Certain printers unable to print Most affected printers are receipt or label printers that connect via USB. | OS Build 19042.1081 KB5003690 2021-06-21 | Resolved KB5004237 | 2021-07-13 10:00 PT |
| Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs The 64-bit versions of IE11 and apps using the 64-bit version of the WebBrowser control might show PDFs as just gray. | OS Build 19042.1052 KB5003637 2021-06-08 | Resolved KB5004760 | 2021-06-29 10:00 PT |
| A high-pitched noise might be heard when using 5.1 audio with certain settings Certain combinations of apps, audio devices and Windows settings might produce a high-pitched noise when using 5.1 audio | OS Build 19042.906 KB5000842 2021-03-29 | Resolved KB5003690 | 2021-06-21 14:00 PT |
| News and interests button on the Windows taskbar might have blurry text Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar. | OS Build 19042.964 KB5001391 2021-04-28 | Resolved KB5003690 | 2021-06-21 14:00 PT |
| Apps might have issues accessing event logs on remote devices Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later. | OS Build 19042.10000 KB5003637 2021-06-08 | Resolved KB5003637 | 2021-06-08 10:00 PT |
| Security updates released May 11, 2021 might not offer in managed environments Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices are affected. | OS Build 19042.985 KB5003173 2021-05-11 | Resolved | 2021-05-11 19:01 PT |
| Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. | N/A | Resolved | 2021-05-07 13:29 PT |
| Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. | N/A | Resolved | 2021-05-07 13:29 PT |
| Lower than expected performance in games Some users have reported lower game performance in full screen or borderless windowed mode when using multiple monitors. | OS Build 19042.906 KB5000842 2021-03-29 | Resolved | 2021-04-27 15:48 PT |
| Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates Microsoft Edge missing when installing Windows from custom media/ISOs using updates released March 25, 2021 or later. | OS Build 19042.906 KB5000842 2021-03-29 | Resolved | 2021-03-29 17:01 PT |
| Unexpected results when printing from some apps or to some printers Issues might include missing or solid color graphics, misalignment/formatting issues, or printing of blank pages/labels. | OS Build 19042.867 KB5000802 2021-03-09 | Resolved KB5001649 | 2021-03-18 19:00 PT |
| Error when attempting to print to certain printers You might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print. | OS Build 19042.867 KB5000802 2021-03-09 | Resolved KB5001567 | 2021-03-15 14:00 PT |
| Memory or disk space error when opening documents in Microsoft Office apps You might receive an error when attempting to open files that trigger the Protected View feature. | OS Build 19042.844 KB4601382 2021-02-24 | Resolved | 2021-03-13 11:42 PT |
Issue details
July 2021
Printing and scanning might fail when these devices use smart-card authentication | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.1110 KB5004237 2021-07-13 | Resolved: 2021-08-03, 10:36 PT Opened: 2021-07-23, 14:36 PT |
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. Affected platforms:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. | ||
Certain printers unable to print | ||
| Status | Originating update | History |
| Resolved KB5004237 | OS Build 19042.1081 KB5003690 2021-06-21 | Resolved: 2021-07-13, 10:00 PT Opened: 2021-07-08, 16:40 PT |
After installing KB5003690 or later updates (including out of band updates, KB5004760 and KB5004945), you might have issues printing to certain printers. Various brands and models are affected, primarily receipt or label printers that connect via USB. Note This issue is not related to CVE-2021-34527 or CVE-2021-1675. Affected platforms:
Resolution: This issue was resolved in KB5004237, released July 13, 2021. If you are using an update released before July 13, 2021, you can resolve this issue 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, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Important If you install an update released July 13, 2021 ( KB5004237) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. | ||
June 2021
Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs | ||
| Status | Originating update | History |
| Resolved KB5004760 | OS Build 19042.1052 KB5003637 2021-06-08 | Resolved: 2021-06-29, 10:00 PT Opened: 2021-06-25, 12:53 PT |
After installing KB5003637 or later updates, Internet Explorer 11 (IE11) or apps using the 64-bit version of the WebBrowser control might fail to open PDFs or may render as just a gray background using the Adobe Acrobat plug-in. Note Internet Explorer is only affected if Enable 64-bit Processes for Enhanced Protected Mode is enabled in the Advanced tab in Internet Options. Workaround: To mitigate the issue, you can use one of the following:
Resolution: This issue was resolved in the out-of-band update KB5004760. It is a cumulative update, so you do not need to apply any previous update before installing it. KB5004760 is now available on the Microsoft Update Catalog and must be manually downloaded and installed. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Affected platforms:
| ||
Windows 10 Volume 4 Loops
News and interests button on the Windows taskbar might have blurry text | ||
| Status | Originating update | History |
| Resolved KB5003690 | OS Build 19042.964 KB5001391 2021-04-28 | Resolved: 2021-06-21, 14:00 PT Opened: 2021-06-14, 17:43 PT |
After installing KB5001391 or later updates, the news and interests button in the Windows taskbar might have blurry text on certain display configurations. Affected platforms:
Resolution: This issue was resolved in KB5003690. | ||
Apps might have issues accessing event logs on remote devices | ||
| Status | Originating update | History |
| Resolved KB5003637 | OS Build 19042.10000 KB5003637 2021-06-08 | Resolved: 2021-06-08, 10:00 PT Opened: 2021-06-07, 16:10 PT |
After installing KB5003637 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected. Affected platforms:
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003637 installed. | ||
May 2021
A high-pitched noise might be heard when using 5.1 audio with certain settings | ||
| Status | Originating update | History |
| Resolved KB5003690 | OS Build 19042.906 KB5000842 2021-03-29 | Resolved: 2021-06-21, 14:00 PT Opened: 2021-05-13, 19:35 PT |
After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used. Workaround: To mitigate this issue, you can try one or more of the following:
Affected platforms:
Resolution: This issue was resolved in KB5003690. | ||
Security updates released May 11, 2021 might not offer in managed environments | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.985 KB5003173 2021-05-11 | Resolved: 2021-05-11, 19:01 PT Opened: 2021-05-11, 14:58 PT |
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003173 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates. Affected platforms:
Resolution: This issue is now resolved on the service-side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions. | ||
April 2021
Lower than expected performance in games | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.906 KB5000842 2021-03-29 | Resolved: 2021-04-27, 15:48 PT Opened: 2021-04-23, 18:04 PT |
A small subset of users have reported lower than expected performance in games after installing KB5000842 or later updates. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors. Affected platforms:
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 device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. | ||
March 2021
Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.906 KB5000842 2021-03-29 | Resolved: 2021-03-29, 17:01 PT Opened: 2021-03-29, 16:15 PT |
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone Servicing Stack Update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the Servicing Stack Update (SSU) and latest cumulative update (LCU) without any extra steps. Workaround: If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge from here. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business Affected platforms:
Resolution: This issue is resolved. To avoid this issue, be sure to first slipstream the Servicing Stack Update (SSU) released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the latest cumulative update (LCU). To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:
| ||
Unexpected results when printing from some apps or to some printers | ||
| Status | Originating update | History |
| Resolved KB5001649 | OS Build 19042.867 KB5000802 2021-03-09 | Resolved: 2021-03-18, 19:00 PT Opened: 2021-03-18, 17:25 PT |
After installing updates released March 9, 2021 or March 15, 2021, you might get unexpected results when printing from some apps. Issues might include:
Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB5001649. It is a cumulative update, so you do not need to apply any previous update before installing it. You will need to Check for updates to install KB5001649 and might need to also select Download and Install. For instructions on how to Check for updates, please see Update Windows 10. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5001649 is cumulative and addresses both the issue above and the issue addressed in the March 15, 2021 out-of-band release for the APC_INDEX_MISMATCH error with a blue screen. | ||
Error when attempting to print to certain printers | ||
| Status | Originating update | History |
| Resolved KB5001567 | OS Build 19042.867 KB5000802 2021-03-09 | Resolved: 2021-03-15, 14:00 PT Opened: 2021-03-10, 18:04 PT |
After installing KB5000802, you might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print to certain printers in some apps. This issue affects a subset of Type 3 printer drivers and does not affect printer drivers that are Type 4. If you are unsure which type your printer driver is, use the following steps:
Workaround: To mitigate the issue, follow the instructions in this video. The Command Prompt commands from the video are as follows (you will need to replace KX driver for Universal printing with the name of your printer, as explained in the video):
Affected platforms:
Resolution: This issue was resolved in the out-of-band update KB5001567. It is a cumulative update, so you do not need to apply any previous update before installing it. You will need to Check for updates to install KB5001567 and might need to also select Download and Install. For instructions on how to Check for updates, please see Update Windows 10. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. | ||
Windows 10 Volume 4 Loop Download
Memory or disk space error when opening documents in Microsoft Office apps | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.844 KB4601382 2021-02-24 | Resolved: 2021-03-13, 11:42 PT Opened: 2021-03-13, 10:50 PT |
When opening a document in Microsoft Word, Microsoft Excel, or any Microsoft Office applications, you might receive the error, 'Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space'. This issue only affects devices that have installed Microsoft Office apps from the Microsoft Store and are attempting to open a document that has triggered the use of the Protected View feature. Affected platforms:
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 non-managed devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. To find out more about using Group Policies, see Group Policy Overview. | ||
May 2020
Errors or issues during or after updating devices with certain Conexant audio drivers | ||
| Status | Originating update | History |
| Resolved | N/A | Resolved: 2021-05-07, 13:29 PT Opened: 2020-05-27, 00:20 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio 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 IDs are 25702617, 25702660, 25702662, and 25702673. Affected platforms:
Resolution: The safeguard hold with safeguard IDs 25702617, 25702660, 25702662, and 25702673 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered. | ||
Errors or issues during or after updating devices with Conexant ISST audio drivers | ||
| Status | Originating update | History |
| Resolved | N/A | Resolved: 2021-05-07, 13:29 PT Opened: 2020-05-27, 00:22 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio 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 25178825. Affected platforms:
Resolution: The safeguard hold with safeguard ID 25178825 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered. | ||