Can't update W10

Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as a
home pc or a company pc. I choosed company pc, as it works in our LAN as
a file-, print- and webserver. Sort of NAS. Perhaps some settings now
prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

On Tue, 23 Jan 2018 11:50:26 +0100, Fokke Nauta
wrote:

Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as a
home pc or a company pc. I choosed company pc, as it works in our LAN as
a file-, print- and webserver. Sort of NAS. Perhaps some settings now
prevent a normal update?

Thanks in advance for your help.

You don't want 1709 so count yourself lucky.
However you can use W10 help.



Fokke Nauta

Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as a
home pc or a company pc. I choosed company pc, as it works in our LAN as
a file-, print- and webserver. Sort of NAS. Perhaps some settings now
prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

And that worked ? ("I choosed company pc")

You're not supposed to do that.

The "free" upgrade is for *home* users. Whether installing Home
or Pro, you are a "home user". Pretend to be a humble home user.

That's a trick question to catch Enterprise end-users trying to
thwart their IT department by "pouring crap" over top of carefully
prepared IT OS installations. People were doing that at their
work, blowing away the company OS image, which is why the trick
question is there to stop the installation.

The install should stop if you answer "as a business user".
Or, it'll fail to activate, and go into grace mode. It won't
be activated and after 30 days it'll indicate the end of the
grace period. The grace period exists so IT people can prepare a machine
for deployment, which may take days to do.

The Digital Entitlement, you have until the end of January
to generate one. This is a priority, and is what you need
to achieve now. The current date is Jan23 and not much
time remains for free upgrades. Check to see if it's activated.

slmgr /dlv

Does it say "activated" ?

If you have a big investment (time spent) setting this up, then

1) make a backup of at least C: and System Reserved

2) slui 4

Enter the Win7 key and see if it is accepted.
I don't know if that will override how you answered The Question,
but it might. The idea is to convert the Win7 key
into a digital entitlement.

3) Verify with slmgr /dlv

4) If you screw up, you can restore from (1).

An alternative is:

1) Backup the current fully-fleshed Win10 install
2) Restore the Win7 image you made before this exercise started.
You made a backup, right ? You're not relying on the
"Revert" capability to save you I hope. It works, but it
is slow and less than perfect.

3) Install Win10 over the restored Win7.
4) Answer "Home" user when The Question appears.
5) slmgr /dlv to check for Digital Entitlement and activation.

6) Now, restore the image from (1).
Check activation. Use the command to activate if
it's not activated, as the Digital Entitlement on the
MS server from (5) should be enough to authorize the
current installation.

The key message here is, get your "activation" status worked
out, no matter what, before the end of the month, or it's
going to cost you $150 to fix later. You want proof you
have Digital Entitlement now.

I did this on my current machine, on Dec.31 (when the idea
was, that was the last day). I got my Digital Entitlement
completed, then I removed Windows 10 from the machine (for
now). In future, I may need to restore it again, and
the Digital Entitlement is waiting for me when I need it.
It's like "free money" in a sense. Maybe if I sell my
computer, it'll be the OS of choice to put on it :-)
So I won't be wasting any other OSes.

The Digital Entitlement and free upgrade is available
until Jan.31 or so. Whatever the last day of the
month is.

*******

If you are actually Activated and that part is OK,
then there is less to worry about.

To enter Control Panels, use Start : Run and

control
control.exe

And that will bring up the traditional Control Panel interface.
You can pin this to the Task Bar so you won't have to do it
a second time.

In there, is a Troubleshooter control panel. Select it.

The Troubleshooter should have a box in the upper right
hand corner for "Search". Search for "Update" or
"Windows Update". You get the idea.

The Windows Update troubleshooter should be able to
clean out the gigabytes of files in SoftwareDistribution.
This has been known to help get Windows Update working
again. A script on tenforums.com is available to do this
too, and the TroubleShooter that Microsoft uses, does
all the same steps.

After doing that, and trying Settings gear wheel and
"Updates and Security" from the Settings panel,
report back how many updates aren't installed or
are broken.

You can also download updates from catalog.update.microsoft.com.

Those come in executable .msu format.

To install one in relative peace, you can:

1) Download the KB file matching your OS, from the
selection you made in catalog.update.microsoft.com.
If you have a list of failed updates, you can download
all of those now, and save for the next steps.

