Cannot install KB3023266 and subsequent Windows updates.

H

Harold

Contributor
Joined
Feb 14, 2015
Posts
23
Location
England
Windows 7 X64

22 updates released on 10th December 2014 all failed to install on the first attempt (error code 80200053) but did so without my intervention the next day on the second attempt. Perhaps this was a sign of something to come.

KB3023266 (released January), failed to install despite multiple attempts. Initial installation proceeds normally. On reboot, it says "Installing Windows update". The counter gets as far as 100% before it aborts. It then retries. First error code was 80244019. I checked the appropriate services were running (Background Intelligent Trans; Windows Update - both set to automatic-delayed). This time (and since), KB3023266 failed with code 8000505 repeatedly. I

wasn't too worried about the failure of a single update to install until I found that the following updates released in February all failed to install with the code 800F0826 - which if I am correct, means that they depend on the successful installation of 3023266 for them to install. The same thing happens as with 3023266 except when several updates fail to restore, I can't access the computer for over 30 minutes whilst it tries, fails, restores settings and tries again.

Tried the following, all without success:
- SFC (run in Administrator cmd window) No errors found
- Microsoft Fixit (MicrosoftFixit50123.msi)
- WindowsUpdateDiagnostic
- System Update Readiness Tool
- Your SFCFix.exe - no errors
- Moved or deleted unnecessary temporary files in case there was a problem with a corrupted file
- Downloaded KB3023266 directly instead of via Windows Update. Also tried via Safe Mode

So I have run out of ideas. This is well beyond my modest capabilities.

Any help you can provide will be very much appreciated. A

s requested in your instructions, I prepared a copy of CBS folder, which covers the last two days of failed attempts. However, even after zipping, it is enormous - 136MB (there are 5 CbsPersist cab files in the folder) so for now, I have just uploaded the CBS.log (zipped) as it is much smaller.

SFCFix log
SFCFix version 2.4.2.1 by niemiro.
Start time: 2015-02-15 16:23:56.920
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


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


Successfully processed all directives.
SFCFix version 2.4.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-02-15 16:41:45.119
----------------------EOF-----------------------
 
Hello Harold and welcome to the forum.

Can you please post the contents of the following log:
C:\Windows\Logs\CBS\CheckSUR.persist.log

Also please run windows updates, let it fail, then upload the following two logs:

Convert CBS.log to CBS.txt

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button => Inside the search box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  2. Press Enter
  3. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Windows Update Log

  1. Click on the Start button -> Inside the search box copy and paste the following command
    cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
  2. Please go to your desktop and attach WindowsUpdate.txt to your next post
 
Thank you very much indeed for getting back to me.

Restored hidden updates.

Attempted re-installation of KB3023266. Failed with error code 80004005

Computer also attempted to install KB3031432, 3013455, 3004361. All failed with error code 80246007. BITS service is set correctly: start - Automatic (Delayed), and has started.

Attached checksur.persist.log, cbs.txt (zipped) and Windowsupdate.txt as requested.

CBS.txt is on Dropbox via https://www.dropbox.com/s/3okigs8ufl6f8h2/CBS TXT.zip?dl=0

Many thanks again.
 

Attachments

Hi,

Let's try clearing out the SoftwareDistribution folder. Your WindowsUpdate log shows that there may be an issue with the contents of that folder:
Code: 
2015-02-18    11:21:28:931    1260    1838    DnldMgr    Preparing update for install, updateId = {E4351B8D-F78B-45D9-8AFF-E36BF026445C}.203.
2015-02-18    11:21:28:931    1260    1838    Misc    FATAL: Failed to delete file \\?\C:\windows\SoftwareDistribution\Download\Install\mpsyschk.exe (hr = 80070005) after 0 retries
2015-02-18    11:21:28:947    1260    1838    DnldMgr    WARNING: Update invalid.  Error is 0x80246007.

