Issues Updating from 1703 to 1709

We fully understand that you want to upgrade to version 1709 without any issues.  Since you're unable to reset the Windows Update components, it is best to do a clean install. Like what we've mentioned, an issue with Windows 10's system files can be the reason why you're unable to update. We need to replace your copy of Windows 10 so that we can resolve the issue. By completely replacing your copy of Windows 10, not only will you be able to update to the latest version, it will also eliminate the possibility of experiencing the same Windows Update issue in the future. This is because you're now using a brand new copy of Windows 10.

If you do not prefer to perform a clean install, we suggest performing a custom install. A custom install will only remove your programs. All of your files will not be deleted. You can refer to this article if you want to perform a custom install.

If you're going to perform either a clean install or custom install, kindly remove any extra peripheral devices. You mentioned in your reply in January 7, 2018, that you're encountering the 0xC1900101 – 0x30018 error code. This means that a device driver has stopped responding to setup.exe during the upgrade process. Since you're using a laptop, make sure that you're only using the built-in components of the computer.

If the issue persists after performing a custom install, we highly recommend that you do a clean install of Windows 10. If you do not want to perform a clean install, we encourage you to submit your issue using the Feedback Hub.  You can either vote on an existing submission or submit a new issue. When you submit a feedback item we gather additional details and information about your issue that will help determine what’s causing it and address it. Feedback items regularly receive Microsoft responses on the submissions in the Feedback app so you can see what we are doing about your feedback. Please revisit frequently to see the status of your feedback items. 

For more information on Feedback Hub, see our support article.

In order to submit new feedback, please follow these steps:

1. On a Windows 10 device, search for “Feedback Hub” in Cortana search, then launch the app.
2. Navigate to Feedback in the left menu, then press + Add new feedback.
3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory.
4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you’re done.
5. Once you’ve completed the form and monitoring, click Submit.
6. Click Continue using Feedback Hub.
7. 7Click My feedback at the top, then find the item you submitted (it may take a while to appear).
8. Open the item you submitted, then click Share.
9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>).

Best regards.

Hi AO,

         Thank you for the information. 

         You will find that you misread or misunderstood my comment about Command Prompt, entering even copies of the commands is time consuming and I cannot run the commands as a batch, I don't know how.  You will find that I reported all the errors that occurred during my last resetting of the Update components.  I assume copies of the error reports from previous 1709 failures were extracted by the Help Desk but obviously those files have no value.

          # I fail to understand why system files should be wrong in any way after any of:-

a/. Running a Command Prompt for sfc /scannow where unfixable files are reported and anything else corrected

b/. Running the DISM Tool to find, and then again to fix, any errors found.

c/.  Running an .iso of the current 1703 OS as an Upgrade Install.

We seem to be covering the same old ground yet again; I appreciate that you only answer on the basis of the last post and forget the forgoing amongst everything else.  Do you think you can speed read the whole thread to see if there is anything you have missed?

            I would appreciate some answer to the # paragraph please, for my education.

I use Feedback all the time for things wrong, errors and solutions I have found.  I have been doing so since the first Consumer 10 was available for testing!  I had hoped that all of my time on behalf of Microsoft could possibly be repaid in helping me find the cause of this problem and a clean reinstall will not do that.  The answer to this problem will benefit both of us, less problems for users means happier users/clients.

            For me to do a clean install is a failure for us both and one more bug to be included in every future incarnation if Windows: A rare bug today may be very common tomorrow.   In 1703 it was a failure to ensure that all the necessary Updates were in place, found and reported as required before 1703 would install.  Microsoft failed me on the Win 8 to Win 8.1 Upgrade and blamed the problem on the Dell image of Win 8.  That is not the case here as the .iso came directly from Microsoft servers under a new licence for the Pro version.

            I have worked hard to find solutions with no expectation of thanks from Microsoft or any to whom the advise has helped, regardless of which Account I have used to do so.  FYI, I changed my account to restrict myself to Win10 only, similarly with Win 8.

            I remember the many thousands of users seeking an answer to the failure of the 8.1 Upgrade, so many that some of use were farmed out to other IT to help with the overload, The removal of similar thread references and the way in which the Community Website has changed disguise the size of any problem.

           Regarding a report of the issue in Feedback (which I did last month), I take it to mean that Microsoft take no notice of the Community site members and the help they seek when looking at the total of problems discovered.

Running both the SFC and DISM tools will check for system corruption and image errors. There are times that these tools will not be able to detect the error in the system files. If you're still having an issue updating to the version 1709 even when SFC and DISM tools did not find any issues, there is a possibility that the tools was not able to detect the corrupted system files. This is the reason why we need to perform either a custom install or clean install. This is for us to fully replace your copy of Windows 10. You mentioned on the third item that you're tried running the version 1703 ISO file of Windows 10. If you're using this to perform a repair upgrade or in-place upgrade, we recommend that you use the latest ISO file of Windows 10 which has the version 1709 update. If you;'re already using the latest ISO file of Windows 10 and you still cannot upgrade by performing an in-place upgrade, the current system files of Windows 10 may also be hindering you from upgrading to the latest version. This is also why we're suggesting that you perform a clean install or a custom install.

Please take note that when a user posts an issue in the Feedback Hub, other users can upvote it if they have the same problem. You can also post the link of your Feedback Hub post here so that other community member who has the same issue can upvote it.

Thanks.

Hi

Restarting my laptop this evening :-

1/.  The 1709 Update is yet again being downloaded regardless of the Administrative Template setting.   I have been forced to DISABLE UPDATES while I get this problem sorted.  I will do all re Update reset required and then run the full 1709 .iso as an Upgrade.  Should that fail I will then report such and use the same image for a clean install.

2/.  After the installation of the latest 1703 update KB4057144 I now find Edge now will not use the extension for Lastpass, since it is the only extension I use I could apply to all extensions.

Kindly update us if you're able to update to version 1709 after resetting the update, running the full 1709 ISO file, and performing a clean install.

Regarding the extension in Microsoft Edge, we recommend that you temporarily disable it and enable the extension again to see if Microsoft Edge will start using the extension again.