Upgrade from 1809 to 1903 seems to be in a loop

Page 2 of 2 FirstFirst 12

  1. Posts : 92
    Windows 10
    Thread Starter
       #11

    Bree said: View Post
    Use Option Five in this tutorial to see what your SFC errors are.
    Run SFC Command in Windows 10
    Bree, thank you for the SFC Details link. Attached is the result. An initial look through the result seems to indicate that all the problems are associated with Windows Defender - as suggested may be the case in your previous Post.

    Tomorrow I will create the ISO. Before running the ISO is there any way to check the integrity of the ISO update?

    Thanks

    T.
    Upgrade from 1809 to 1903 seems to be in a loop Attached Files
      My ComputerSystem Spec

  2. Bree's Avatar
    Posts : 12,406
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #12

    Tabvla said: View Post
    Before running the ISO is there any way to check the integrity of the ISO update?
    Not directly, but before creating the .iso file the MCT checks the integrity of all the files it has downloaded to create the ISO.
      My ComputersSystem Spec


  3. Posts : 92
    Windows 10
    Thread Starter
       #13

    Firstly, thanks for the advice and apologies for the long delay in replying.

    Bree.... two things of which I am not sure.

    1. Macrium

    In the past I have always used the Microsoft system image utility as found in File History with the associated Recovery Boot USB. Following your suggestion, I installed Macrium Free and created a system image on an HDD and recovery boot medium on a DVD. On page 322 of the Macrium User Guide it shows the Macrium recovery boot menu consisting of two options, Windows 10 and Macrium Reflect System Recovery. When I restart the computer it simply goes straight into Windows as normal and does not show this recovery boot menu. Did I miss something when I created the recovery DVD..?

    2. W10 v 1903 ISO

    As per your suggestion I followed Shawn's Tutorial to download and create an ISO. The Microsoft site does not specifically recommend this method for updates. The site states that the ISO method is to be used when upgrading from an older version of Windows (XP, Vista....) or installing Windows on another machine. I am just wondering if the ISO method is appropriate for a version update.

    Thanks

    T.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 8,802
    Windows 10 Pro X64 1903 18362.295
       #14

    If the Macrium recovery is on a DVD then you need to boot the DVD to use Macrium Rescue (Recovery). Then you would click on Restore and Browse for an image file, navigate to the image backup you made on the HDD and select it. Then you would click on Restore image and that will restore the image to the drive you specify (be careful, make sure you pick the right one). When done your PC will be back to exactly where it was when the image was created.

    You can do this as many times as you need or want.

    When you created the image, did you select all partitions on the drive? If not you should have as many times it's one of the other partitions that gets corrupted that prevents you from being able to boot and not the Windows 10 partition.
      My ComputersSystem Spec

  5. Bree's Avatar
    Posts : 12,406
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #15

    Tabvla said: View Post
    ... the Macrium recovery boot menu consisting of two options, Windows 10 and Macrium Reflect System Recovery. When I restart the computer it simply goes straight into Windows as normal and does not show this recovery boot menu. Did I miss something when I created the recovery DVD..?
    No, the DVD is fine. What you missed is that adding Macrium as a boot menu option is a separate independent option that you can add in addition to creating the bootable DVD or USB. Click on Windows Boot Menu in the list of devices and you will see at the bottom the options to add Macrium to the boot menu.

    Click image for larger version. 

Name:	image.png 
Views:	34 
Size:	17.2 KB 
ID:	242450



    The Microsoft site does not specifically recommend this method for updates. The site states that the ISO method is to be used when upgrading from an older version of Windows (XP, Vista....) or installing Windows on another machine. I am just wondering if the ISO method is appropriate for a version update.
    Yes, it is a perfectly good way to upgrade from one version of W10 to the next and the one I've been using for every version from 1511 to 1903. Microsoft's advice is read by those who may have little knowledge of computers, so they have to be careful to avoid suggesting anything too technical. Allowing the Update Assistant to do all the work for you is 'safe' advice under those circumstances.
      My ComputersSystem Spec


  6. Posts : 92
    Windows 10
    Thread Starter
       #16

    Ztrucker.... thank you for your "heads-up" on the partitions. I am not sure, I simply left the settings as per the Macrium default, which I think included all the partitions except the one allocated to "Data". The next time that I do this I will be sure to check.

    Bree..... thank you for answering my questions and for the Screenshot. I will rerun Macrium and add Macrium to the Boot Menu.

    I will keep this Thread open until I have completed the 1903 upgrade.

    T.
      My ComputerSystem Spec



  7. Posts : 92
    Windows 10
    Thread Starter
       #17

    Bree and Ztruker......

    Thank you for your advice with regards to installing 1903. The installation has now been completed.

    SFC is still reporting..... "Windows Resource Protection found corrupt files but was unable to fix some of them". Extracting the SFC Details the errors are the same as before and all seem to be related to Windows Defender.

    I attach the SFC Details file for your information.

    T.
    Upgrade from 1809 to 1903 seems to be in a loop Attached Files
      My ComputerSystem Spec


  8. Posts : 27,176
    windows 10 professional version 1607 build 14393.969 64 bit
       #18

    The CBS log displayed hash mismatches.

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow

    6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread





    Code:
    2019-09-03 10:27:08, Info                  CSI    00000239 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    0000023b [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    0000023d [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    0000023f [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    00000241 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    00000243 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    00000245 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    00000247 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:08, Info                  CSI    00000249 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    0000024d [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    0000024e [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000250 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000251 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000253 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000254 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000256 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000257 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000259 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    0000025a [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    0000025c [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    0000025d [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    0000025f [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000260 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000262 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000263 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000265 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-09-03 10:27:13, Info                  CSI    00000266 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-09-03 10:27:13, Info                  CSI    00000269 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    0000026c [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    0000026f [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    00000272 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    00000275 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    00000278 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    0000027b [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    0000027e [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    00000281 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted
    2019-09-03 10:27:13, Info                  CSI    00000282 [SR] Verify complete
      My ComputerSystem Spec


  9. Posts : 92
    Windows 10
    Thread Starter
       #19

    zbook.... thanks for your reply.

    I will post when completed.

    T.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Greetings I haven't gotten the Feature Update notification in Update and Security, so I decided to download the Upgrade Assistant to do the update manually. I ran the download assistant and got 3 green check marks. The update seemed to...
I am on version 1803 PRO 64-bit. Ever since 1809 was made available, I was not able to get a successful upgrade after at least 10 attempts over the 6 months since 1809. Each time after the second reboot and after the "48 Percent "message the...
Being in the slow ring, 1903 turned up on checking via Windows Update. I fresh installed 1809 a few months ago, don't particularly want to do that again with all the settings and software to sort. Have now installed 1903 at least 6 times, allegedly!...
Solved 1809/1903 in General Support
Will I still be eligible for Windows 1903 update seeing as how I never got the 1809 update.?Apparently tried to update 1/1/19 but for some unknown reason failed and no further attempt. Thank You
Hi all, After upgrading to 1809 from 1803 my laptop is stuck in boot loop. The boot sequence is now - Lenovo logo, blank screen, Lenovo logo (different resolution), blank screen, reboot. Here's what I tried - Windows 10 repair (created now...
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 20:18.
Find Us