update troubleshooter always reports database corruption

I'm still trying to upgrade from 1607 to 1709 without success. When it
fails, if I run the troubleshooter, it -always- reports corruption. The
disk is clean as far as I can tell and sfc and dism do their jobs without
reporting problems. If I run the troubleshooter twice in a row it will not
report corruption a second time and both runs claim all the problems are
fixed. Yet the update fails reliably.

On 25/02/2018 02:14, Jason wrote:
I'm still trying to upgrade from 1607 to 1709 without success. When it
fails, if I run the troubleshooter, it -always- reports corruption. The
disk is clean as far as I can tell and sfc and dism do their jobs without
reporting problems. If I run the troubleshooter twice in a row it will not
report corruption a second time and both runs claim all the problems are
fixed. Yet the update fails reliably.


I have told you, pay somebody to fix it for you. It is nearly 7 months
you have been going on about this and no progress has been made. You
need to pay or keep whatever you have. It can't be any clearer!!!



--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Jason wrote:
I'm still trying to upgrade from 1607 to 1709 without success. When it
fails, if I run the troubleshooter, it -always- reports corruption. The
disk is clean as far as I can tell and sfc and dism do their jobs without
reporting problems. If I run the troubleshooter twice in a row it will not
report corruption a second time and both runs claim all the problems are
fixed. Yet the update fails reliably.


Is your AV disabled during the upgrade ?

*******

Purely as a lark...

1) Back up C: with Reflect or BackUpper.

2) Enter Control Panels : Programs and Features and delete *everything*.

If you delete the AV, don't forget to download the cleaner tool
from the AV maker and run that too.

3) Reboot.

4) Insert 1709 DVD. Runs Setup.exe off the DVD.

If it installs, then you know one of your programs is implicated.

A second area to check is, "do you use custom Junction Points?".

For example, without too much trouble, I could move my home directory
to D: . But, the installer doesn't like that. Do you have any customization
that moved the Program Files or Home Directory, or added custom libraries ?
Try putting the stuff back to default conditions.

*******

Does the machine have custom hardware ?

Strip the machine of non-essentials. *Only* the disk
needing the install should be present. Just the disk and
your DVD drive, or your disk plus USB key with Win10 on it.

And before you begin the install attempt, you'd of course
reboot and verify that the OS is stable with the new (temporary) config.

*******

After all experiments are finished, put things back, restore from backup
with the OS image that matches the reinstalled hardware.

*******

I had corruption on a couple of C: drives here, but they
were Insider editions and it was something in the last two
upgrades that did it. My volume bitmap was damaged (not a biggy),
plus something called Extended Attributes for a set of files
was damaged too. From another OS, this is what fixed it. The
commands individually (or repeating the second command
twice in a row) didn't work. Only these two in sequence worked.
At the time, the damaged partitions were M: and N: while I
was attempting repair. I thought for sure they were toast.

chkdsk /offlinescanandfix M:
chkdsk /F M:

I think we discussed the location of .log files in
a previous thread.

HTH,
Paul

Jason wrote:

I'm still trying to upgrade from 1607 to 1709 without success. When it
fails, if I run the troubleshooter, it -always- reports corruption.
The disk is clean as far as I can tell and sfc and dism do their jobs
without reporting problems. If I run the troubleshooter twice in a
row it will not report corruption a second time and both runs claim
all the problems are fixed. Yet the update fails reliably.

Did you delete the local catalog database to have WU rebuild it anew?

https://support.microsoft.com/en-us/...ate-components
http://ccm.net/faq/2471-how-to-purge...s-update-cache

In article , lid says...
4) Insert 1709 DVD. Runs Setup.exe off the DVD.

If it installs, then you know one of your programs is implicated.

I tried just that a week ago and the installation succeeded, so it
apparently is not hardware-related.

A few years ago, I *had* fiddled with Junction Points but that was
before I upgraded from 7 to 10 so there shouldn't be remnants of that
experiment remaining, but I'll make sure.

All of the chkdsk'ing I can think of shows no issues.