2) Disconnect the network cable.
Reboot.
(This step puts wuauserv in a benign state. Since the
network is no longer available to the OS, then wuauserv
has no choice but to listen to the "query" from the
.msu you're about to launch.)

3) Double click the .msu to install.

4) If you have multiple .msu files, *don't* click the
reboot button you see. Only click reboot when the *last*
.msu is installed.

5) Do your reboot. Reconnect the network cable when you
feel like it.

That doesn't "force" an update, but it is an alternate
method to resolve a broken update. I've only had a couple
of occasions where that method didn't get me past a
"fail" one.

HTH,
Paul

On 23-1-2018 12:37, Paul wrote:
Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as
a home pc or a company pc. I choosed company pc, as it works in our
LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

And that worked ? ("I choosed company pc")

Yes, it did. No problem.

You're not supposed to do that.

The "free" upgrade is for *home* users. Whether installing Home
or Pro, you are a "home user". Pretend to be a humble home user.

Well, I have quite a humble nature :-) But I thought we have a
professional LAN.

That's a trick question to catch Enterprise end-users trying to
thwart their IT department by "pouring crap" over top of carefully
prepared IT OS installations. People were doing that at their
work, blowing away the company OS image, which is why the trick
question is there to stop the installation.

Yes, I can imagine. Once upon a time I performed maintenance on desktop
computers and the server in a community center.

The install should stop if you answer "as a business user".

No, it didn't.

Or, it'll fail to activate, and go into grace mode. It won't
be activated and after 30 days it'll indicate the end of the
grace period. The grace period exists so IT people can prepare a machine
for deployment, which may take days to do.

It activated very well.
It was not a W7 upgrade but a fresh W10 installation.

The Digital Entitlement, you have until the end of January
to generate one. This is a priority, and is what you need
to achieve now. The current date is Jan23 and not much
time remains for free upgrades. Check to see if it's activated.

slmgr /dlv

Does it say "activated" ?

In PC settings it says that Windows is activated with a digital license.

If you have a big investment (time spent) setting this up, then

1) make a backup of at least C: and System Reserved

2) slui 4

Enter the Win7 key and see if it is accepted.
I don't know if that will override how you answered The Question,
but it might. The idea is to convert the Win7 key
into a digital entitlement.

3) Verify with slmgr /dlv

4) If you screw up, you can restore from (1).

An alternative is:

1) Backup the current fully-fleshed Win10 install
2) Restore the Win7 image you made before this exercise started.

As it is a newly built pc with a fresh W10 installation, there is no W7
image.

You made a backup, right ? You're not relying on the
"Revert" capability to save you I hope. It works, but it
is slow and less than perfect.

3) Install Win10 over the restored Win7.
4) Answer "Home" user when The Question appears.
5) slmgr /dlv to check for Digital Entitlement and activation.

6) Now, restore the image from (1).
Check activation. Use the command to activate if
it's not activated, as the Digital Entitlement on the
MS server from (5) should be enough to authorize the
current installation.

The key message here is, get your "activation" status worked
out, no matter what, before the end of the month, or it's
going to cost you $150 to fix later. You want proof you
have Digital Entitlement now.

I did this on my current machine, on Dec.31 (when the idea
was, that was the last day). I got my Digital Entitlement
completed, then I removed Windows 10 from the machine (for
now). In future, I may need to restore it again, and
the Digital Entitlement is waiting for me when I need it.
It's like "free money" in a sense. Maybe if I sell my
computer, it'll be the OS of choice to put on it :-)
So I won't be wasting any other OSes.

The Digital Entitlement and free upgrade is available
until Jan.31 or so. Whatever the last day of the
month is.

*******

If you are actually Activated and that part is OK,
then there is less to worry about.

I'm happy to read that.

To enter Control Panels, use Start : Run and

control
control.exe

And that will bring up the traditional Control Panel interface.
You can pin this to the Task Bar so you won't have to do it
a second time.

In there, is a Troubleshooter control panel. Select it.

The Troubleshooter should have a box in the upper right
hand corner for "Search". Search for "Update" or
"Windows Update". You get the idea.