SoftwareDistribution Rename

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.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    net stop wuauserv
    ren %SystemRoot%\SoftwareDistribution\Download DL.bak
    net start wuauserv

Regards,
Stephen
 
Dear Stephen

Many thanks for your suggestion. Funnily enough, I forgot to mention that before contacting sysnative, in case there was some clash, I actually moved all the folders out of windows\software distribution\download - which I assumed were the uninstalled updates, but not the files (which appeared to be from the successful updates), and I also moved the contents of windows\software distribution\datastore\logs.

I did as you suggested (renaming Download folder to DL) and attempted to install KB3023266. Unfortunately, again, no joy (error code 80004005).

I'm pretty sure that the problem is somewhere on this computer (settings clashing or something similar), rather than a faulty MS update, as I have a reserve computer in case of emergencies, with almost identical software setup. This also runs W7 x64 and it has installed all the updates without a problem.

Best wishes

Harold
 
Hello Harold,

80246007 - refers to the file not being downloaded, this could be from the other error we are seeing with 80004005 (KB3023266). Now this error on its own is rather odd, not much indication is given as to why this is occurring. Except this file is list over and over again bfsvc.exe.

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    FileScan::
bfsvc.exe
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Thanks
Alex
 
Hi Alex

Thank you very much for contributing to sorting this problem.

Re 80246007, the files did originally download correctly. I moved the downloads and 'hid' the updates when I was trying to sort out the problem myself. I assume that when I restored hidden updates, they didn't re-download as WUpdate 'thought' they were still on my computer. I can easily (I think) sort that. I apologise if I have made things more difficult by trying possible solutions before asking for professional help. My experience of 30 years computing is that most things can be sorted if you take the time and work through the options - although not in this case.


Have run SFCFix as instructed. Here is the contents of the text file.



Code: 
FCFix version 2.4.3.0 by niemiro.
Start time: 2015-02-19 09:52:50.965
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\HL Gordon\Desktop\SFCFixScript.txt [1]
 

FileScan::
[0: 2] C:\Windows\winsxs\amd64_microsoft-windows-b..vironment-servicing_31bf3856ad364e35_6.1.7601.17514_none_843a86a1bc33fcd1\bfsvc.exe
 Expected: ER+E4nIQUIr3XVhvbhB/VGXd/2jLhUXpMnrRrmkzftE=
 Expected: 6.1.7601.17514
Successfully traced component amd64_microsoft-windows-b..vironment-servicing_31bf3856ad364e35_6.1.7601.17514_none_843a86a1bc33fcd1.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery
 [C:\Windows\bfsvc.exe]
FileScan:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-02-19 09:52:51.574
Script hash: RWabZYnU2w3zBspBgYhkwJdnK2beoO2yfVubGUPCD0k=
----------------------EOF-----------------------
 
Hi Harold,

Re 80246007, the files did originally download correctly. I moved the downloads and 'hid' the updates when I was trying to sort out the problem myself. I assume that when I restored hidden updates, they didn't re-download as WUpdate 'thought' they were still on my computer. I can easily (I think) sort that. I apologise if I have made things more difficult by trying possible solutions before asking for professional help. My experience of 30 years computing is that most things can be sorted if you take the time and work through the options - although not in this case.
Click to expand...

No not at all, this is always the best approach to try and isolate the issue.

The file checks out, it doesn't appear to be corrupt. TBH I am not entirely sure that this file is causing this error, but as it appeared isnide the WindowsUpdate log and the CBS log, I thought it would be the first place to start.

