Windows 10 update return 0x80245006

[kha]

Hello,

I/m trying to update a Windows 10 Pro version 1809 build 17764.805 machine but I receive this message:
There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80245006)

After looking on internet and trying different solutions I end up on this forum.

Run sfc:
Checking CheckSUR.persist.log . . . Attempting repair . . . Stage 1 Stage 2 Stage 3 Due to the nature of your corruptions, scan times have been extended by approximately 15-20 minutes. Please be patient and allow the operation to complete. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.17763.805 [===========================83.4%================ ] Error: 0x80245006 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


Running SFCFix return at one point this:
Checking CheckSUR.persist.log . . . Attempting repair . . . Stage 1 Stage 2 Stage 3 Due to the nature of your corruptions, scan times have been extended by approximately 15-20 minutes. Please be patient and allow the operation to complete. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.17763.805 [===========================83.4%================ ] Error: 0x80245006 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Checking for updates . . . No new update is available at this time. Processing directive 1 of 1 (AutoAnalysis::) Checking store directories . . . Checking CBS.log . . . Checking CBS.persist.log . . . Checking CheckSUR.log . . . Checking CheckSUR.persist.log . . . Attempting repair . . . Stage 1 Stage 2 Stage 3 SUMMARY: CBS & SFC total detected corruption count: 0 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 Press any key to continue to explanation of summary . . . --- Displaying Message 1 of 1 --- No corruptions have been detected on this computer. Whilst this is a good thing,be aware that not all types of corruption can be detected by this tool. Therefore, if you are currently experiencing continued problems with your computer it is likely that you are going to need the assistance of a human analyst in order to find and fix them. If your problems persist, and you are currently being instructed by a helper, you should let them know about this development by sending them the logfile which will soon be generated and opened so that they can perform a manual fix. If you are not currently being instructed by a helper but still need assistance,you should seek free advice from your favourite forum or sysnative.com. Create anew thread and provide this logfile in the first post of that thread along with a complete description of the problems you were experiencing which led you to run this tool. * Press any key to continue . . . --- Displaying Message 1 of 1 --- No corruptions have been detected on this computer. Whilst this is a good thing,be aware that not all types of corruption can be detected by this tool. Therefore, if you are currently experiencing continued problems with your computer it is likely that you are going to need the assistance of a human analyst in order to find and fix them. If your problems persist, and you are currently being instructed by a helper, you should let them know about this development by sending them the logfile which will soon be generated and opened so that they can perform a manual fix. If you are not currently being instructed by a helper but still need assistance,you should seek free advice from your favourite forum or sysnative.com. Create anew thread and provide this logfile in the first post of that thread along with a complete description of the problems you were experiencing which led you to run this tool. * Press any key to continue . . .


The log file is:
SFCFix version 3.0.2.1 by niemiro. Start time: 2020-01-22 22:29:10.671 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. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2020-01-22 22:52:07.351 ----------------------EOF-----------------------

I put the logs here
win10 - Google Drive

Thanks for assistance.

 

[Sysnative Windows Update]

Hi!

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.

 

[kha]

After I talked with a few colleagues I find out that an application installed on all computers in the company blocks the updates, the app in question is bitglass.
I stopped it's service and removed the associated script in Settigns->Proxy. Some updates (windows defender) were installed, but updates for version 1809 failed to install.
sfc/scannow showed some errors in the logs which I couldn't fix with dism. At this point SFCFix started to crash and was unusable.
dism couldn't fix the issue because the ISO created with MediaCreationTool was newer than what it was installed and couldn't find the files at that version, they were newer in the ISO.

On some forums it was suggested to install .NET Framework 3.5, I did that using dism and the ISO created. Still no luck with sfc and dism.
After I rebooted the machine I stopped the bitglass service and removed the script in proxy. Today, while browsing the net, a message popped up and notified me that I have an update ready to install, this time it was a newer Windows version (1903). The files were downloaded, at reboot hanged. Stopped the computer from button and on power up the installation starts. A few reboots later and Windows starts.

Run sfc and found something, but it was repairable.

Now, I'm going to create an ISO with MediaCreationTool to have the exact same version available in case some files we'll be corrupted again.

 

[Sysnative Windows Update]

Thanks for letting me know.