Alan
asked on
Win 10 Pro - Failing to Update from 1703 to 1709 - Windows Setup could not configure Windows to run on this computer's hardware
Hi All,
We are running updates on Win10 Pro machines, and have one that refuses to update for some reason.
It is currently on Win10 Pro 1703 (Version 10.0.15063.909) and should be updating to 1709, but it continually fails with the error:
"Windows Setup could not configure Windows to run on this computer's hardware"
The machine is a Surface Pro 3, and has had no other issues that we know of.
We have tried freeing up disk space, but this seems to make no difference (and the machine passes the 'upgrade requirements' checks, including the disk space check fine).
Searching on the web throws up many and varied suggestions, including, for example, removing the IIS Admin service with a command such as:
So, question is, how should we approach this? Where to start?
Thanks,
Alan.
We are running updates on Win10 Pro machines, and have one that refuses to update for some reason.
It is currently on Win10 Pro 1703 (Version 10.0.15063.909) and should be updating to 1709, but it continually fails with the error:
"Windows Setup could not configure Windows to run on this computer's hardware"
The machine is a Surface Pro 3, and has had no other issues that we know of.
We have tried freeing up disk space, but this seems to make no difference (and the machine passes the 'upgrade requirements' checks, including the disk space check fine).
Searching on the web throws up many and varied suggestions, including, for example, removing the IIS Admin service with a command such as:
sc delete iisadmin
However, I figured I'd rather ask here and gather views on the best way to approach this more methodically than just trying random things someone found via Google.So, question is, how should we approach this? Where to start?
Thanks,
Alan.
Check that the following services have been set to Auto start and reboot. Also run an SFC /ScanNow, and run Cleanmgr or Ccleaner to delete old files. You can also delete old update files from c:\Windows\SoftwareDistrib ution\Down load folder.
Services need to be set to autostart: Windows Update (wuauserv), BITS, Cryptographic Services (cryptsvc), TrustedInstaller.
See https://forums.techguy.org/threads/kb4056892-not-loading.1207391/#post-9489015
Services need to be set to autostart: Windows Update (wuauserv), BITS, Cryptographic Services (cryptsvc), TrustedInstaller.
See https://forums.techguy.org/threads/kb4056892-not-loading.1207391/#post-9489015
I found installing from here somehow seemed to resolve the problem. It will first check for compatibility. Click the "update now" button.
https://www.microsoft.com/en-ca/software-download/windows10
https://www.microsoft.com/en-ca/software-download/windows10
I agree with Rob on using the Media Creation Link. I find that to be the preferred approach. We have one or two machines that did not update and this is how we did it.
Be sure to update BIOS, Chipset and Video drivers before doing this. The Meltdown Threat requires both firmware and operating system updates.
If you are using a third party AV (other than Windows Defender), uninstall it before proceeding with the above and install it again when all complete.
Be sure to update BIOS, Chipset and Video drivers before doing this. The Meltdown Threat requires both firmware and operating system updates.
If you are using a third party AV (other than Windows Defender), uninstall it before proceeding with the above and install it again when all complete.
You should upload setuperr.log so anyone can look at it.
ASKER
Hi Guys,
Thanks for the replies so far. I will work through them one by one.
McKnife: Which setuperr.log do you mean? There are actually quite a few on the C:\ drive at this point. Maybe I should delete them all first, then try a suggestion from above, and if it fails, the setuperr.log file(s) must relate to that attempt?
Thanks,
Alan.
Thanks for the replies so far. I will work through them one by one.
McKnife: Which setuperr.log do you mean? There are actually quite a few on the C:\ drive at this point. Maybe I should delete them all first, then try a suggestion from above, and if it fails, the setuperr.log file(s) must relate to that attempt?
Thanks,
Alan.
The one in the temporary update folder, which is C:\$Windows.~BT\Sources\Pa nther
Alan, an experienced member like you should not go without feedback, right :-) ?
ASKER
Hi McKnife,
Yes, you are right - apologies!
I didn't actually have any feedback (I should have posted to say that ), as we are wanting to do a full backup first, and that is scheduled for this Friday evening (overnight).
We will then try some of the above, and I will also delete the entire C:\$Windows.~BT\ directory prior to doing the updates, so that whatever logs are in there afterwards, must relate to our latest attempt(s) and I can then post back here.
Thanks for your patience,
Alan.
Yes, you are right - apologies!
I didn't actually have any feedback (I should have posted to say that ), as we are wanting to do a full backup first, and that is scheduled for this Friday evening (overnight).
We will then try some of the above, and I will also delete the entire C:\$Windows.~BT\ directory prior to doing the updates, so that whatever logs are in there afterwards, must relate to our latest attempt(s) and I can then post back here.
Thanks for your patience,
Alan.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Lately, Microsoft published a new tool: https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
SetupDiag.exe is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
ASKER
Hi Guys,
We got the laptop from the user on Friday, and ran a full image backup using dd from a live Ubuntu USB drive.
We then tried running the updates with no USB connections, and that worked.
Seems very odd why that would cause the problem, but it appears it was the case here.
Thanks for your patience,
Alan.
We got the laptop from the user on Friday, and ran a full image backup using dd from a live Ubuntu USB drive.
We then tried running the updates with no USB connections, and that worked.
Seems very odd why that would cause the problem, but it appears it was the case here.
Thanks for your patience,
Alan.
please find the best guide to prepare for creators upgrade...
https://www.groovypost.com/howto/prepare-computer-windows-10-creators-update-version-1703/
and
step by step to upgrade the version
https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install-winpc/how-to-upgrade-to-windows-10-version-1709-fall/617a37da-8fc0-4f33-a3eb-59fe9082f925
all the best