The section inside the CBS log that this file corresponds to is:
Code: 
2015-02-18 11:29:42, Info                  CBS    Clearing HangDetect value
2015-02-18 11:29:42, Info                  CBS    Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
2015-02-18 11:29:42, Info                  CBS    WER: Generating failure report for package: Package_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0, status: 0x80004005, failure source: GC, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2015-02-18 11:29:42, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-02-18 11:29:42, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
2015-02-18 11:29:42, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
2015-02-18 11:30:06, Info                  CBS    SQM: Reporting package change completion for package: Package_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0, current: Installed Invalid, original: Staged, target: Installed, status: 0x80004005, failure source: GC, failure details: "80004005	bfsvc.exe	21	38	Install (upgrade)	Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS	", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1297, first merged sequence: 1297
2015-02-18 11:30:06, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0, session id: 142862, sample type: Standard
2015-02-18 11:30:06, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard

To me this looks like the installer failed on KB3023266, but we already knew this update was failing. So I looked a bit further into th elog and found

Code: 
2015-02-18 11:26:44, Error      [0x018007] CSI    0000004a (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]

2015-02-18 11:28:32, Info                  CSI    00000039@2015/2/18:11:28:32.01 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;374503
2015-02-18 11:28:32, Error      [0x018007] CSI    0000003a (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]
2015-02-18 11:28:51, Info                  CSI    0000003b End executing advanced installer (sequence 57)
    Completion status: S_OK 

2015-02-18 11:29:25, Info                  CSI    00000040@2015/2/18:11:29:25.462 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-AppID, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;40482259
2015-02-18 11:29:25, Info                  CSI    00000041 End executing advanced installer (sequence 59)
    Completion status: S_OK 

2015-02-18 11:29:25, Info                  CSI    00000042 Begin executing advanced installer phase 38 (0x00000026) index 21 (0x0000000000000015) (sequence 60)
    Old component: [ml:360{180},l:358{179}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.18526, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:360{180},l:358{179}]"Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2015-02-18 11:29:26, Info                  CSI    00000043 Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:f3ccf0266e4bd0011c0000006405e005} pathid: {l:16 b:f3ccf0266e4bd0011d0000006405e005} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.18526_none_36526db91b434d3f" pid: 564 starttime: 130687324965572229 (0x01d04b6dfd380e85)
2015-02-18 11:29:26, Info                  CSI    00000044 Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:7452fa266e4bd0011e0000006405e005} pathid: {l:16 b:7452fa266e4bd0011f0000006405e005} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.17514_none_365b53d91b3ce4ff" pid: 564 starttime: 130687324965572229 (0x01d04b6dfd380e85)
2015-02-18 11:29:26, Info                  CSI    00000045 Calling generic command executable (sequence 3): [20]"C:\windows\bfsvc.exe"
    CmdLine: [47]""C:\windows\bfsvc.exe" C:\windows\boot /nofonts"
2015-02-18 11:29:27, Error      [0x018009] CSI    00000046 (F) Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
    Process exit code 21 (0x00000015) resulted in success? FALSE
    Process output: [l:0 ][gle=0x80004005]
2015-02-18 11:29:27, Info                  CSI    00000047 Calling generic command executable (sequence 4): [24]"C:\windows\fveupdate.exe"
    CmdLine: [35]""C:\windows\fveupdate.exe" /memtest"
