How do I manually install Windows 10 updates?

[Ropuchy]

Hello.
I attempted updating my graphics drivers but they failed due to the OS not being up to date.

The automatic Windows updater keeps running into issues, and is unable to update.

I am currently running the 15063.413 build of Windows 10 1703.
I've found that the most recent build of Windows is 15063.540.

How should I download and install this update?

I've found 4 files on the Windows Update Catalog by searching "KB4034674"
Should I download all 4?

 

[Ropuchy]

See if this helps

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, DISM cleans image files, re run SFC if it failed to fix all files and restart PC

what type of file did it give you from windows catalog? If its a cab file you can use a command line to install it: https://www.tenforums.com/tutorials/66346-install-cab-file-windows-10-a.html

DISM reports no issues, while SFC says there's something funky. I'll have to run it again to see the error message, but I remember it was just redirecting me to a file location for an error report.

Nah, the file from the catalog ran fine. Windows accepted it as an update and had me verify that I wanted to run it and whatnot. It's just that once it completed, I get a message saying that it did not install... No error or anything, it just says that it didn't install.

 

[Colif]

probably cbs log. if you do the dism command after SFC, it should fix the things it couldn't before.

I was just setting up a new dell and got an error updating same cumulative patch, but restarting update fixed it.

 

[Ropuchy]

probably cbs log. if you do the dism command after SFC, it should fix the things it couldn't before.

I was just setting up a new dell and got an error updating same cumulative patch, but restarting update fixed it.

Alright, I'll try that.
I currently have a CMD prompt window open that's in the middle of processing.
Would it be ok for me to open up a new window to do the SFC and DISM stuff?

 

[androbourne]

Wait for the first process to finish. SCP scans everything for issues if it attempts to fix what you are doing it could make it worse.

 

[Ropuchy]

Wait for the first process to finish. SCP scans everything for issues if it attempts to fix what you are doing it could make it worse.

Ok. It may take all night to hear back from me, then.
It looks like it'll take a bit for what it's doing at the moment.

 

[androbourne]

Ok no worries. Just let us know how to goes.

 

[Ropuchy]

probably cbs log. if you do the dism command after SFC, it should fix the things it couldn't before.

I was just setting up a new dell and got an error updating same cumulative patch, but restarting update fixed it.

Yeah, it's the CBS log.
The sfc, DISM, then restart and sfc didn't work.
It says that WIndows Resource Protection found corrupt files but was unable to fix some of them.

Should I go find the CBS log?

 

[Ropuchy]

Ok no worries. Just let us know how to goes.

The offline updater didn't work. I got the errors: 1726 and 1722, if that helps at all.

 

[androbourne]

It for sure sounds more like a OS corruption or a Windows Updater corruption. Not simply one update that failed.

Try this for the error 1726

Press Windows key + X or put the mouse in the lower left corner.
Open the Command Prompt (Run as Administrator)
Type in WSReset.exe and hit enter.
Type the following in a Command Window (CMD) to re-register the Store App:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.XML

And this for 1722

Method 1: Check if the Installer Service is running. To do so, follow these steps.

a. Click Start, Click Run and type “Services.msc” (without quotes) and press Enter.
b. Double-click Windows Installer.
c. Set the Startup type of Windows Installer to Manual.
d. Click Start to start the service. Note down the error message if any. Click OK.

Method 2: Reregister the Windows Installer. Follow these steps for the same.

a. Quit all Windows programs.
b. Click Start, All Programs, Accessories and click Run. Type “msiexec /unregister” (without quotes) in the Open box, and then click OK.
c. Click Start, All Programs, Accessories and click Run. Type “msiexec /regserver” (without quotes) in the Open box, and then click OK. Restart your computer.

Check to see if the problem persists.

Original sources.
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_repair/dism-failing-with-error-1726/a96a1f49-c841-4253-a5a8-b9d0d3122b56

https://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_programs/im-getting-an-error-1722-windows-installer-package/ec60ba09-fc3c-49b4-b3bd-c315c2c7d17a

P.S.
Did you ever try to do a system restore to prior when that first update failed to install?

 

[Ropuchy]

It for sure sounds more like a OS corruption or a Windows Updater corruption. Not simply one update that failed.

Try this for the error 1726

Press Windows key + X or put the mouse in the lower left corner.
Open the Command Prompt (Run as Administrator)
Type in WSReset.exe and hit enter.
Type the following in a Command Window (CMD) to re-register the Store App:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.XML

And this for 1722

Method 1: Check if the Installer Service is running. To do so, follow these steps.

a. Click Start, Click Run and type “Services.msc” (without quotes) and press Enter.
b. Double-click Windows Installer.
c. Set the Startup type of Windows Installer to Manual.
d. Click Start to start the service. Note down the error message if any. Click OK.

Method 2: Reregister the Windows Installer. Follow these steps for the same.

a. Quit all Windows programs.
b. Click Start, All Programs, Accessories and click Run. Type “msiexec /unregister” (without quotes) in the Open box, and then click OK.
c. Click Start, All Programs, Accessories and click Run. Type “msiexec /regserver” (without quotes) in the Open box, and then click OK. Restart your computer.

Check to see if the problem persists.

Original sources.
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_repair/dism-failing-with-error-1726/a96a1f49-c841-4253-a5a8-b9d0d3122b56

https://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_programs/im-getting-an-error-1722-windows-installer-package/ec60ba09-fc3c-49b4-b3bd-c315c2c7d17a

P.S.
Did you ever try to do a system restore to prior when that first update failed to install?

