Errors on installing KB4517389 and KB2267602 on Windows 10 Pro FR

pyhair

pyhair

Member
Joined
Apr 27, 2015
Posts
19
Hello,

After having some files corrupted and BSOD on boot, I managed to boot again with the help of a clean install on a secondary drive and a bootable USB stick. However some corruptions remain. One error is on Windows Update.

I spent days trying to fix with sft /scannow, dism with many options, downloaded iso, extracted and mounted wim files, dism /RestoreHealth online and offline, with and without source, from the wim, from the secondary install, from a command shell in repair mode and from the shell of my secondary install (with internet access). Now I'm at the end of what I can do and I need your help to go further. Windows is working but updates don't install, I need to fix it.

Here are the errors I get in the Windows Update panel:

2019-10 Mise à jour cumulative pour Windows 10 Version 1903 pour les systèmes x64 (KB4517389) - Erreur 0x80070002

Mise à jour intelligente de la sécurité pour Windows Defender Antivirus - KB2267602 (version 1.303.1437.0) - Erreur 0x80070643


I ran SFC scan twice as the first one reported to reboot. The second after reboot.

Here are the logs: CBS Logs (link valid 30 days)


The SFCFix report:

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-10-11 15:47:26.134
Microsoft Windows 10 Build 18362 - 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-10-11 15:57:55.808
----------------------EOF-----------------------


Thank you for your help fixing this box.

Regards
Pyhair
 
Hi,

Thank your for having a look. I don't think the drive broke down. I ran chkdsk which didn't find any problem.

The corruption came after I disconnected a harddisk I had to connect to clean. Everything was fine until I disconnected it and the next boot. I don't explain what happened. Maybe a virus, but scan found nothing.

Now that Windows is booting again, I'd rather not reinstall everything, if repairable.

What do you mean by "this was likely a clone" ?
 
I managed to boot again with the help of a clean install on a secondary drive and a bootable USB stick.
Click to expand...

Could you clarify where did you get a BSOD and where your OS is located now? Based on the state of the system, it's unlikely that the logs came from a system that was freshly installed.
 
Could you clarify where did you get a BSOD and where your OS is located now? Based on the state of the system, it's unlikely that the logs came from a system that was freshly installed.
Click to expand...

Sorry, I was not clear. The secondary drive on which in installed a temporary fresh Win 10 helped to acces the files and operate offline on the broken one without booting on the slow DVD-R.

The BSOD was on the broken Windows. There is no more BSOD now. I copied some files, or renamed them (using the clean system or the recovery console) until the broken could start again. It starts, but Windows update does not work. Some system files are still not correct. Not essential to boot, but preventing Windows Update to function properly.

The logs come from the broken-semi-repaired system. Not the freshly installed. I don't want to keep the freshly temporary installed system. I'd like to repair the one I generated and sent the logs from. Everything I sent was from the old system I want to repair, which can boot and is on C:\
 
Ahhh, I understand now.

Given the state of logs, I'd like to verify the state of the drive:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
"Test #","Type","Status","% Completed","Lifetime hours","LBA of the first error"
1,"Extended offline","Completed without error","100%","5323","-"

Attributes have nothing pink or red

"ID","Name","Failed","Norm-ed value","Worst","Threshold","Raw value","Type","Flags"
5,"Reallocated Sector Count","never","100","100","10","0","<b>pre-failure</b>","PO--CK"
9,"Power-On Time","never","98","98","0","5323","old age","-O--CK"
12,"Power Cycle Count","never","98","98","0","1911","old age","-O--CK"
177,"Wear Leveling Count","never","96","96","0","64","<b>pre-failure</b>","PO--C-"
179,"Used Reserved Block Count (Total)","never","100","100","10","0","<b>pre-failure</b>","PO--C-"
181,"Program Fail Count","never","100","100","10","0","old age","-O--CK"
182,"Erase Fail Count","never","100","100","10","0","old age","-O--CK"
183,"Runtime Bad Blocks","never","100","100","10","0","<b>pre-failure</b>","PO--C-"
187,"Reported Uncorrectable","never","100","100","0","0","old age","-O--CK"
190,"Airflow Temperature","never","61","50","0","39","old age","-O--CK"
195,"Hardware ECC Recovered","never","200","200","0","0","old age","-O-RC-"
199,"CRC Error Count","never","100","100","0","0","old age","-OSRCK"
235,"POR Recovery Count","never","99","99","0","14","old age","-O--C-"
241,"Total LBAs Written","never","99","99","0","25077058532","old age","-O--CK"
 
Hi,

Yes, I did remove Avast and retried repair install, but still failed.

I guess we are at the end of what can be done in BSOD section.

Do you think you can help fixing the error preventing a repair install ?
 
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