[SOLVED] Windows Update error 0x80070246

S

supportit

Member
Joined
Jun 4, 2020
Posts
8
Hello there,
we have a domaincontroller running on Windows Server 2016 which has a problem with Windows Updates. I searched for the problem and in all this I found this forum and saw some great answers from you.
So hopefully you can help me (we are using a German version, so sorry if I can't type the exact English errors).

If I install Windows Updates, I get the error 0x80070246. I tried the usual fix for Windows Updates, stopping the service, renaming the SoftwareDistribution folder, restarting service, searching again, sadly the same error.

running sfc /scanow directly results in an error, it doesn't even try fo fix it.
various dism commands result in an "illegal charackter error" and a restorehealth stops at 4,5 %
The system was rebooted and the errors are still there.

If I run the SFCFix.exe straight as-is it isn't able to complete, I waited to about 40 minutes. Then I pressed the enter key and the programm finishes with 0 errors.

Because this is the only domaincontroller and also Fileserver, there is no good way to just reinstall it.

So here are a few files you might need, I used the Instructions post as reference.

SFCFix.txt on Desktop after the script ran:

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-05 00:00:45.451
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-06-05 00:26:52.295
----------------------EOF-----------------------


And please have a look at the CBS.zip and the dism.log in the attachment. I renamed the logs prior to all the fixing, so that it creates fresh ones.

Thank you very much in advance.

- Max
 

Attachments

Hi!
Thank you for your reply.

Yes, actually, kind of. The Server is virtualized on a Proxmox Host (with ZFS, no Hardware-RAID). There we had not enough RAM so we bought a new pair with more RAM and gave the machine more RAM. We have not tested the memory though, it did just work. Do you think that might be a problen? I just noticed that the Test only ran for 26 minutes (not 40 as I stated) but if felt like more ;)

Thanks!
 
Hi,
okay. We will try that somehow. Actually, I just remebered that I think we had the problems already, before upgradeing the RAM. So in case the faulty RAM did cause this error, how might we able to fix it? I will scedule the RAM test anyway, just want to know how we could repair it. I have 2 weeks of vacation, after that I will try to find time where we can run it. It's 32 GB so it might take a while.

Thanks again!
 
Hi!

I'd need some diagnostic logs first to check them:

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.
 
Hello guys,
so I ran the procmon and stopped capturing right after the Windows Update error-ed out. Is it correct that the PML file is almost 3 GB big?
I used 7zip to compress it together with the CBS.log with "ultra" settings. I got it compressed to about 85 MB though.
Please have a look: sysnative_pcmon.7z (85.55MB) - SendSpace.com

Thanks in advance!
 
Hi!

Hope you had a nice vacation.

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

Hi,
thank you, yeah, vacations are always nice ;)
I will try this fix later today, thanks.

Greetings
 
Hi,
I was able to run the tool. That's the fixlog:

Code: 
Entfernungsergebnis von Farbar Recovery Scan Tool (x64) Version: 24-06-2020
durchgeführt von update (25-06-2020 00:32:31) Run:1
Gestartet von C:\Users\update\Desktop\sysnative
Geladene Profile: Medistar & isamservice & update & support-it &
Start-Modus: Normal
==============================================

fixlist Inhalt:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKLM\COMPONENTS\DerivedData\Components\amd64_2a996118f5d367f2e2357953c2c068b4_31bf3856ad364e35_10.0.14393.1770_none_da5e365ea3857638]
*****************

Fehler: (0) Erstellen eines Wiederherstellungspunktes gescheitert.

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

Der Vorgang wurde erfolgreich beendet.


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

HKLM\COMPONENTS\DerivedData\Components\amd64_2a996118f5d367f2e2357953c2c068b4_31bf3856ad364e35_10.0.14393.1770_none_da5e365ea3857638 => erfolgreich entfernt

==== Ende von Fixlog 00:32:32 ====
It basically states that it succesfully removed the component stated in the txt. Should that fix the issue or is there anything else I could do before testing RAM?

Thanks in advance!
 
Hi!

You can retry updates with Process Monitor enabled again, so I can check it, but yes, testing RAM is definitely something to be done.

P.S. I can read German results just fine. :-)
 
Hi again!
I have great news, I was actually able to install windows Updates without any error, that's fantastic!
So what did go wrong? Was there registry corruption that Windows itself wasn't able to fix?

Thank you very much! I will do the RAM test eventually just to be safe, but so far this problem appears to be fixed.
Thanks again!

Best regards
 
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