Creators Update: 0 for 2 :(

Am I the only one having endless trouble with this update?
It has failed on my laptop and deskside. MS "support" has
been trying for 3 weeks to fix the desktop problem, error 0x80070003.
Today MS offered the update for the laptop and failed twice with
0x80070002.

I've tried the various repair actions for both with no luck. MS
"support" has escalated the deskside problem to Level 1 - lots of
tries and many logs since haven't identified the problem.

A third machine here, my wife's, got the update without a hitch.
The difference: her machine is a month old and came with Win 10.
The other two are older and both were upgraded from Win 7.

Jason wrote:

Am I the only one having endless trouble with this update?
It has failed on my laptop and deskside. MS "support" has
been trying for 3 weeks to fix the desktop problem, error 0x80070003.
Today MS offered the update for the laptop and failed twice with
0x80070002.

I've tried the various repair actions for both with no luck. MS
"support" has escalated the deskside problem to Level 1 - lots of
tries and many logs since haven't identified the problem.

A third machine here, my wife's, got the update without a hitch.
The difference: her machine is a month old and came with Win 10.
The other two are older and both were upgraded from Win 7.

Tried a fresh install of Windows 10 (install again but choose to wipe
for a new/fresh install of Windows 10)? Backup your data, make sure you
have the installers for the apps, backup an image of the current Windows
10 installation, and fresh install Windows 10 (it will get your product
key from your Microsoft account). Could be you're lugging pollution
from Windows 7 or apps that is not compatible under Windows 10.

In article , says...
Could be you're lugging pollution
from Windows 7 or apps that is not compatible under Windows 10.

That's likely I guess. The question is, why is this just showing up now?
The upgrade from 7 to 10 worked and so did subsequent updates until this
one. My question then is -what- is causing the problem? If it's a
particular app I'll happily reinstall it or just get rid of it, but
starting from scratch is too daunting to consider until I have exhausted
every possibility. There is a point at which the update procedure threw
in the towel, so why can't there be more specific information as to the
cause. There are tons of logs produced during the update. MS support
gathered them all up and the reason should be in there somewhere...

On 26/10/2017 21:35, Jason wrote:
Am I the only one having endless trouble with this update?
It has failed on my laptop and deskside. MS "support" has
been trying for 3 weeks to fix the desktop problem, error 0x80070003.
Today MS offered the update for the laptop and failed twice with
0x80070002.

I've tried the various repair actions for both with no luck. MS
"support" has escalated the deskside problem to Level 1 - lots of
tries and many logs since haven't identified the problem.

A third machine here, my wife's, got the update without a hitch.
The difference: her machine is a month old and came with Win 10.
The other two are older and both were upgraded from Win 7.


Have you tried running the setup.exe directly by mounting the iso on
your machine? In fact, have you downloaded the full iso for future
reference? If not then why not?

If you have the iso then running the setup file directly will solve most
problems. Just make sure you are offline and choose "ignore updates"
when running it. This is for downloading further updates and may
complicate things even more. Best thing is to ignore the updates now
until your setup has finished upgrading your system. Then you can get
one more update after you have rebooted the system at least two times.



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

"Jason" wrote in message
...

Am I the only one having endless trouble with this update?
It has failed on my laptop and deskside. MS "support" has
been trying for 3 weeks to fix the desktop problem, error 0x80070003.
Today MS offered the update for the laptop and failed twice with
0x80070002.

I've tried the various repair actions for both with no luck. MS
"support" has escalated the deskside problem to Level 1 - lots of
tries and many logs since haven't identified the problem.

A third machine here, my wife's, got the update without a hitch.
The difference: her machine is a month old and came with Win 10.
The other two are older and both were upgraded from Win 7.

Jason,

You have probably already tried this but just in case - turn off any 3rd
party antivirus/malware/ransomware software.

I have over 30 systems to update and have found (so far) that MalwareBytes
(free or paid version) was a major cause of the failed upgrades on the few
I've done so far. After I disabled it, the upgrade worked.

Bob S.

On Sat, 28 Oct 2017 21:30:11 -0400, "Bob_S" wrote:



"Jason" wrote in message
al-september.org...

Am I the only one having endless trouble with this update?

Yes..

On Sat, 28 Oct 2017 21:30:11 -0400 "Bob_S" wrote in
article
You have probably already tried this but just in case - turn off any 3rd
party antivirus/malware/ransomware software.

I have over 30 systems to update and have found (so far) that MalwareBytes
(free or paid version) was a major cause of the failed upgrades on the few
I've done so far. After I disabled it, the upgrade worked.

Bob S.

I don't have MalwareBytes - I did at one time and it was very difficult to
completely get rid of it! And yes, I turned off A-V software to no avail.
Per recommendation of the MS support folks, I also use msconfig to disable
all but the Microsoft services during the update. Didn't seem to help. I
also spent a couple hours the other day going through -all- of the
installed programs and drivers and tossed quite a few old ones that I no
longer need. MS Support said that drivers can prevent an update from
succeeding.

What I don't get is this: at some point, Setup logic determines that the
update cannot proceed. Why doesn't it tell me/anybody why? I'd think that
would be easier than poring over all the logs (most of which don't mean
much to me anyway). MS support has collected them all and handed them off
to "Tier 3" for analysis. Hope springs eternal....

Thanks

"Jason" wrote in message
...

On Sat, 28 Oct 2017 21:30:11 -0400 "Bob_S" wrote in
article
You have probably already tried this but just in case - turn off any 3rd
party antivirus/malware/ransomware software.

I have over 30 systems to update and have found (so far) that MalwareBytes
(free or paid version) was a major cause of the failed upgrades on the few
I've done so far. After I disabled it, the upgrade worked.

Bob S.

I don't have MalwareBytes - I did at one time and it was very difficult to
completely get rid of it! And yes, I turned off A-V software to no avail.
Per recommendation of the MS support folks, I also use msconfig to disable
all but the Microsoft services during the update. Didn't seem to help. I
also spent a couple hours the other day going through -all- of the
installed programs and drivers and tossed quite a few old ones that I no
longer need. MS Support said that drivers can prevent an update from
succeeding.

What I don't get is this: at some point, Setup logic determines that the
update cannot proceed. Why doesn't it tell me/anybody why? I'd think that
would be easier than poring over all the logs (most of which don't mean
much to me anyway). MS support has collected them all and handed them off
to "Tier 3" for analysis. Hope springs eternal....

Thanks

Jason,

Past experience with windows upgrades has shown that video drivers are
notorious for creating problems. I've had one Dell Win10 system at a
clients location with a PCI video card installed where the video driver was
the problem.

Two methods that have worked for me:

1. Go to *manufactures* site and download and install the latest video
driver. If it's an onboard video setup, then still do the same thing -
download the latest driver(s) from the manufacturers site.

2. Uninstall the video driver / software package (AMD, NVidia) and then do
the upgrade using the windows generic driver. Then reinstall video
drivers/software.

Now I have found that when I was upgrading systems from 1607 to 1703 the
Intel drivers were problematic - specifically the video drivers.

When you uninstall the video drivers (software) make sure you reboot and
insure that the system is using the generic drivers. If it's reloaded the
same drivers, you didn't uninstall them. If it's a system that is using an
onboard Intel video chip you may not be able to uninstall it and even if you
disable it in Device Manager, it comes back. In the device Manager, find
the manufacturers drivers under "System" and right click on each one and
select "Update Driver Software". You may find that some of them will
update.

After all are updated, try the upgrade again after rebooting the system.

If it still fails, go back to the Device Manager System menu and look for
th4e video/graphics chip drivers and right-click to bring up the Properties
window. Then select the Drivers tab - you may see a selection to "Roll Back
Driver". If it's not grayed out, try rolling back the driver.

The past few months there have been a mall number of updates available from
the Intel site that indicate to me that the driver downloads from MS may
have been a bit buggy. I have not taken the time to ferret out all the
details. I just do the above and try to update any drivers individually
under the System devices in Device Manager and the reboot and try the
upgrade.

With over 30 systems of varying vintage and manufactures I can't remember
all the details but I have troubleshot a lot of previous upgrade problems
with versions 1607 and 1703. The latest version 1709 has been upgrading
fine - save one system and that was a MS Surface Pro 4 tablet. Go
figure.... But it upgraded on the second attempt.

I'm assuming that MS had you run the Troubleshooter (windows update) and
that it cleaned everything out and said it found and fixed a corrupted
database. If not - do that first.

Bob S.

On Tue, 31 Oct 2017 19:59:40 -0400 "Bob_S" wrote in
article

"Jason" wrote in message
...

On Sat, 28 Oct 2017 21:30:11 -0400 "Bob_S" wrote in
article
You have probably already tried this but just in case - turn off any 3rd
party antivirus/malware/ransomware software.

I have over 30 systems to update and have found (so far) that MalwareBytes
(free or paid version) was a major cause of the failed upgrades on the few
I've done so far. After I disabled it, the upgrade worked.

Bob S.

I don't have MalwareBytes - I did at one time and it was very difficult to
completely get rid of it! And yes, I turned off A-V software to no avail.
Per recommendation of the MS support folks, I also use msconfig to disable
all but the Microsoft services during the update. Didn't seem to help. I
also spent a couple hours the other day going through -all- of the
installed programs and drivers and tossed quite a few old ones that I no
longer need. MS Support said that drivers can prevent an update from
succeeding.

What I don't get is this: at some point, Setup logic determines that the
update cannot proceed. Why doesn't it tell me/anybody why? I'd think that
would be easier than poring over all the logs (most of which don't mean
much to me anyway). MS support has collected them all and handed them off
to "Tier 3" for analysis. Hope springs eternal....

Thanks

Jason,

Past experience with windows upgrades has shown that video drivers are
notorious for creating problems. I've had one Dell Win10 system at a
clients location with a PCI video card installed where the video driver was
the problem.

Two methods that have worked for me:

1. Go to *manufactures* site and download and install the latest video
driver. If it's an onboard video setup, then still do the same thing -
download the latest driver(s) from the manufacturers site.
No onboard video and the Nvidia driver is current.

2. Uninstall the video driver / software package (AMD, NVidia) and then do
the upgrade using the windows generic driver. Then reinstall video
drivers/software.

Now I have found that when I was upgrading systems from 1607 to 1703 the
Intel drivers were problematic - specifically the video drivers.

When you uninstall the video drivers (software) make sure you reboot and
insure that the system is using the generic drivers. If it's reloaded the
same drivers, you didn't uninstall them. If it's a system that is using an
onboard Intel video chip you may not be able to uninstall it and even if you
disable it in Device Manager, it comes back. In the device Manager, find
the manufacturers drivers under "System" and right click on each one and
select "Update Driver Software". You may find that some of them will
update.

After all are updated, try the upgrade again after rebooting the system.
MS Support seems to be suspicious of drivers in general being the possible
cause of my troubles. I've been weeding out old ones that I don't need any
more and will continue hunting.

If it still fails, go back to the Device Manager System menu and look for
th4e video/graphics chip drivers and right-click to bring up the Properties
window. Then select the Drivers tab - you may see a selection to "Roll Back
Driver". If it's not grayed out, try rolling back the driver.

The past few months there have been a mall number of updates available from
the Intel site ...

There's no integrated video in this machine, just the Nvidia PCI card.

I'm assuming that MS had you run the Troubleshooter (windows update) and
that it cleaned everything out and said it found and fixed a corrupted
database. If not - do that first.
I've done that 'til I'm blue in the face. It always claims to have fixed
everything. Then I run the install, it fails, and the troubleshooter once
again claims it found problems and fixed 'em all...


Bob S.

"Jason" wrote in message
...

On Tue, 31 Oct 2017 19:59:40 -0400 "Bob_S" wrote in
article

"Jason" wrote in message
...

On Sat, 28 Oct 2017 21:30:11 -0400 "Bob_S" wrote in
article
You have probably already tried this but just in case - turn off any 3rd
party antivirus/malware/ransomware software.

I have over 30 systems to update and have found (so far) that
MalwareBytes
(free or paid version) was a major cause of the failed upgrades on the
few
I've done so far. After I disabled it, the upgrade worked.

Bob S.

I don't have MalwareBytes - I did at one time and it was very difficult to
completely get rid of it! And yes, I turned off A-V software to no avail.
Per recommendation of the MS support folks, I also use msconfig to disable
all but the Microsoft services during the update. Didn't seem to help. I
also spent a couple hours the other day going through -all- of the
installed programs and drivers and tossed quite a few old ones that I no
longer need. MS Support said that drivers can prevent an update from
succeeding.

What I don't get is this: at some point, Setup logic determines that the
update cannot proceed. Why doesn't it tell me/anybody why? I'd think that
would be easier than poring over all the logs (most of which don't mean
much to me anyway). MS support has collected them all and handed them off
to "Tier 3" for analysis. Hope springs eternal....

Thanks

Jason,

Past experience with windows upgrades has shown that video drivers are
notorious for creating problems. I've had one Dell Win10 system at a
clients location with a PCI video card installed where the video driver
was
the problem.

Two methods that have worked for me:

1. Go to *manufactures* site and download and install the latest video
driver. If it's an onboard video setup, then still do the same thing -
download the latest driver(s) from the manufacturers site.
No onboard video and the Nvidia driver is current.

2. Uninstall the video driver / software package (AMD, NVidia) and then do
the upgrade using the windows generic driver. Then reinstall video
drivers/software.

Now I have found that when I was upgrading systems from 1607 to 1703 the
Intel drivers were problematic - specifically the video drivers.

When you uninstall the video drivers (software) make sure you reboot and
insure that the system is using the generic drivers. If it's reloaded the
same drivers, you didn't uninstall them. If it's a system that is using
an
onboard Intel video chip you may not be able to uninstall it and even if
you
disable it in Device Manager, it comes back. In the device Manager, find
the manufacturers drivers under "System" and right click on each one and
select "Update Driver Software". You may find that some of them will
update.

After all are updated, try the upgrade again after rebooting the system.
MS Support seems to be suspicious of drivers in general being the possible
cause of my troubles. I've been weeding out old ones that I don't need any
more and will continue hunting.

If it still fails, go back to the Device Manager System menu and look
for
th4e video/graphics chip drivers and right-click to bring up the
Properties
window. Then select the Drivers tab - you may see a selection to "Roll
Back
Driver". If it's not grayed out, try rolling back the driver.

The past few months there have been a mall number of updates available
from
the Intel site ...

There's no integrated video in this machine, just the Nvidia PCI card.

I'm assuming that MS had you run the Troubleshooter (windows update) and
that it cleaned everything out and said it found and fixed a corrupted
database. If not - do that first.
I've done that 'til I'm blue in the face. It always claims to have fixed
everything. Then I run the install, it fails, and the troubleshooter once
again claims it found problems and fixed 'em all...


Bob S.

Jason,

If you updated all the drivers in the Device Manager System devices as I
said then:

Uninstall that NVidia driver and software and use the generic windows
drivers for the upgrade.

Also make sure nothing else is connected to the system such as USB devices
(other than keyboard and mouse), no printers. Make it as bare bone as
possible. If you have an extra USB card or other PCI card installed for
eSATA or something else - remove them.

I assume that MS verified that you have enough hdd space (min 8.5GB to 20GB)
to perform the upgrade and they had you run a memory check and CHKDSK on the
drives - right?

Bob S.

On Tue, 31 Oct 2017 22:32:41 -0400 "Bob_S" wrote in
article
Jason,

If you updated all the drivers in the Device Manager System devices as I
said then:

Uninstall that NVidia driver and software and use the generic windows
drivers for the upgrade.

Also make sure nothing else is connected to the system such as USB devices
(other than keyboard and mouse), no printers. Make it as bare bone as
possible. If you have an extra USB card or other PCI card installed for
eSATA or something else - remove them.

I assume that MS verified that you have enough hdd space (min 8.5GB to 20GB)
to perform the upgrade and they had you run a memory check and CHKDSK on the
drives - right?

Bob S.



There's plenty of space. I've run CHKDSK and no problems were reported.
I've removed printer drivers per your and MS' suggestion. There are no
other PCI cards installed besides the Nvidia adapter. I also took a long
walk through installed software and tossed some old applications that I no
longer need. MS has disabled all but MS services via MSCONFIG during the
update. I also disconnected a USB3 hub; there's only one more attached USB
device beside kbd/mouse - the APC UPS. I'll unhook that one and try again.

Thanks.

Jason wrote:
On Tue, 31 Oct 2017 22:32:41 -0400 "Bob_S" wrote in
article
Jason,

If you updated all the drivers in the Device Manager System devices as I
said then:

Uninstall that NVidia driver and software and use the generic windows
drivers for the upgrade.

Also make sure nothing else is connected to the system such as USB devices
(other than keyboard and mouse), no printers. Make it as bare bone as
possible. If you have an extra USB card or other PCI card installed for
eSATA or something else - remove them.

I assume that MS verified that you have enough hdd space (min 8.5GB to 20GB)
to perform the upgrade and they had you run a memory check and CHKDSK on the
drives - right?

Bob S.



There's plenty of space. I've run CHKDSK and no problems were reported.
I've removed printer drivers per your and MS' suggestion. There are no
other PCI cards installed besides the Nvidia adapter. I also took a long
walk through installed software and tossed some old applications that I no
longer need. MS has disabled all but MS services via MSCONFIG during the
update. I also disconnected a USB3 hub; there's only one more attached USB
device beside kbd/mouse - the APC UPS. I'll unhook that one and try again.

Thanks.

The first one, should be the copy-file stage.

C:\$WINDOWS.~BT\Sources\Panther\setupact.log 19,068,030 bytes --- "correct" timestamp

Subsequent stages dump here.

C:\Windows\Panther\setupact.log 75,017,518 bytes --- Redmond time

The "error" is not right at the end of that file,
because the "unroll" of the install also gets logged.

There is also potentially a setuperr.log.

How to interpret, is documented here.

https://technet.microsoft.com/en-us/...(v=ws.10).aspx

"When a failure occurs in Windows Setup, review the entries
in the Setuperr.log file, then the Setupact.log file, and
then other log files as appropriate."

Paul

Il 26/10/2017 22.35, Jason ha scritto:
Am I the only one having endless trouble with this update?

No. Only 1 of 3.
The other 2 will wait ...

On 26/10/2017 21:35, Jason wrote:

Am I the only one having endless trouble with this update?
It has failed on my laptop and deskside. MS "support" has
been trying for 3 weeks to fix the desktop problem, error 0x80070003.
Today MS offered the update for the laptop and failed twice with
0x80070002.

I've tried the various repair actions for both with no luck. MS
"support" has escalated the deskside problem to Level 1 - lots of
tries and many logs since haven't identified the problem.

A third machine here, my wife's, got the update without a hitch.
The difference: her machine is a month old and came with Win 10.
The other two are older and both were upgraded from Win 7.



Have you tried running the setup.exe directly by mounting the iso on your machine? In fact, have you downloaded the full iso for future reference? If not then why not?

If you have the iso then running the setup file directly will solve most problems. Just make sure you are offline and choose "ignore updates" when running it. This is for downloading further updates and may complicate things even more. Best thing is to ignore the updates now until your setup has finished upgrading your system. Then you can get one more update after you have rebooted the system at least two times.




Wow, actual good advice from Good Guy. Miracles do happen.
--
Buffalo

On Wed, 1 Nov 2017 13:19:32 -0600 "Buffalo"
wrote in article
Have you tried running the setup.exe directly by mounting the iso on
your machine? In fact, have you downloaded the full iso for future
reference? If not then why not?

I have tried this. No luck. So have the MS support people - they gathered
a ton of log files and will let me know what they find.