Yeah, it's probably a little bit corrupt.

Will any of this delete any of my personal data and whatnot?
I'll try it all out if it doesn't. Thanks!

No, there isn't any restore point prior to the update. I had updated my version of windows from 1603 to 1703, which deleted all restore points. After that, this has been the first update it's tried to do. So I don't have any restore points prior to any of this. I did have some in 1603, but they got deleted.

Sorry for responding a bit late. It decided not to notify me.

 

[androbourne]

It shouldn't delete anything personal. We are working on Windows Updater only. However. It is always a good idea to make a backup incase your system corruption gets worse.

And yeah that makes sense. I believe build updates are automatically removed from restore points after a month.

 

[Ropuchy]

It shouldn't delete anything personal. We are working on Windows Updater only. However. It is always a good idea to make a backup incase your system corruption gets worse.

And yeah that makes sense. I believe build updates are automatically removed from restore points after a month.

Alright.
Yeah, it's pretty frustrating.
I'll try the stuff you suggested and report back once I'm one or encounter any errors.

 

[Ropuchy]

It shouldn't delete anything personal. We are working on Windows Updater only. However. It is always a good idea to make a backup incase your system corruption gets worse.

And yeah that makes sense. I believe build updates are automatically removed from restore points after a month.

Alright.
So I tried the fix for 1726, but I seem to have deleted the Windows Store app at some point, so it doesn't do what it should. How should I go about getting the app back?

For your first suggestion for fixing 1722, I ran into an error saying that I am not able to access the services app, and that an administrator has blocked it... So I logged into the hidden admin account and finished Method 1. Would it still do what it's supposed to?

Should I do method 2, or is that not necessary now?

 

[Ropuchy]

Alright, the Windows updater gave me some error codes now.
It hadn't before for some reason.

They are: 2017-08 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4034674) - Error 0x800706be

2017-08 Security Update for Adobe Flash Player for Windows 10 Version 1703 for x64-based Systems (KB4034662) - Error 0x800706be

And two AMD related ones, which are only an issue because Windows has to fully update for them to update as well.

 

[Ropuchy]

I think I'll try to repair the Windows install by repairing it with the ISO image or whatnot.

Thanks a tonne, androbourne, rgd1101, and Colif! Y'all helped a tonne, even if it didn't necessarily work... I'll select rgd1101's answer that suggested doing the ISO thing-a-ma-bob as the solution.
I'll start a new thread for helping me figure out how to do all of that, so I'll link that here: http://www.tomshardware.com/forum/id-3493097/repair-windows-iso-file.html

 

[androbourne]

Repairing Windows Updates and Updater is a pain. It doesn't always work and a wipe/reload is normally a last resort, but sometimes necessary.

Windows is special like that.

 

[Ropuchy]

Well, doing the ISO thing brought the build number down to 15063.0. (Used to be 15063.413)
So yeah, not sure what happened there.

I also still get all of the same errors when trying to update Windows.

2017-06 Update for Windows 10 Version 1703 for x64-based Systems (KB4022405) - Error 0x800706be

2017-08 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4034674) - Error 0x800706ba

2017-08 Security Update for Adobe Flash Player for Windows 10 Version 1703 for x64-based Systems (KB4034662) - Error 0x800706ba

And Error 0x800706be for two AMD related installs that failed.

 

[Ropuchy]

Alright, I found a bit of info on a potential way to fix the error I'm getting in SFC.

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Down on point 3, I keep getting the fourth message "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log."

It says I can repair it manually. How should I go about doing this? Or will it not work?

 

[androbourne]

You need to read the CBS.log file and see what the error is first.

 

[Ropuchy]

You need to read the CBS.log file and see what the error is first.

Alright.
So what am I looking for in the log?

 

[androbourne]

Anything that indicates what the error is. The log is huge so it can take awhile to read through it.

 

[Ropuchy]

Anything that indicates what the error is. The log is huge so it can take awhile to read through it.

Ok.
Well, "Primitive installers committed for repair" comes up 17,057 times...

Also a few other little things like:

This "DIRSD OWNER WARNING" related stuff comes up about 1000 times.

00004efc [DIRSD OWNER WARNING] Directory [l:52 ml:53]'\??\C:\Program Files (x86)\Common Files\System\en-US' is not owned but specifies SDDL in component Microsoft-Windows-WAB-Core.Resources, arch x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

And this comes up about 1500 times. (They may be duplicates of one another, but it's too long for me to tell.)

00004f4f Error - Overlap: Duplicate ownership for directory \??\C:\WINDOWS\microsoft.net\authman in component Microsoft.Interop.Security.AzRoles, version 10.0.15063.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

So yeah, there's those 3 types of messages in there, and that's about it. There are a lot of them, though.

 

[androbourne]

I don't recall if we tried doing this yet in either of the troubleshoot steps. But try running this command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

Then restart your PC

 

[Ropuchy]

I don't recall if we tried doing this yet in either of the troubleshoot steps. But try running this command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

Then restart your PC

Funnily enough, I'm doing that exact thing right now.
I think I've done it before, but not since the ISO thingy.

 

[Ropuchy]

I don't recall if we tried doing this yet in either of the troubleshoot steps. But try running this command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

Then restart your PC

Looks like it didn't fix the issue.
Though the Windows Updater did act slightly differently.
After the first attempt to install the updates failed, it said that they had to be installed by opening up a separate window (Or something similar to that. It didn't say it for too long, so I didn't get to read exactly what it said.)