BigJohn Member Joined Dec 20, 2019 Posts 5 Dec 21, 2019 #1 Tried to apply cumulative update with Error 0x800f0982 (2019-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4530715) - Error 0x800f0982) Followed the link Windows Update Forum Posting Instructions Step #2 - Run SFC scan Step #3 – SURT/DISM Scan Step #4 - Run SFCFix with following error SFCFix Has Crashed Something has gone horribly wrong and SFCFix has crashed. Attachments CBS.zip 205 KB · Views: 6
Tried to apply cumulative update with Error 0x800f0982 (2019-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4530715) - Error 0x800f0982) Followed the link Windows Update Forum Posting Instructions Step #2 - Run SFC scan Step #3 – SURT/DISM Scan Step #4 - Run SFCFix with following error SFCFix Has Crashed Something has gone horribly wrong and SFCFix has crashed.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Dec 21, 2019 #2 Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
BigJohn Member Joined Dec 20, 2019 Posts 5 Jan 2, 2020 #3 Thanks for feedback. I just came back from holiday. Below please find the dropbox link of the LogFile.PML and CBS.log while capturing from failed Windows update. WinUpdate_Logs
Thanks for feedback. I just came back from holiday. Below please find the dropbox link of the LogFile.PML and CBS.log while capturing from failed Windows update. WinUpdate_Logs
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 2, 2020 #4 Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled. Attachments fixlist.txt 2.7 KB · Views: 13
Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled.
BigJohn Member Joined Dec 20, 2019 Posts 5 Jan 2, 2020 #5 Attached the Fixlog.txt file and the dropbox link for ProcessMon and CBS logs. I retried the windows update and still failed. WinUpdate_Logs Attachments Fixlog.txt 3.6 KB · Views: 3
Attached the Fixlog.txt file and the dropbox link for ProcessMon and CBS logs. I retried the windows update and still failed. WinUpdate_Logs
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 2, 2020 #6 Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled. Attachments fixlist.txt 2.7 KB · Views: 5
Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled.
BigJohn Member Joined Dec 20, 2019 Posts 5 Jan 2, 2020 #7 Failed again. Please find the CBS and ProcessMon logs for this Windows update run. WinUpdate_Logs Attachments Fixlog.txt 3.6 KB · Views: 3
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 2, 2020 #8 Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled. Attachments fixlist.txt 2.7 KB · Views: 10
Thank you. Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Afterwards, retry updates with ProcMon capture enabled.
BigJohn Member Joined Dec 20, 2019 Posts 5 Jan 3, 2020 #9 This time the windows update ran successfully. Thank you very much.