What's new

[SOLVED] Updating Win 10 14393.1439 fails repeatedly

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Updating Win 10 14393.1439 fails repeatedly.

The last update that worked was in June 2017.

Have tried every solution under the sun, with no luck for almost 18 months.

Update fails on KB4033631 and KB4049411, according to Update History. Yet, Update Status says: "Your device is up to date. Last checked: ‎11/‎10/‎2018, ‏‎7:52 PM."

sfc /scannow does not work and returns: "Windows resource protection cannot start the repair service."

Computer is a Toshiba Kirabook laptop, model PSU8SU

Hardware Abstraction Layer Version = "10.0.14393.206"

The experts on this forum have solved issues with very similar characteristics. I would be grateful for help with mine.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
My error. Sorry. The correct current Windows version is:

Windows 10 Pro Version 1607 14393.1358 (X64) (2016-09-15 22:36:13)
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Updating Win 10 14393.1439 fails repeatedly.

The last update that worked was in June 2017.

Have tried every solution under the sun, with no luck for almost 18 months.

Update fails on KB4033631 and KB4049411, according to Update History. Yet, Update Status says: "Your device is up to date. Last checked: ‎11/‎10/‎2018, ‏‎7:52 PM."

sfc /scannow does not work and returns: "Windows resource protection cannot start the repair service."

Computer is a Toshiba Kirabook laptop, model PSU8SU

Hardware Abstraction Layer Version = "10.0.14393.206"

The experts on this forum have solved issues with very similar characteristics. I would be grateful for help with mine.
My error. Sorry. The correct current Windows version is:

Windows 10 Pro Version 1607 14393.1358 (X64) (2016-09-15 22:36:13)


REPLY: I have uploaded the cbs folder and the sfcfix.txt file.

sfc /scannow returns: "Windows resource protection cannot start the repair service."

Please let me know if I have not complied with all of your requests. Your willingness to help is greatly appreciated.
 

Attachments

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
SFC Scan



  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, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
As requested, ran sfc /scannow and it still returns "Windows Resource Protection could not start the repair service".

Then copied cbs.txt to desktop. Attempted to attach file for uploading, but received message that file is too big to upload (about 11mb). Please advise.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Zip it up and try again. If still too big, please use a file sharing service of your choice.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
As requested, ran sfc /scannow and it still returns "Windows Resource Protection could not start the repair service".

Then copied cbs.txt to desktop. Attempted to attach file for uploading, but received message that file is too big to upload (about 11mb). Please advise.
OK. Zip file attached.
 

Attachments

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing 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
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Please accept my apology for taking so long to get back to you. It is not for lack of appreciation for your help. You are my last hope.

The reason for the delay was severe technical problems in executing your instructions. Procmon.exe consumed enormous amounts of memory. Installed hardware memory is 8GB. With procmon.exe and the update exe processing, "out of memory" crashes occurred before reaching the installation failure, thereby rendering the capture of the procmon logfile impossible.

I had to increase virtual memory several times. "Success" (win update failure before running out of memory, thereby allowing for capture of the procmon logfile) achieved with virtual memory set to minimum and maximum (fixed size) of 32,768.

procmon logfile Dropbox - WIN10UPDATE - Simplify your life

cbs log (zipped) attached.

Thanks for your patience and willingness to help. You provide a great service for very tough problems.




Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing 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
 

Attachments

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Also, winupdate attempted with latest media creation tool: MediaCreationTool1809.exe
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Re: Updating Win 10 14393.1358 fails repeatedly (title corrected)

During which process did you run ProcMon?
I followed your instructions:

1. I booted the laptop.
2. I started procmon.exe
3. procmon log began running
4. I executed MediaCreationTool1809.exe and followed the prompts.
5. update downloaded
6. update verified
7. update installation began
8. update installation failed
9. I stopped procmon, saved the procmon log, and sent it to you, along with the cbs log.

I hope that answers your question. If not, please clarify.

Thanks.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
I wanted you to do it during an update, not an upgrade. You said that some updates were failing. Try installing some of them. Do not attempt the upgrade for now.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
I wanted you to do it during an update, not an upgrade. You said that some updates were failing. Try installing some of them. Do not attempt the upgrade for now.
Now I understand. Two automatic updates continually fail, as documented in my first post. I'll get back to you.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
I wanted you to do it during an update, not an upgrade. You said that some updates were failing. Try installing some of them. Do not attempt the upgrade for now.
OK. activated "normal" update process, allowing Windows to search for updates and select the next ones in line to be updated. The two updates that have failed repeatedly began to be downloaded. I executed procmon.exe as soon as the download process started and stopped it when the update error was returned and the update process terminated.

CBS log attached and procmon log dropboxed.

Dropbox - Logfile (1).zip

Thanks.
 

Attachments

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,413
Location
Croatia
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.
 

seeotter

Contributor
Joined
Nov 14, 2018
Messages
31
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.

Thanks. Could not zip components file, but dropbox successfully uploaded the original file. Here is the link:

Dropbox - components

Thanks again for helping.
 
Top