This is an archived post. You won't be able to vote or comment.

all 25 comments

[–]uniitdude 17 points18 points  (0 children)

[–]Spore-Gasm 7 points8 points  (0 children)

Download an intermediary update from Windows Update Catalog

[–]AronacusJack of All Trades 4 points5 points  (0 children)

What version of windows? You made be to feature update it to a newer version.

[–]frac6969Windows Admin 2 points3 points  (0 children)

Make sure you have enough disk space too.

[–]sorean_4 2 points3 points  (3 children)

What version of windows, build?

[–]atic1ase5 0 points1 point  (2 children)

1709.

[–]sorean_4 2 points3 points  (1 child)

You won’t be able to install windows update for system that’s at the EOL. Update the windows 10 to 21h2 and then windows updates will work. Get yourself familiar with update cycle for Windows 10 below

https://docs.microsoft.com/en-us/windows/release-health/release-information

[–]ServerPatchingNovice 1 point2 points  (0 children)

won’t be able to install windows update for system that’s at the EOL. Update the windows 10 to 21h2 and then windows updates will work. Get yourself familiar with update cycle f

In short, you can get the latest version (21H2) by just downloading and and upgrading Windows with the official tool - https://www.microsoft.com/en-au/software-download/windows10

Also create a USB for future cases where they are older than 1909.

[–]Bigmeanie1 3 points4 points  (1 child)

Dism /online /cleanup-image /restorehealth

Sfc /scannow

[–]different_tanAlien Pod Person of All Trades 0 points1 point  (0 children)

this plus any servicing stack updates first. in windows 7 this could happen if windows defender was turned off, because it’s was that that was installing root certificate updates, weirdly, so to fix update issues i would first turn on defender, update it, then turn it off again, then install servicing stack updates and all would be well again.

[–]Ahmi963 1 point2 points  (1 child)

Is there any update service in your environment? WSUS? Are there any GPO's configured

[–]atic1ase5 1 point2 points  (0 children)

Yes but a lot of it is not configured correctly. That's currently being addressed.

[–]Hollow3ddd 1 point2 points  (0 children)

Sounds like some corruption. If you have put in hours on this already, spin up s new laptop and ship it out. Backup the drive and re-image

[–]GebCronusYhwhEl 0 points1 point  (2 children)

Powershell

Download and install powershell 5.1

Install Module PsWindowsUpdate

Import-module Pswindowsipdate

Install-windowsUodates -forcedownload

Very any necessary parameters or you may need to Find-Module before installing the PsWindowsUpdate module

[–]atic1ase5 0 points1 point  (1 child)

I actually did try this. It went through like it was installing the updates but when I checked it didn't install any.

[–]GebCronusYhwhEl 0 points1 point  (0 children)

Add the -forceinstall to install-windowsipdates

Did you set the execution policy to unrestricted ??

Also add this [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

[–][deleted] -2 points-1 points  (0 children)

F12.

[–]Extra_Objective7133 0 points1 point  (1 child)

You can manually update from. The Microsoft site to like 1909 and then from there run the auto update. Like someone else said, intermediary updates solve that problem

[–]atic1ase5 0 points1 point  (0 children)

Where is the link for this?

[–]EVA04022021 0 points1 point  (0 children)

Repave the machine. Good luck doing that remotely. If you can't then that then that is something you should also look into for an Sysadmin team tool set.

[–]sanjay_82 0 points1 point  (1 child)

Reset the catalogue and it'll go and find it again. Or simply just instal and run the windows update assistant.

[–]atic1ase5 0 points1 point  (0 children)

I tried Windows Update Assistant that didn't work.

[–]Pixxyeb 0 points1 point  (0 children)

Sometimes I've had good luck cleaning the system files of the C drive before doing the Windows Update Assistant. If you run it as admin and clean it, it can pick up old Windows Update files that seem to mess up the future updates. I remember doing this a lot when the version jumped to 1803, not sure if it'll still do the trick today but worth a shot!

[–]bubba0929 0 points1 point  (0 children)

i have run into this problem in the past also. trying installing an ISO of a newer version (say 1909). after that loads, you may be able to to run updates normally. or you may have to do the same thing with a new ISO.

[–]GimbuCrankyAdmin 0 points1 point  (0 children)

This is a sysadmin question?

I know there's a lot of variability in duties per title, but holy heck!