Microsoft has released a solution for the Stop 0xd1 errors that some customers encountered after the July 10th update release. The offering of Windows updates released on July 10th will resume.
Suggested actions for customers:
- Customers who have previously deployed Windows updates released on July 10 and did not encounter any Stop 0x1d errors have no new action to take.
- Customers who did not install Windows updates released on July 10 are encouraged to apply the original updates released on July 10, and monitors for Stop 0x1d errors.
- Only customers who encounter a Stop 0xd1 error after installing Windows updates released on July 10 are encouraged to install one of the following update packages to resolve the Stop 0x1d symptom:
If you have already performed the below steps of rolling back the July Cumulative Updates (CU), you will need to resinstall the CU before installing the new patch.
Starting from having to install the July CU again, we’ll do the following:
From the Configuration manger app, run:
Choose “Install All”:
Since I deployed this patch as available, you can see the client had to download the patch, rather then it being downloaded already, waiting for a MW. The reason I made it available is because not ever server needed the fix, and it was easier to just have it offered to the admins if they needed it.
Post installation reboot required:
Once both patches are installed, well see the folllowing:
If you still have the CU installed and are experiencing the issues decribed in this article, install just the additional patch:
Rinse and repeat for your specific OS version.
*Please note this patch will require a reboot in most cases.*