Update 1709 to 1803

Page 1 of 7 123 ... LastLast

  1. Posts : 128
    windows 10 64-bit "home"
       #1

    Update 1709 to 1803


    Hello,

    I know, I know - countless problems with that update everywhere.

    In short: since the inception of the 1803 update in October 2018 my computer tries to bring that update to a good end - in vain. And this several times a week, with a considerable slowing down of the machine at each try - so much so that I had to make the update service inactive while working, so as not to imper my work.

    Seeing no solution to this problem, and reading the often contradictory information about this ubiquitous problem, I finally contact Microsoft over here in Belgium. After checking everything - and trying a partial reinstall (while keeping all files), which also failed after the second restart, those helpful people at Microsoft told me that 1709 contained a blocking element which made the update impossible. So, wonderful recommendation (as usual): back up everything on C and do a clean reinstall.

    Now, is that really, really necessary? Nobody told me of course what the blocking element was, they just confirmed the error code: 0x800700d8. But it is my experience with Microsoft that when a problem gets a bit too complex and that they really must devote time to it, they just go into "total reinstall" retreat.

    So, maybe there is a less drastic solution to my problem somewhere. Could find anything except complaints about similar difficulties for Forum 10 users.

    Meanwhile, I'll avoid updates. My actual version works okay (even with a number of ridiculous quirks, which are not as annoying as the one described above).

    Thanks for perhaps redirecting me to some threads or tutorials that wull show me the way.

    haku
      My Computer


  2. Posts : 43,004
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, please start with basics: check your disk, file system and system files:

    Download and run Hard Disk Sentinel (trial) (incl. SSDs) and post a screenshot of its GUI.
    If ok, from an admin command prompt run
    chdsk c: /SCAN
    and post the summary result

    If ok, run
    SFC /SCANNOW
    and post the summary result.

    Please post a screenshot of your partitions using Minitool Partition Wizard (free) - not Disk Management- expanding columns so all text is visible.
    To post a screenshot please use the Insert Image icon above your post.

    Now, build 1809 has been out for around 3 months, and now 1903 is not far off. There is little point in upgrading to 1803- you could at least upgrade to 1809.

    Please download an iso for 1809 using Microsoft's media creation tool. (Easy to find).
    @zbook will want to take this thread on.

    Noted you started a thread on this here without a conclusion or providing requested results as far as I can see, so given that effort, I'll now leave you hoping someone else will take this on.
    File Associations Keep Reverting to Windows 10 Defaults - Page 2 - Windows 10 Forums
      My Computers


  3. Posts : 128
    windows 10 64-bit "home"
    Thread Starter
       #3

    Hi Dalchina,
    Thanks for the quick answer.
    In fact, when taking over the computer momentarily, the Microsoft help people (I had 3 in a row) seem to have done a series of tests.
    However, none of the ones you recommend.
    I'll do these.
    What galls me, is that they didn't even mention, as you do, version 1809 and/or the coming 1903.
    Well, we'll see what your series of tests come up with. Apart from that annoying update problem, my 3-year old PC seems to work without a hitch. We shall see.

    Haku
      My Computer


  4. Posts : 128
    windows 10 64-bit "home"
    Thread Starter
       #4

    Hi again,
    No problem with HD Sentinel nor chkdsk c:/scan. Everything seems okay (see relevant screenshots). However a snag with SCANNOW, as you will see on the attached screenshot.

    What shall I do?

    haku
    Attached Thumbnails Attached Thumbnails Update 1709 to 1803-test-f10-01-hd-sentinel.jpg   Update 1709 to 1803-test-f10-02-scan.jpg   Update 1709 to 1803-test-f10-03-scannow-failed.jpg  
      My Computer


  5. Posts : 43,004
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5
      My Computers


  6. Posts : 128
    windows 10 64-bit "home"
    Thread Starter
       #6

    To all intents I attach already the Minitool GUI. All seems okay there too.

    haku
    Attached Thumbnails Attached Thumbnails Update 1709 to 1803-test-f10-04-minitool-partition.jpg  
      My Computer


  7. Posts : 128
    windows 10 64-bit "home"
    Thread Starter
       #7

    Thanks. But what options shall I use, recommended in that link?

    1. System File Checker SFC cannot repair corrupted member file
    2. Windows Resource Protection found corrupt files but was unable to fix some of them
    3. System File Checker not working, will not run or could not repair.

    If this happens, you may try to Run System File Checker in Safe Mode or at Boot Time or repair the Windows Component Store using DISM and see if it works, or you may troubleshoot the errors individually, by following the individual links.
    Never done anything of the sort, so I'm being cautious...

    haku
      My Computer


  8. Posts : 43,004
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #8

    Trying to run sfcWindows Resource - Microsoft Community

    Besides my post #5 (Boot to Safe Mode and try running SFC /SCANNOW), please do this:

    Windows key + R
    services.msc

    maximise the window and post a screenshot.

    Also run Hard Disk Sentinel again and look at Disk 2 (65%) and post the GUI.

    Minitool screenshot: plenty of space on C: but I'd want someone familiar with MBR to check the details.
    I don't know why C: isn't Active, Boot and System
      My Computers


  9. Posts : 128
    windows 10 64-bit "home"
    Thread Starter
       #9

    Found something about the matter lower on the "WindowsClub" page of instructions, trying this out: Starting Service Windows Modules Installer. Hope I'm not doing anything dangerous...
      My Computer


  10. Posts : 43,004
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #10

    Boot to Safe Mode and retry SFC /SCANNOW

    If this happens, you may try to Run System File Checker in Safe Mode or at Boot Time
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:48.
Find Us




Windows 10 Forums