Yes, it says that some settings are set by the organisation (or
somethinh like that). Anyway, the automatic update is disabled, and I
don't mind. I can do that manually, can't I?
No, obviously not.


The Windows Update troubleshooter should be able to
clean out the gigabytes of files in SoftwareDistribution.
This has been known to help get Windows Update working
again. A script on tenforums.com is available to do this
too, and the TroubleShooter that Microsoft uses, does
all the same steps.

Ah. This reminds me of a trick with W7 updates trouble:
1) stop the windows update service
2) delete the Windows\SoftwareDistribution folder
3) restart the service
4) reopen the Update Windows dialog. Click the update
button.

Quess what? It's updating KB4054517 now.


After doing that, and trying Settings gear wheel and
"Updates and Security" from the Settings panel,
report back how many updates aren't installed or
are broken.

You can also download updates from catalog.update.microsoft.com.

Those come in executable .msu format.

To install one in relative peace, you can:

1) Download the KB file matching your OS, from the
selection you made in catalog.update.microsoft.com.
If you have a list of failed updates, you can download
all of those now, and save for the next steps.

2) Disconnect the network cable.
Reboot.
(This step puts wuauserv in a benign state. Since the
network is no longer available to the OS, then wuauserv
has no choice but to listen to the "query" from the
.msu you're about to launch.)

3) Double click the .msu to install.

4) If you have multiple .msu files, *don't* click the
reboot button you see. Only click reboot when the *last*
.msu is installed.

5) Do your reboot. Reconnect the network cable when you
feel like it.

That doesn't "force" an update, but it is an alternate
method to resolve a broken update. I've only had a couple
of occasions where that method didn't get me past a
"fail" one.

Using this process sounds like a good idea when everything else fails.

Or should I format the SSD and install W10 from scratch again, but this
time as a home user? I purchased an OEM license, would I be allright
with my activation again?

Thanks,
Fokke


HTH,
Paul

On 23-1-2018 12:25, Lucifer Morningstar wrote:
On Tue, 23 Jan 2018 11:50:26 +0100, Fokke Nauta
wrote:

Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as a
home pc or a company pc. I choosed company pc, as it works in our LAN as
a file-, print- and webserver. Sort of NAS. Perhaps some settings now
prevent a normal update?

Thanks in advance for your help.

You don't want 1709 so count yourself lucky.
However you can use W10 help.



Fokke Nauta


I have 1709, whatever it might be. No good?

On 23-1-2018 13:40, Fokke Nauta wrote:
On 23-1-2018 12:37, Paul wrote:
Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as
a home pc or a company pc. I choosed company pc, as it works in our
LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta


cut



The Windows Update troubleshooter should be able to
clean out the gigabytes of files in SoftwareDistribution.
This has been known to help get Windows Update working
again. A script on tenforums.com is available to do this
too, and the TroubleShooter that Microsoft uses, does
all the same steps.

Ah. This reminds me of a trick with W7 updates trouble:
1) stop the windows update service
2) delete the Windows\SoftwareDistribution folder
3) restart the service
4) reopen the Update Windows dialog. Click the update
button.

Quess what? It's updating KB4054517 now.

Well, it did and it required a restart after installing. After that I
went looking for updates again but it tried to download the same update
again. This time it won't download. And it said that the installation of
KB4054517 failed.

So - back to square one :-(

After doing that, and trying Settings gear wheel and
"Updates and Security" from the Settings panel,
report back how many updates aren't installed or
are broken.

You can also download updates from catalog.update.microsoft.com.

Took a look into that. There are so many drivers that I don't know which
ones to choose.


Those come in executable .msu format.

To install one in relative peace, you can:

1) Download the KB file matching your OS, from the
selection you made in catalog.update.microsoft.com.
If you have a list of failed updates, you can download
all of those now, and save for the next steps.

2) Disconnect the network cable.
Reboot.
(This step puts wuauserv in a benign state. Since the
network is no longer available to the OS, then wuauserv
has no choice but to listen to the "query" from the
.msu you're about to launch.)

3) Double click the .msu to install.

4) If you have multiple .msu files, *don't* click the
reboot button you see. Only click reboot when the *last*
.msu is installed.

5) Do your reboot. Reconnect the network cable when you
feel like it.