2015-02-18 11:29:29, Info                  CSI    00000048 Done with generic command 4; CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output: [l:248 [248]"BitLockerUpdate: Running.

BitLockerUpdate: Service request is for memtest.exe.

BitLockerUpdate: BitLocker Drive Encryption is not turned ON on the OS volume.

BitLockerUpdate: No servicing was performed on the OS volume.

BitLockerUpdate: Done.

"]
2015-02-18 11:29:29, Info                  CSI    00000049@2015/2/18:11:29:29.768 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-BootEnvironment-Core-MemoryDiagnostic, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;7110792
2015-02-18 11:29:29, Error      [0x018007] CSI    0000004a (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]
2015-02-18 11:29:29, Info                  CSI    0000004b End executing advanced installer (sequence 60)
    Completion status: S_OK

From what I have been able to make out of this log is the uninstaller tried to perform a rollback on the installation process, but failed:

Code: 
2015-02-18 11:26:44, Error      [0x018007] CSI    0000004a (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]

Code: 
2015-02-18 11:28:32, Error      [0x018007] CSI    0000003a (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]

First lets check to see if we can see anything that is pending:

Please navigate to C:\Windows\winsxs and copy any files with a similar name to pending.xml (e.g. pending.xml, pending.xml.bad, pending.xml_dfsadf78 etc.) to your folder on the Desktop [there may not be any, just if there are]. Then zip up this folder and attach it to your next post.

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button. Inside the search box type in CMD
  2. Right click on CMD => Choose Run as Administrator
  3. Inside the Command Prompt windows copy and paste the following command
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG QUERY HKLM\COMPONENTS >1&& notepad 1
  4. Please wait for this to Finish before continuing with rest of the steps.
Please also export the following registry keys, add them into a zip and attach to this post:

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. 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\WindowsUpdate\Auto Update

  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file Update (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or One Drive
 
Greetings Alex

Wow. This is turning into a marathon. Thank you very much for all the time you have devoted to my problem.

Answering your points:
1. winsxs folder: NO files with filename 'pending'. 15GB worth of other files!
2. 1.txt attached.
3. Couldn't attach the Reg Hive (assume it's to stop you unintentionally loading it into your registry) so available from this Dropbox link https://www.dropbox.com/s/f755ttekyh567n4/Update?dl=0

For now, I have changed Windows Update schedule to 'Never check for updates'.


Best wishes

Harold

txt.gif
1.txt (528 Bytes)
 

Attachments

  • 1.txt
    1.txt
    528 bytes · Views: 6
Hi Alex
No, it's not installed. It's one of the latest batch that didn't install. It was published on 9th February so came after my problems started.
 
Hi Harold,

Thank you for the donation :)

All that checks out, lets try and clear the pending transactions. First we will try the less aggressive method:

Boot into the Windows RE mode: How to use the Windows 7 System Recovery Environment Command Prompt

Once the command Window is displayed please follow the below steps.

First command to enter is wmic logicaldisk get name. you will be given a similar output to:

Code: 
X:\Sources>wmic logicaldisk get name
Name
C:
D:
E:
X:

Now when you are in the RE the drive letters will often move around. start with the first letter that was provided in the list and enter in the following command (for this example we will use C:\ as it is the first one)

dir C:\
-This will display all the folders in the root drive of C

Can you see a folder called C:\Windows in list?
-If you can see C:\Windows then run the DISM command as DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

If you can not see the Windows folder move onto the next Drive letter that we obtained with wmic logicaldisk get name and type in dir <DRIVE LETTER> (replace <DRIVE LETTER> with the drive you would like to check), can you see the Windows Folder?
-If yes, enter in the following command DISM /Image:C:\ /Cleanup-Image /RevertPendingActions and changed the C to what ever Drive letter has the Windows folder

Its just a case of going through each drive letter that was produced from the first list until the Windows folder is found then run the DISM command on that drive
 
No. Thank you. All of you provide an excellent service, in your own time, without remuneration, and you have immense patience with us non-experts as you guide us through the minefield that is the misbehaving computer. I very happy to say that in an open forum.

Re the latest attempt:
- System RE already loaded onto my computer (though about a year ago, I did buy a new version of W7Pro just in case something major happens and I have to do a full reinstall).
- My 'C' drive is 'D', if you know what I mean.
- Entered the code as described. Ran smoothly.
- Attempted installation of KB3023266. Went through the normal installation uneventfully, as before. Configured updates whilst shutting down, as before. On restart, configuring Windows updates - got to 80% and then failed. Reverting changes. Error code 80004005 again.

Time for plan B?

Only one other thought. I assume that 3023266 is compatible with my system?
 
Hello again,

Only one other thought. I assume that 3023266 is compatible with my system?
Click to expand...

Yes it should be, if anything appears inside Windows updates it will be compatible with your system.

Lets try this method:

