[SOLVED] [7SP1 x64] KB4048597 fails to install
- Thread starter rob0v
- Start date
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
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.
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.
Re: [W7SP1 x64] KB4048597 fails to install
The script failed at the first attempt, but succeeded at the 2nd attempt; output from both scripts below. I'm now re-trying install of updates.
The script failed at the first attempt, but succeeded at the 2nd attempt; output from both scripts below. I'm now re-trying install of updates.
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-12-05 18:11:14.802
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\b\Desktop\SFCFixScript.txt [1]
RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ucrt_31bf3856ad364e35_6.1.7601.23656_none_ae28cf5190fe7811.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2017-12-05 18:11:15.301
Script hash: BRw69+JqsFsIJRVvTzFtLMQYNSwq+PDN4ixBdTx5aB0=
----------------------EOF-----------------------Re: [W7SP1 x64] KB4048597 fails to install
I attempted WU install of KB4048957 and it failed again.
Uploaded cbs.log
Your patience in helping repair my WUs is legendary, but this process seems endless! I am wondering if it's worth biting the bullet and re-installing Windows from zero. Are there any indications that we are reaching the end?
I attempted WU install of KB4048957 and it failed again.
Uploaded cbs.log
Your patience in helping repair my WUs is legendary, but this process seems endless! I am wondering if it's worth biting the bullet and re-installing Windows from zero. Are there any indications that we are reaching the end?
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
You know the drill.
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.
You know the drill.
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.
Re: [W7SP1 x64] KB4048597 fails to install
The script failed at the first attempt, but succeeded at the 2nd attempt; output from both scripts below. I'm now re-trying install of updates.
Your patience in helping repair my WUs is legendary, but this process seems endless! I am wondering if it's worth biting the bullet and re-installing Windows from zero. Are there any indications that we are reaching the end?
The script failed at the first attempt, but succeeded at the 2nd attempt; output from both scripts below. I'm now re-trying install of updates.
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-12-05 19:04:14.799
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\b\Desktop\SFCFixScript.txt [1]
RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-u..rsalcrt-apifwd-win7_31bf3856ad364e35_6.1.7601.23656_none_aa4830af3e29a3af.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2017-12-05 19:04:14.939
Script hash: iKVqGnNJzddtTnmFGhhAWdt79NkEiUMoVWWTeOV66/g=
----------------------EOF-----------------------Your patience in helping repair my WUs is legendary, but this process seems endless! I am wondering if it's worth biting the bullet and re-installing Windows from zero. Are there any indications that we are reaching the end?
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
Thank you for the kind words. I really can't tell at this point. It could be 1 more and it could be 10 more. We'll just have to try and see :) Go ahead with Windows Update now and let me know if successful. If not, CBS.log please.
Thank you for the kind words. I really can't tell at this point. It could be 1 more and it could be 10 more. We'll just have to try and see :) Go ahead with Windows Update now and let me know if successful. If not, CBS.log please.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
Okay, we've made some progress. Time to try this again. Please try just once.
[W7SP1 x64] KB4048597 fails to install
Okay, we've made some progress. Time to try this again. Please try just once.
[W7SP1 x64] KB4048597 fails to install
Re: [W7SP1 x64] KB4048597 fails to install
The DISM install failed with below output. Uploaded zipped cbs.log and dsim.log files.
The DISM install failed with below output. Uploaded zipped cbs.log and dsim.log files.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\temp
C:\temp>DISM.exe /Online /Add-Package /PackagePath:C:\temp\Windows6.1-KB4048957-
x64.cab
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~
~7601.23934.1.2
[==========================100.0%========================= ]
An error occurred - Package_for_RollupFix Error: 0x800736b3
Error: 14003
The referenced assembly is not installed on your system.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.logSysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and try to install the update 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 attach the LogFile.PML file as well as your CBS.log
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and try to install the update 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 attach the LogFile.PML file as well as your CBS.log
Re: [W7SP1 x64] KB4048597 fails to install
CBS and DISM logs attached. Procmon Logfile is on its way, but will take a while to upload.
View attachment CBS & DISM 20171206-1445.zip
CBS and DISM logs attached. Procmon Logfile is on its way, but will take a while to upload.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:C:\temp\Windows6.1-KB4048957-x64.cab
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23934.1.2
[==========================100.0%========================= ]
An error occurred - Package_for_RollupFix Error: 0x800736b3
Error: 14003
The referenced assembly is not installed on your system.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.logRe: [W7SP1 x64] KB4048597 fails to install
I left the default filters when I saved the Procmon Logfile (~70% of events). Let me know if you need All Events and I'll send again.
I left the default filters when I saved the Procmon Logfile (~70% of events). Let me know if you need All Events and I'll send again.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
Retrieve Components/Software Hives
Note: The Software hive has confidential and sensitive information in it so please send me a PM with a link to that particular hive so it's not in the public form.
Note: The Software hive has confidential and sensitive information in it so please send me a PM with a link to that particular hive so it's not in the public form.
- Please download the Freeware RegBak from here: Acelogix Software - Download products
You will find it at the bottom of the page that the link brings you to. - Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
- Click the New Backup button. Accept the defaults and simply click Start.
- When it says Finished successfully, click the Close button.
- This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
- This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, two of which are named COMPONENTS and SOFTWARE.
- Copy these two files to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
- Now right click on these files on your desktop and select Send to > Compressed (zipped) folder.
- Then please upload the zip file(s) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are One Drive or SendSpace and then just provide the link in the PM.
- You can close any open windows you have as well as the RegBack program now.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Re: [W7SP1 x64] KB4048597 fails to install
Remove Update Manually
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 command into it, press enter
wusa /uninstall /KB:4015549
If there's an error, or a message that the update is not installed, please do a registry scan for the update with FRST and provide SearchReg.txt
Remove Update Manually
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 command into it, press enter
wusa /uninstall /KB:4015549
If there's an error, or a message that the update is not installed, please do a registry scan for the update with FRST and provide SearchReg.txt
The wusa uninstall failed; upload to zipped cbs & dism logs
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Search with Farbar Recovery Scan Tool (FRST)
- Download FRST64 and save it to the Desktop.
- Open the Command Prompt as Administrator (Tutorial)
- Type or copy/paste the following command:
Code:
dism /online /Get-FeatureInfo /FeatureName:TFTP|find "completed"- Wait for the command to finish with "The operation completed successfully"
- Close the window "Administrator: Command Prompt"
- Execute FRST/FRST64 right click on the icon and choose Run as Administrator. Make sure all other windows are closed.
(When the tool opens for the first time, you must click Yes on the disclaimer.)
- On the Search box (1) type or copy and paste the following text:
KB4015549 - Press the Search Registry button.
- Wait for the search to finish FRST will produce a log called (SearchReg.txt) in the same directory the Tool is run from.
- Please attach the log to your post.
FRST64 registry search successfully completed:
View attachment SearchReg.txt
View attachment SearchReg.txt
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
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.
Afterwards, try updating again and attach CBS.log if it fails.
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.
Afterwards, try updating again and attach CBS.log if it fails.
Has Sysnative Forums helped you? Please consider donating to help us support the site!