[SOLVED] Failed update KB4471318

BelCraig · Dec 16, 2018

Hi Guys,
My Machine seems to be having a problem installing the security Monthly Quality Rollups'

My Machine failed to install 2018-11 (KB4467107) - Never installed.
It's now on 2018-12 (KB4471318) and again is failing to install.
This process is sending the computer into a loop. When I go to shut down it only allows me to shutdown and install updates. Each time windows boots it goes to install the updates and the rolls back because the update failed.
I tried various solutions on the internet from resetting my network adaptor to downloading the package from the download centre to install on its own. But all of these had failed. I stumbled on this forum and hope someone here can help me.

In running Windows 7 Professional (SP1) (x64).
I've followed the instructions in another post on this forum

Step 4 - SFCFIX

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-16 12:19:51.446
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
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: 16
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-12-16 15:54:13.421

Step 5: CBS LOG file added here
https://1drv.ms/u/s!An728nlinYyEha8zE0O4HxAIozfXeA

Sysnative Windows Update · Dec 17, 2018

Hello and welcome!

Please attach C:\Windows\Inf\setupapi.dev.log.

BelCraig · Dec 18, 2018

I've potentially got two that fits the bill,

I've placed them both and I've kept the original file names so you can see.

https://1drv.ms/f/s!An728nlinYyEha9tAOa5nhd-72axZg

Many Thanks in advance for your help

Craig

Sysnative Windows Update · Dec 18, 2018

Are there exclamation marks in your Device Manager?

BelCraig · Dec 20, 2018

There was one, but this was simple settled by unplugging my keyboard and reinserting it. I've since restarted the PC and the update failed and there are now no errors in the device manager.

Sysnative Windows Update · Dec 20, 2018

Can I see both CBS.log and setupapi.dev.log after the latest attempt?

BelCraig · Dec 23, 2018

Sorry for the delayed reply...
Please see link above for new files, old files have been moved into OLD folder. as of copying the were no triangles in the device managers

Sysnative Windows Update · Dec 24, 2018

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

BelCraig · Dec 26, 2018

Here is the log report

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2018-12-27 00:20:05.048
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Craig\Desktop\SFCFixScript.txt [0]
 

FileScan::
[0: 2] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7600.16385_none_b93f4c460912265a\cpu.inf
 Expected: xo7oBiuSHbHnmUzSEsmUr3BXHH51621TRxSC8+KAJ10=
 Expected: 6.1.7600.16385 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7600.16385_none_b93f4c460912265a with return code -2.
 [C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_neutral_ae5de2e1bf2793c3\cpu.inf]

[1: 1] C:\Windows\inf\cpu.inf
File is untraceable.
 Found: rRKGXKXPzj8aIeFZBQfB8vdMJ9jN9/0jKdTeKKsZScw=
 Version number not available.
Trace not available.
 
[2: 1] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24214_none_bbf9b0e91f1ea205\cpu.inf
 Expected: xhSfTyqXd86Il5mEXa3Oj1+Xb+ayJwf643YzYBv/sIM=
 Expected: 6.1.7601.24214 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24214_none_bbf9b0e91f1ea205 with return code -2.
 
[3: 1] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24231_none_bbe110331f318de2\cpu.inf
 Expected: C6hpPVNrc2PWdea7V1R+QGW9hrH9l3xSMwHj4PUwK2Q=
 Expected: 6.1.7601.24231 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24231_none_bbe110331f318de2 with return code -2.
 
[4: 2] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24260_none_bbbfa0251f4ac85e\cpu.inf
 Expected: rRKGXKXPzj8aIeFZBQfB8vdMJ9jN9/0jKdTeKKsZScw=
 Expected: 6.1.7601.24260 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24260_none_bbbfa0251f4ac85e with return code -2.
 [C:\Windows\System32\DriverStore\FileRepository\cpu.inf_amd64_neutral_f64f7a1c5164e4e5\cpu.inf]

[5: 1] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24291_none_bba030ab1f623588\cpu.inf
 Expected: Bds/BzPBG0ky2/fl8EpFxVEVNvnV8ML8WEJ9ETRpl6M=
 Expected: 6.1.7601.24291 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24291_none_bba030ab1f623588 with return code -2.
 
[6: 1] C:\Windows\winsxs\amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24308_none_bc0883e31f12e897\cpu.inf
 Expected: xJA+pSCtTcYlgLaidR/ocOCT4a0QYqqEqISujzSA0aw=
 Expected: 6.1.7601.24308 Found: Version number not available.
Failed to trace component amd64_cpu.inf_31bf3856ad364e35_6.1.7601.24308_none_bc0883e31f12e897 with return code -2.
FileScan:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-12-27 00:20:39.278
Script hash: DHmGwoIvVsk71pU7RC7VEQ9dhAUERVG4bMejZI/JqYM=

thanks

Sysnative Windows Update · Dec 30, 2018

Please temporarily uninstall your antivirus software and retry updates.

BelCraig · Jan 1, 2019

Hi I removed my virus software and attempted to install the updates. I've attached the logs in the links above.

thanks

Craig

Sysnative Windows Update · Jan 3, 2019

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.

BelCraig · Jan 3, 2019

View attachment Fixlog.txt

regards craig

Sysnative Windows Update · Jan 3, 2019

Please attempt updating and attach CBS and setupapi.dev.log if it fails.

BelCraig · Jan 5, 2019

Sorry meant to reply that I had put the new files in the link above. I've updated them this morning

thanks for your continued help!

Sysnative Windows Update · Jan 5, 2019

Step#1 - Export registry as hive

Click on the Start button and in the search box, type regedit
When you see regedit on the list, right-click on it and select Run as administrator.
When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (*.*).
Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
Attach the .ZIP file to your next post.
If the file is too large to upload here, upload to SendSpace and just provide the link here.

BelCraig · Jan 5, 2019

File added to link above.

Sysnative Windows Update · Jan 5, 2019

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.

BelCraig · Jan 6, 2019

Still unsuccessful

Files added to link at top

Sysnative Windows Update · Jan 6, 2019

Step#1 - FRST Scan

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. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

[SOLVED] Failed update KB4471318

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Attachments

Member

Inactive

Member

Inactive

Attachments

Member

Inactive

Member

Inactive

Member

Inactive

Attachments

Member

Inactive