Win10 no longer updates

I have one (spare) machine that no longer can update...it will sit there
at 80% "feature update to version 1709"

If I let it sit overnight the update never completes.


I ran the update troubleshooter and it found one error which it said it
corrected....registry server not found or corrupt.


Problem is not corrected and if I run the troubleshooter again, same
problem is found and corrected but update still not working.


Have not found any help on Google but wonder if the H/W of the machine
may not be up to spec?

philo wrote:
I have one (spare) machine that no longer can update...it will sit there
at 80% "feature update to version 1709"

If I let it sit overnight the update never completes.


I ran the update troubleshooter and it found one error which it said it
corrected....registry server not found or corrupt.


Problem is not corrected and if I run the troubleshooter again, same
problem is found and corrected but update still not working.


Have not found any help on Google but wonder if the H/W of the machine
may not be up to spec?

Is there enough storage space for an Upgrade ?

You could try downloading a 1709 DVD and executing "Setup.exe"
on the DVD, and it will do the Upgrade from there. This beats
sitting in an Upgrade Loop with good ole Windows Update.

I generally "blast" in my upgrades, and don't wait around.
I make a backup first though, just in case (for situations
where I want to keep the integrity of the install).

People with say, a tablet, with 32GB eMMC storage, they
will find the Upgrade "binds a little", as there will be
barely enough space to finish it. Sometimes the upgrade
asks for a scratch device it can use, to complete the
operation.

If you think there is actual damage to C: , you have the
option of running DISM restorehealth and sfc /scannow, but
I really doubt that's going to achieve a positive result.
And even if the temp folder under C: has gigabytes of
stuff and SoftwareDistribution has gigabytes of stuff,
"sweeping out the storage" doesn't guarantee it'll work
either.

These are some examples of commands you can look up.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

sfc /verifyonly
sfc /offbootdir=c:\ /offwindir=c:\windows /scannow

As for "making a DVD", you don't even have to do that :-)
Windows 10 has a virtual DVD drive, and you can "mount"
the ISO9660 file, and execute "setup.exe" off the virtual
DVD drive. (This recommendation only applies to Repair/Upgrade
installs, as a "blank hardware" install requires a real DVD
or a USB key.) Which is fast, compared to physical hardware.
Since the WIM is compressed, it takes a mighty processor
to plow through that and complete the file copy step in
only a few minutes. That takes some of the fun out of the
speedup a virtual DVD gives you.

Win10_1709_English_x64.iso 4,697,362,432 bytes
Win10_1709_English_x32.iso 3,473,729,536 bytes

The x64 one is a bit big, and you'll want to download
that onto NTFS storage rather than FAT32.

The first version of Win10 was about 600MB smaller.

Paul

On 04/25/2018 08:42 AM, Paul wrote:
philo wrote:
I have one (spare) machine that no longer can update...it will sit
there at 80% "feature update to version 1709"

If I let it sit overnight the update never completes.


I ran the update troubleshooter and it found one error which it said
it corrected....registry server not found or corrupt.


Problem is not corrected and if I run the troubleshooter again, same
problem is found and corrected but update still not working.


Have not found any help on Google but wonder if the H/W of the machine
may not be up to spec?

Is there enough storage space for an Upgrade ?

You could try downloading a 1709 DVD and executing "Setup.exe"
on the DVD, and it will do the Upgrade from there. This beats
sitting in an Upgrade Loop with good ole Windows Update.

I generally "blast" in my upgrades, and don't wait around.
I make a backup first though, just in case (for situations
where I want to keep the integrity of the install).

People with say, a tablet, with 32GB eMMC storage, they
will find the Upgrade "binds a little", as there will be
barely enough space to finish it. Sometimes the upgrade
asks for a scratch device it can use, to complete the
operation.

If you think there is actual damage to C: , you have the
option of running DISM restorehealth and sfc /scannow, but
I really doubt that's going to achieve a positive result.
And even if the temp folder under C: has gigabytes of
stuff and SoftwareDistribution has gigabytes of stuff,
"sweeping out the storage" doesn't guarantee it'll work
either.

These are some examples of commands you can look up.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

sfc /verifyonly
sfc /offbootdir=c:\ /offwindir=c:\windows /scannow

As for "making a DVD", you don't even have to do that :-)
Windows 10 has a virtual DVD drive, and you can "mount"
the ISO9660 file, and execute "setup.exe" off the virtual
DVD drive. (This recommendation only applies to Repair/Upgrade
installs, as a "blank hardware" install requires a real DVD
or a USB key.) Which is fast, compared to physical hardware.
Since the WIM is compressed, it takes a mighty processor
to plow through that and complete the file copy step in
only a few minutes. That takes some of the fun out of the
speedup a virtual DVD gives you.

Win10_1709_English_x64.iso** 4,697,362,432 bytes
Win10_1709_English_x32.iso** 3,473,729,536 bytes

The x64 one is a bit big, and you'll want to download
that onto NTFS storage rather than FAT32.

The first version of Win10 was about 600MB smaller.

** Paul



Plenty of room on the 320 gig drive...I think I'll just put the machine
aside and try again in a few months...it's just a spare machine and I
have many spares


thanks

Am Wed, 25 Apr 2018 12:29:54 -0500, schrieb philo:

Plenty of room on the 320 gig drive...I think I'll just put the machine
aside and try again in a few months...it's just a spare machine and I
have many spares

Be careful.
I had a machine that wouldn't update, for two years.
Then, one day, back in January, it updated to the 1709 release.
And then rebooted.

That was the last I ever saw of it alive.
True story.