[SOLVED] Error 0x800f0982 - Cumulative Update KB4530715

N

navysites

Member
Joined
Dec 30, 2019
Posts
18
Hi!

PC: Lenovo Yoga C930
OS: Windows 10 Pro x64 Version 1809 Build 17763.316

Installation of the cumulative update always reaches 100%, but then fails with error 0x800f0982.
Earlier Cumulative Update 2019-03 had installed without issues.

I tried my best to translate a few things from the German UI, hopefully understandable.

Error 0x800f0982 may occur related to asian language packs: https://support.microsoft.com/de-de/help/4493509/windows-10-update-kb4493509.
However, no asian language pack was ever installed.

Removing the Connect app is also likely to cause this issue - but I did not remove it.

Steps taken on my own:
cmd (Run as Administrator for all of the following commands)
sfc /scannow: reported some issues, but could not repair them
Perform a restart
dism /Online /Cleanup-Image /ScanHealth: possible repairs
dism /Online /Cleanup-Image /RestoreHealth: success
dism /Online /Cleanup-Image /ScanHealth: no issues detected
Perform a restart
sfc /scannow: reported some issues and repaired them
dism /Online /Cleanup-Image /ScanHealth: no issues detected
sfc /scannow: no integrity violations found
Windows Update: again error 0x800f0982 for Cumulative Update 2019-12 KB4530715
Windows Update Troubleshooter: The issue could not be detected by the troubleshooter.

After that I performed the steps described in the Windows Update Forum Posting Instructions.

SFCFix.txt, empty lines removed:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-31 18:13:05.271
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
Failed to generate a complete zip file. Upload aborted.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-12-31 18:16:08.321
----------------------EOF-----------------------

CBS folder

If I understand correctly, I have the option to try an in-place upgrade to my current version 1809 (or newer), keeping my apps, in order to get rid of the issue for the moment.
However, I don't know for how long the effect would last.
Besides, I want to avoid go through all of my settings just to find out which ones I need to redo.
My other PC, HP Envy 17 bw0003ng, has the same issue.
Windows Update used to work without issues on both PCs for some months, but sooner or later they arrived at error 0x800f0982.
Therefore I would very much prefer to find and eliminate the root cause once for all, if possible.

Thank you in advance!
 

Attachments

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.
i3yiUac.png


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.
 
Thank you for your quick reaction!

Process Monitor Trace captured.

Installing the Cumulative Update failed, as expected:
2019-12 Kumulatives Update für Windows 10 Version 1809 für x64-basierte Systeme (KB4530715)
Installationsfehler – 0x800f0982

Besides, there is a pending restart now due this update just installed:
Microsoft .NET Framework 4.8 für Windows 10 Version 1809 für x64 (KB4486153)
Neustart ausstehend

Along with instructions on further steps for me to take, please also let me know when to perform (or to postpone) that pending restart, so it does not interfere with your diagnostics plan.

Logfile.PML

CBS folder
 
OK, restart performed.
Clicked Repeat button to install Cumulative Update.
Then two additional updates were found, downloaded and successfully installed - they required another restart.

2019-12 Kumulatives Update für .NET Framework 3.5, 4.7.2 und 4.8 für Windows 10 Version 1809 für x64 (KB4533094)
Neustart ausstehend

Microsoft .NET Framework 4.8 Language Packs für Windows 10 Version 1809 für x64 (KB4087642)
Neustart ausstehend

Restart performed.
ProcMon trace captured now - from clicking the Repeat button for the Cumulative Update to the point where it reported error 0x800f0982.
Along came also Security intelligence update for Windows Defender Antivirus (KB2267602), however without requiring a restart.
If this should interfere with your diagnostics, I can try again to capture a ProcMon trace of installing the Cumulative Update only.

Logfile.PML

CBS folder
 
Thank you.

Please do the following:

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.
 

Attachments

Thank you!

Do you prefer to read such few lines of information right away in the text or to have the file attached? Here's both.

Fixlog.txt:

Entfernungsergebnis von Farbar Recovery Scan Tool (x64) Version: 28-12-2019
durchgeführt von cli (31-12-2019 23:39:06) Run:1
Gestartet von C:\Users\cli\Desktop
Geladene Profile: cli (Verfügbare Profile: cli)
Start-Modus: Normal
==============================================

fixlist Inhalt:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKLM\COMPONENTS\CanonicalData\Deployments\aa8952d922d..8d2eed6aea4_31bf3856ad364e35_10.0.17763.348_30abf4d99918ef0e]
*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

Der Vorgang wurde erfolgreich beendet.


========= Ende von CMD: =========

HKLM\COMPONENTS\CanonicalData\Deployments\aa8952d922d..8d2eed6aea4_31bf3856ad364e35_10.0.17763.348_30abf4d99918ef0e => erfolgreich entfernt

==== Ende von Fixlog 23:39:06 ====
 

Attachments

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.
 

Attachments

Thank you. You too.

Please do the following again:

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.
i3yiUac.png


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.
 
Thanks.

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.
 

Attachments

Thanks.

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.
 

Attachments

Thanks.

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.

I'm off to bed.

Good night.
 

Attachments

Morning!

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.
 

Attachments

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.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top