That doesn't "force" an update, but it is an alternate
method to resolve a broken update. I've only had a couple
of occasions where that method didn't get me past a
"fail" one.

Using this process sounds like a good idea when everything else fails.

Or should I format the SSD and install W10 from scratch again, but this
time as a home user? I purchased an OEM license, would I be allright
with my activation again?

Thanks,
Fokke


HTH,
Paul

Fokke Nauta wrote:

Or should I format the SSD and install W10 from scratch again, but this
time as a home user? I purchased an OEM license, would I be allright
with my activation again?

Thanks,
Fokke

If your Windows Update is working, do you really need to test that ?

The OEM license would likely be a System Builder license, as
a royalty license for Win10, would include an MSDM table
in the BIOS chip for re-activation. I'm not really sure
whether MS does anything to help a System Builder. It could
be that you have to enter the key the second time as well.

It would be easy for Microsoft to keep a record of each
activation, and realize your machine had "burned" a System
Builder OEM key. As you're not supposed to be able to transfer
such a key to a second machine. But do they do it that way ? Dunno.

I have one activation here, where how it happened remains
a mystery. The OS is activated, but no qualifying OS was
present at the time. I suspect there was some sort of
confusion between the Insider Editions I was running
and the Release edition. And maybe it came up on an
operator "scope" at Microsoft and they just approved it
as some sort of bug. I know that two Insider Editions
got into a squabble and I had to reenter account and
password at one point, while that got worked out.

Really, just about anything is possible with that
activation server.

Paul

On 23-1-2018 14:00, Paul wrote:
Fokke Nauta wrote:

Or should I format the SSD and install W10 from scratch again, but
this time as a home user? I purchased an OEM license, would I be
allright with my activation again?

Thanks,
Fokke

If your Windows Update is working, do you really need to test that ?

Well, it's still not working. Downloaded a W10 update repair tool from
MS and it fixed several issues.
But it still won't update ...


The OEM license would likely be a System Builder license, as
a royalty license for Win10, would include an MSDM table
in the BIOS chip for re-activation. I'm not really sure
whether MS does anything to help a System Builder. It could
be that you have to enter the key the second time as well.

It would be easy for Microsoft to keep a record of each
activation, and realize your machine had "burned" a System
Builder OEM key. As you're not supposed to be able to transfer
such a key to a second machine. But do they do it that way ? Dunno.

I have one activation here, where how it happened remains
a mystery. The OS is activated, but no qualifying OS was
present at the time. I suspect there was some sort of
confusion between the Insider Editions I was running
and the Release edition. And maybe it came up on an
operator "scope" at Microsoft and they just approved it
as some sort of bug. I know that two Insider Editions
got into a squabble and I had to reenter account and
password at one point, while that got worked out.

Really, just about anything is possible with that
activation server.

Paul

Fokke Nauta wrote:

Paul wrote:

You can also download updates from catalog.update.microsoft.com.

Took a look into that. There are so many drivers that I don't know which
ones to choose.

Use the search box at the upper right corner to hunt for the updates by
number that you want to download.

On 1/23/2018 5:50 AM, Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says:Â* 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as a
home pc or a company pc. I choosed company pc, as it works in our LAN as
a file-, print- and webserver. Sort of NAS. Perhaps some settings now
prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

Try the Windows Update Troubleshooter

https://support.microsoft.com/en-us/help/10164

Ben

On 1/23/2018 3:02 PM, Ben Myers wrote:
On 1/23/2018 5:50 AM, Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says:Â* 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as
a home pc or a company pc. I choosed company pc, as it works in our
LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

Try the Windows Update Troubleshooter

https://support.microsoft.com/en-us/help/10164

Ben
Don't give up it took me some months to finally get my tablet to upgrade
to 1709. I can't tell you what I did precisely, but it may have been
that not all of the previous version updates had been applied.

--
2017: The year we learn to play the great game of Euchre

Fokke Nauta wrote:
On 23-1-2018 14:00, Paul wrote:
Fokke Nauta wrote:

Or should I format the SSD and install W10 from scratch again, but
this time as a home user? I purchased an OEM license, would I be
allright with my activation again?

Thanks,
Fokke

If your Windows Update is working, do you really need to test that ?

Well, it's still not working. Downloaded a W10 update repair tool from
MS and it fixed several issues.
But it still won't update ...

