[SOLVED] WU error 0x800f0982, but SFCFix found no corruptions

Sysnative Windows Update · Aug 5, 2019

Yes, because while uninstalling it, you (or the system) mas experienced an error and corrupted the files and the keys. Please retry ProcMon now.

HapaxOromenon · Aug 5, 2019

Hello. Thanks for the explanation. My ProcMon log can be found at Files shared via Tresorit

Sysnative Windows Update · Aug 5, 2019

Can you please run DISM?

HapaxOromenon · Aug 5, 2019

Hello. DISM completed successfully and I attach my CBS log.

Sysnative Windows Update · Aug 5, 2019

Please go to services.msc (type that into the Run box) and check whether the Windows Module Installer service is running.

HapaxOromenon · Aug 5, 2019

Hello. The Windows Modules Installer service is currently running.

Sysnative Windows Update · Aug 5, 2019

Can you tell me which update fails and does it fail with an error code, as in do you get this in the Windows Update section itself or over reboot?

HapaxOromenon · Aug 5, 2019

Hello. It's the latest cumulative update, KB4505903. Within Settings -> Update & Security -> Windows Update, it appears under "Additional updates available", and I click "Download and install now". The text at the top changes to "Checking for updates", then "Updates are available". Underneath that it says "2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4505903)", and "Status: Getting things ready". This then changes to "Status: Installing 0%", "Status: Installing 12%", etc. Eventually it gets to "Status: Installing 100%" and stays there for a few seconds. Then the text changes to say "There were problems installing some updates, but we'll try again later", and below that it says "2019-07 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4505903) -Error 0x800f0982", with a button underneath saying "Retry". I hope this fully answers your question.

Sysnative Windows Update · Aug 5, 2019

What security software are you using?

HapaxOromenon · Aug 5, 2019

Hello. I am using Kaspersky Internet Security 2020. I also occasionally run a manual scan with HitmanPro.

Sysnative Windows Update · Aug 5, 2019

Please temporarily disable Kaspersky and retry the installation. You may need to temporarily remove it from the system.

HapaxOromenon · Aug 5, 2019

Hello. I uninstalled Kaspersky from Settings -> Apps, and followed it up with Kaspersky's special uninstall tool (kavremover) to get rid of any traces that were left. I then tried the update and it failed in exactly the same way as before. The entire sequence of events was precisely the same as I described in post #28. So, since Kaspersky doesn't seem to be the problem, and I didn't want to leave myself unprotected, I went ahead and reinstalled it now.

Sysnative Windows Update · Aug 5, 2019

Okay, thank you for testing. Please try booting your system in Clean Boot mode and retrying from there: https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

HapaxOromenon · Aug 5, 2019

Hello. I disabled all startup items and non-Microsoft services as instructed in the link, then rebooted. When I tried the update this time, it failed in exactly the same way as before. Therefore I followed the instructions to now re-enable all my startup items and services.

Sysnative Windows Update · Aug 6, 2019

Okay. Can you please get me a fresh ProcMon capture just like you have done before? Thank you

HapaxOromenon · Aug 6, 2019

Hello. My ProcMon log can be found at Files shared via Tresorit. Since the last recorded operations seem to be writing to CBS.log, I've also attached that. Finally, if I might add an observation of my own, the CBS log seems to show errors like "0000002f (F) Can not identify matching versions for component Microsoft-PPIProjection.AppxMain, version 10.0.18362.267, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]", and I did notice that your previous fix for PPIProjection contained files of version 10.0.18362.267, whereas I'm actually still on version 10.0.18362.239 precisely because I haven't been able to install this cumulative update. Do you think this could explain why the fixes so far haven't helped?

Sysnative Windows Update · Aug 6, 2019

Thank you.

No, because I prepare the fixes based on what your logs tell me. I don't manually pick versions in order not to make an inadvertent mistake.

Sysnative Windows Update · Aug 7, 2019

FRST Registry Search
1. Click your Start button and type in cmd. Press Enter.
2. Copy paste the following into the Command Prompt:

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

3. 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.
4. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
5. Copy and paste microsoft-p..-deployment_31bf3856ad364e35_10.0.18362.267_21cebd177486d59c into the Search box and click the Search Registry button.
6. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

HapaxOromenon · Aug 7, 2019

Hello. The resulting SearchReg.txt is attached. Also, Steps 1-2 of your instructions need amending, since the command only seems to work if you right-click Command Prompt and Run as Administrator. When I tried to run the 'reg load' command in a normal (unelevated) command prompt, I got an error: "The requested privilege is not held by the client".

Sysnative Windows Update · Aug 7, 2019

Interesting. Thanks for the feedback.

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.

[SOLVED] WU error 0x800f0982, but SFCFix found no corruptions

Inactive

Well-known member

Inactive

Well-known member

Attachments

Inactive

Well-known member

Inactive

Well-known member

Inactive

Well-known member

Inactive

Well-known member

Inactive

Well-known member

Inactive

Well-known member

Attachments

Inactive

Inactive

Well-known member

Attachments

Inactive

Attachments