It’s always disconcerting to have a windows update fail. I in general think of these updates as things that happen in the background that I don’t need to worry about. Last week, I got a vague error, which after you lookup, basically says “you hand an error”.
So, I decided to give Microsoft Windows 7 support a try (which is a free service to genuine Microsoft Windows 7 Users). I’d say things went well, though it might have been nice if the error sent me to the answer rather than a lengthy support process.
As It Happened
So, here is how things happened:
Contact Microsoft through their support web site
The error itself took me to a web site that allowed me to file a support case for free. Immediately, I got the following back from an auto responder at 9:02AM
Thank you for contacting Microsoft. Your support request was successfully submitted.
A Microsoft support professional will contact you within the response time specified for the support that you chose.
Print or save this page or note the confirmation number for your reference.
Incident title: windows 7 update failed (sp1 I think)
Support request number: 115778719
Severity rating: Severity C (Minimum business impact)
Type of response: Email to firstname.lastname@example.org
Response time: Your expected response time is: 1 business day
View incident online: https://support.microsoft.com/viewincident
Full name: Peter Kellner
E-mail address: …
Followed 15 hours later by:
Thank you for contacting Microsoft Customer Service.
Your request has been processed. A Support Professional will contact you via e-mail within 24 hours to assist with troubleshooting your issue.
If you are using a spam blocker, please make sure you can receive e-mail messages from *.microsoft.com. If you do not see the response from a Support Professional within the next 24 hours, please check your junk mail folder for an e-mail containing your case number which is listed in the subject line of this e-mail.
If you have any questions regarding this service request or need to update the service request notes, please reply to this e-mail with your case number in the subject line.
Thank you for using Microsoft products and services,
Microsoft Online Customer Service
A Proposed Solution
Then, 3 hours later (or 18 hours from the problem start), I get a proposed solution from a human.
Thank you for contacting Microsoft Online Support Service. My name is Joyce, and I am glad to work with you. For your reference, the case ID for this service request is SRX1157341819. You can contact me by sending an email to email@example.com with the case ID in the subject line.
From the problem description, I understand that win7 sp1 fails to install with error 8024200D. If there has been any misunderstanding, please let me know.
I understand the inconvenience you have experienced. Please be assured that I will do my best to help you.
During the Windows 7 SP1 installation, one of the most common causes of failure occurs when a third-party application holds open a file or locks a file that the Service Pack installation program has to use. For example, a third-party antivirus or antispyware application may cause this problem. If you are running any third-party applications such as Spyblocker, Internet or web accelerators (programs designed to boost the speed of the Internet connection), security or anti-virus programs (McAfee, Norton, etc.), I recommend temporarily disabling or shutting them down during the troubleshooting process. Please be sure to re-enable them once the process has completed.
After that, let us try to run System Update Readiness Tool to replace incorrect data, corrupted files and registry keys on the system. I have included detailed steps below.
Step 1: Run the System Update Readiness Tool
1. Please download the System Update Readiness Tool from the link below according to the System Type:
System Update Readiness Tool for Windows 7 32-bit
System Update Readiness Tool for Windows 7 64-bit
2. Double click downloaded file to run the System Update Readiness Tool. Then restart the computer and install Windows 7 SP1.
If Windows 7 SP1 still cannot be installed, I suggest downloading the Standalone Installer and installing it in Clean Boot Mode.
Step 2: Download Windows 7 SP1 Standalone Installer
1. Download Windows 7 SP1 Standalone Installer from the link below according to the System Type:
2. Please visit the above link and click Continue to finish validation. After that the Download buttons will appear.
If your system is Windows 7 32 bit system, please select the file windows6.1-KB976932-X86.exe to download.
If your system is Windows 7 64 bit system, please select the file windows6.1-KB976932-X64.exe to download.
Please do not select “Run” after clicking the Download button. We need to save the file to the local disk instead of run it from internet directly.
Step 3: Install Windows 7 SP1 in Clean Boot Mode
Please disable all startup items and third party services when booting to avoid conflict when installing Windows 7 SP1.
1. Click "Start", type: MSCONFIG in the search box and press Enter.
Note: Please click "Continue" if the "User Account Control" window pops up.
2. Click "Services", check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
3. Click "Startup", click "Disable All", click "OK" and restart the computer.
Note: Temporarily disabling the Startup Group only prevents the startup programs from loading at startup. This shouldn’t affect the system or other programs. We can manually run these programs later.
4. Please double click the downloaded Standalone Installer and follow the instructions to install Windows 7 SP1.
To restore the computer to use a Normal Startup, repeat step 1 above. Then click "Normal Startup" on the General tab, click "OK", and then restart the computer.
If the issue persists, please collect a screenshot of the error message for further research. Please be sure that the information does not contain any of your confidential and private information. It’s for troubleshooting purposes only. Thank you for understanding.
How to capture a Screenshot
1. When the error appears, please press the Print Screen key (PrtScn) on the keyboard.
2. Click "Start", point to "All Programs", point to "Accessories" and then click "Paint".
3. In the Paint program, click the "Edit" menu, click "Paste", click the "File" menu, and click "Save". The "Save As" dialogue box will appear. Type a file name in the "File name:" box, for example: screenshot.
Note: Make sure "JPEG (*.JPG;*.JPEG;*.JPE;*.JFIF)" is selected in the "Save as type" box. Save the screenshot file to the Desktop.
Since our issue also can be caused by the corrupted system components. I also need the log file from the system update readiness tool. If I found any system errors from the log, we might need to involve one System Support later. Please be assured that Microsoft Support will do our best to help you fix the current problem.
Collect the CheckSUR.log file
1. Click "Start. Type "%WINDIR%\Logs\CBS\CheckSUR.log" (without the quotation marks) in the Search Bar and press Enter. We will see a file named "CheckSUR.log"
2. Click on the "File" menu and then click on the "Save As".
3. From the left panel, click "Desktop" and click the Save button.
4. The file will be saved to your Desktop. Please send the file as an attachment in an email to
Note: When attaching files to emails, the process will vary depending on the email application being used. While you are composing the email, most applications will provide you with either an "Attach" button or a Paper Clip Icon to click in order to attach a file. After clicking this button/icon you must browse to the file you wish to attach and select it by either double clicking it or clicking it once and then clicking "Attach".
After obtaining the information, I will research it and get back to you as soon as possible. Please take your time with the steps and let me know the results at your earliest convenience. If there are any questions or concerns, feel free to contact me.
I look forward to your reply.
My Solution Success
I chose the standalone installer for my solution which did work. As advertised, it ran for several hours, but at the end, it did install successfully.
The screen I got to was this:
Within 24 hours, as promised, my system was back up and running! I never actually had any down time so it was a good solution. It just required a little patience.