Windows update fails on Cumulative updates only with Error 0x80070246

[Mitchster]

Dear Sysnative

Windows 10 1809 - since update in November have been unable to update with the Cumulative updates last one KB4480116, and the 2018-12, version of the same.

Have followed your instructions and the SFC came up clear
DISM -came up with the following error
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]Deployment Image Servicing and Management tool
Version: 10.0.17763.1[/FONT]
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]Image Version: 10.0.17763.134[/FONT]
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif][==== 7.5% ]
Error: 14090[/FONT]
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]The value of an attribute in an identity is not within the legal range.[/FONT]
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log[/FONT]
The Clean up would not go beyond this error.
Have attached the CBS Log.

Have independently tried everything, with regards to Windows store, standard troubleshooting of Windows updates, resetting windows update components.
I did have a new SSD drive in November and I am convinced that a driver or similar is causing the issue.

Would so appreciate some advice.
Best
Mitchster

 

[softwaremaniac]

Hello and welcome!

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.

 

[Mitchster]

Please see link to my OneDrive [FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]https://stcyprians-my.sharepoint.com/:u:/g/personal/mitchells_stcyprians_co_za/EZtd9_PpIcpCkj8KbeOEPsoBN7XxB4nJEdnj6DXzTJkjqQ?e=mISbhW

Thanks
Mitchster
[/FONT]

 

[softwaremaniac]

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 attached file 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.
6. Try updates and if any fail, attach CBS.log.

 

[Mitchster]

HI There

Have done as requested - update now will not respond at all now!
have attached fixlog and CBS, am doing another restart now!

Thanks
Mitchster

 

[Mitchster]

HI There

Have done as requested - update now will not respond at all now!
have attached fixlog and CBS, am doing another restart now!

Thanks
Mitchster

 

[Mitchster]

View attachment CBS (3).zip Have reset windows update components and update ran and failed again
Have included a 3rd CBS log

Thanks Mitchster

 

[softwaremaniac]

Thanks. There's more corruption:

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 attached file 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.
6. Try updates and if any fail, attach CBS.log.

 

[Mitchster]

Hi Sysnative

Now getting "Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712)"

HAve attached CBS (4)

Thanks
Mitchster

Thanks. There's more corruption:

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 attached file 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.
6. Try updates and if any fail, attach CBS.log.

 

[softwaremaniac]

Has the RAM on this machine been tested? If not, please test it out.

 

[Mitchster]

Have just tested the RAM all good.
IS it a lost cause?

Best
Mitchster

Dear Sysnative

Windows 10 1809 - since update in November have been unable to update with the Cumulative updates last one KB4480116, and the 2018-12, version of the same.

Have followed your instructions and the SFC came up clear
DISM -came up with the following error
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.134
[==== 7.5% ]
Error: 14090
The value of an attribute in an identity is not within the legal range.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
The Clean up would not go beyond this error.
Have attached the CBS Log.

Have independently tried everything, with regards to Windows store, standard troubleshooting of Windows updates, resetting windows update components.
I did have a new SSD drive in November and I am convinced that a driver or similar is causing the issue.

Would so appreciate some advice.
Best
Mitchster

 

[softwaremaniac]

You can't have tested the RAM this quickly. The RAM is tested with Memtest86 which is run from boot mode and lasts several hours.

We can fix this, but I want to ensure there is no memory corruption on the machine.

 

[Mitchster]

Hi There

I have run Memtest86 in boot mode - all clear - see screen shot.

thanks Mitchster

You can't have tested the RAM this quickly. The RAM is tested with Memtest86 which is run from boot mode and lasts several hours.

We can fix this, but I want to ensure there is no memory corruption on the machine.

 

[softwaremaniac]

I don't see it. Please retry.

 

[Mitchster]

I don't see it. Please retry.

have re upload screenshoot

have uploaded again now, sorry

 

[softwaremaniac]

Thanks! 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 installing the update 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 attach the LogFile.PML file as well as your CBS.log

 

[Mitchster]

Hi Sysnative

Here is link to oneDrive
with Procman log and CBS.

Also worth seeing the update comes up twice, see screenshot,

 

[softwaremaniac]

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 attached file 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).

1. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
2. 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.
3. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
4. Try updates and if any fail, attach CBS.log.

 

[Mitchster]

Still same errors, fixlog and CBS in compressed file in One Drive.

Thanks
Mitchster

 

[softwaremaniac]

Can I get a fresh copy of your COMPONENTS hive as well as ProcMon log during failure?