First, start an Elevated Command Prompt: https://www.sysnative.com/forums/wind...vista-7-a.html
and copy and paste in the following:

fsutil resource setautoreset true %SystemDrive%\

attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
del %SystemRoot%\System32\Config\TxR\*

attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
del %SystemRoot%\System32\SMI\Store\Machine\*.blf
del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms

Restart the computer and try window updates again.
 
Thanks very much.

Lines 1 and 2
Ran fine.

Line 3
There are three files in \System32\Config\TXR.
{2000b491-b3bf-11e4-82e3-c485083926e5}.TM.blf
{2000b491-b3bf-11e4-82e3-c485083926e5}.TMContainer00000000000000000001.regtrans-ms
{2000b491-b3bf-11e4-82e3-c485083926e5}.TMContainer00000000000000000002.regtrans-ms
In all cases, I was unable to delete the files from the command line because they are currently in use (Error Message: - The process cannot access the file because it is being used by another process')

Line 5
There were no files with filetype starting tm*

Line 6
14 files with filetype blf. All deleted successfully.

Line 7
28 files with filetye regtrans-ms. All deleted successfully.

I kept copies of the files that were deleted from the command line in case they are needed again.

Attempted installation of KB3023266. Unfortunately, it failed again with the same error code (80004005).

It's possible that the three files that I couldn't delete have some bearing on this but as the error message was quite clear (file in use), I didn't want to fiddle.
 
After the above, out of interest, I tried installing some of the updates that had previously failed. I downloaded each individually. The following were successful:
3023562
3029944
3020338
3013455
3004361
3021952
3034196

The following failed:
3023266
3031432
3004375
3004394 (which I know you have mentioned on a previous occasion)
These all failed with the same error code 80004005

I then tried to run Windows Update to 'Check for Updates' but it failed with Error Code 8024402C. That was sorted by changing from wifi to LAN. I was then able to install 3006137 and 2952664 (two recent releases).

So we're part of the way there. The plot thickens!

H
 
Good work, now that we have some repaired lets take another look at the logs.

Please run Windows update again (let it fail) then provide the following logs:

Convert CBS.log to CBS.txt

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button => Inside the search box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  2. Press Enter
  3. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Windows Update Log

  1. Click on the Start button -> Inside the search box copy and paste the following command
    cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
  2. Please go to your desktop and attach WindowsUpdate.txt to your next post
 
Sorry about the delay in completing this.

WindowsUpdate.txt attached

View attachment WindowsUpdate v2.txt

cbs.txt is now enormous (347MB). Zipped version on Dropbox at https://www.dropbox.com/s/wjkzn3prvi3m77s/cbsv4_txt.zip?dl=0

When I ran WU yesterday, it offered four updates. The three I chose were 3031432; 3004375; 3004394. The first two failed with error code 80004005. The last failed with 800F0826, which I think might indicate that it can only be installed if another important update installs first. There were multiple attempts to install them, hence the large cbs log.

WU also offered me 3021952. This is an update for IE11. However, this is already installed as shown in IE (About), WU View Update History and Control Panel View installed updates. I wonder if this is because I installed 3021952 manually rather than via WU?

Finally, WU did not offer 3023266, which was the update that I originally had problems with. So I still haven't installed that one.
 
The same error is still occurring.

What security programs do you have installed?

Event Log Viewer

  1. Please download VEW.exe from Here and save it to your desktop.
  2. Go to your desktop and right click on VEW.exe and choose Run as Administrator
  3. Once open set the following settings
    • 'Select log to query'
      1. Tick Application
      2. Tick System
    • 'Select Type to list'
      1. Tick Critical
      2. Tick Error
      3. Tick Information
      4. Tick Warning
    • 'Number or date events'
      1. Tick Number of Events and set it to 20
  4. Click on Run
  5. Once completed a notepad file will open. Please copy and paste the contents of VEW.txt back into this thread.
 
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