Windows Update fail on installing KB4054518 (windows 7)

No, I do not have any exotic devices. It's a normal PC for games and office-like work.
I have my screen, wired mouse, wireless keyboard and an E-sata drive for backup.
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install KB4054518 just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to SendSpace and provide a link for me to download.
 
Hello again at that late hour (I won't last long I think ^^;;)

I ran the above procedure.
I uploaded on dl.free.fr because "sendspace" it super slow :
​
DL.FREE.FR

Good luck with those humongous files ...
 
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.
 

Attachments

Command Prompt

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 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, one by one, pressing enter after each

    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
 
mmmh ....

the del command says the files cannot be accessed because in use (sorry it's in french)

C:\Windows\system32>del %SystemRoot%\System32\Config\TxR\*
C:\Windows\System32\Config\TxR\*, êtes-vous sûr (O/N) ? o
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.0.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.1.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.2.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.3.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.4.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cc-6c6f-11de-8d1d-001e0bcde3ec}.TxR.blf
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TM.blf
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000001.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
C:\Windows\System32\Config\TxR\{016888cd-6c6f-11de-8d1d-001e0bcde3ec}.TMContainer00000000000000000002.regtrans-ms
Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.
 
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.
 

Attachments

Here is the log file :

Fix result of Farbar Recovery Scan Tool (x64) Version: 24.10.2018Ran by shadax (06-11-2018 20:43:15) Run:2
Running from C:\Users\shadax\Desktop
Loaded Profiles: shadax (Available Profiles: shadax)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: fsutil resource setautoreset true %SystemDrive%\
cmd: attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
cmd: del %SystemRoot%\System32\Config\TxR\*
cmd: attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
cmd: del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
cmd: del %SystemRoot%\System32\SMI\Store\Machine\*.blf
cmd: del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms
*****************


Error: (0) Failed to create a restore point.


========= fsutil resource setautoreset true %SystemDrive%\ =========


Op‚ration r‚ussie.


========= End of CMD: =========




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




========= End of CMD: =========




========= del %SystemRoot%\System32\Config\TxR\* =========


C:\Windows\System32\Config\TxR\*, ˆtes-vous s–r (O/N)ÿ? Y
C:\Windows\System32\Config\TxR\*, ˆtes-vous s–r (O/N)ÿ?


========= End of CMD: =========




========= attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* =========




========= End of CMD: =========




========= del %SystemRoot%\System32\SMI\Store\Machine\*.tm* =========




========= End of CMD: =========




========= del %SystemRoot%\System32\SMI\Store\Machine\*.blf =========


Impossible de trouver C:\Windows\System32\SMI\Store\Machine\*.blf


========= End of CMD: =========




========= del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms =========


Impossible de trouver C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms


========= End of CMD: =========




==== End of Fixlog 20:43:15 ====
Click to expand...
 
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