Is grabbing a .msu file from catalog.update.microsoft.com working ?

I would jam in the files until all of them were accepted.

You can use Sysinternals.com Process Monitor, to log all
the WriteFile calls, and see where the update is writing.
Perhaps it uses CBS logfile ? I've even used Process Monitor
to log a Macrium Reflect backup (twenty minutes worth
of computing activity), so you can create huge traces
with it. My trace in that case was 9GB in size, on an
x64 system.

Paul

On 01/23/2018 2:33 PM, Keith Nuttle wrote:
On 1/23/2018 3:02 PM, Ben Myers wrote:
On 1/23/2018 5:50 AM, Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked with
W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But I
can't update Windows.
It says:Â* 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it as
a home pc or a company pc. I choosed company pc, as it works in our
LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

Try the Windows Update Troubleshooter

https://support.microsoft.com/en-us/help/10164

Ben
Don't give up it took me some months to finally get my tablet to upgrade
to 1709.Â* I can't tell you what I did precisely, but it may have been
that not all ofÂ* the previous version updates had been applied.



Might this help? Paul would Know.

DISM.exe /Online /Cleanup-image /Restorehealth

Rene

Rene Lamontagne wrote:
On 01/23/2018 2:33 PM, Keith Nuttle wrote:
On 1/23/2018 3:02 PM, Ben Myers wrote:
On 1/23/2018 5:50 AM, Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked
with W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But
I can't update Windows.
It says: 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it
as a home pc or a company pc. I choosed company pc, as it works in
our LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

Try the Windows Update Troubleshooter

https://support.microsoft.com/en-us/help/10164

Ben
Don't give up it took me some months to finally get my tablet to
upgrade to 1709. I can't tell you what I did precisely, but it may
have been that not all of the previous version updates had been applied.



Might this help? Paul would Know.

DISM.exe /Online /Cleanup-image /Restorehealth

Rene


Isn't this a fresh install though ?

What are the odds a fresh install has a damaged WinSXS ?

I'd like to get some tiny hint from the OP, that'll
head us in the right direction.

Finding the right log file would be a start.
Is that the CBS log ? Or some other log ?

Paul

On 01/23/2018 4:22 PM, Paul wrote:
Rene Lamontagne wrote:
On 01/23/2018 2:33 PM, Keith Nuttle wrote:
On 1/23/2018 3:02 PM, Ben Myers wrote:
On 1/23/2018 5:50 AM, Fokke Nauta wrote:
Hi all,

Recently built a new pc and installed W10 Pro x64. Always worked
with W7; W10 is new to me.
Installation worked will, all necessary programs are installed. But
I can't update Windows.
It says:Â* 2017-12 Cumulative Update for Windows 10 Version 1709 for
x64-based Systems (KB4054517). Awaiting restart.
After restarting it says: We could'n finish installing updates.
Then it shows an overview:
KB4054517 (9) failed to install
KB4056887 Requires restart
KB4058043 Requires restart
KB4056892 failed to install

So - what's wrong here?
Whilst installing W10 I was asked to choose as to whether using it
as a home pc or a company pc. I choosed company pc, as it works in
our LAN as a file-, print- and webserver. Sort of NAS. Perhaps some
settings now prevent a normal update?

Thanks in advance for your help.

Fokke Nauta

Try the Windows Update Troubleshooter

https://support.microsoft.com/en-us/help/10164

Ben
Don't give up it took me some months to finally get my tablet to
upgrade to 1709.Â* I can't tell you what I did precisely, but it may
have been that not all ofÂ* the previous version updates had been
applied.



Might this help? Paul would Know.

DISM.exe /Online /Cleanup-image /Restorehealth

Rene


Isn't this a fresh install though ?

What are the odds a fresh install has a damaged WinSXS ?

I'd like to get some tiny hint from the OP, that'll
head us in the right direction.

Finding the right log file would be a start.
Is that the CBS log ? Or some other log ?

Â*Â* Paul

It sounds like a clean install but he mentions win 7 in the same
sentence! so I'm not sure.
I have only used this command on an upgraded system so not sure if it
would help a new install, May be worth a shot anyway in case all the
trying to upgrade may have done some damage.

Rene