Windows 10: Windows 10 fails to upgrade i'm about to give up. Solved

Page 1 of 2 12 LastLast

  1. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
       30 Dec 2017 #1

    Windows 10 fails to upgrade i'm about to give up.


    Hi People,

    A few days ago a blue dialog popped up on my screen saying the windows 10 fall creator update was ready to be installed so i did but it fails each and every time i try to install it.Things i tryed to solve the problem are


    • Remove my kaspersky internet securtity.
    • unplug all uncessary devices.
    • check my hard drive for errors (chkdsk /f /r) did not find any errors.
    • sfc /scannow (no integrety violations detected).
    • dism /online /cleanup-image /restorehealth (says restore operation completed successfully).
    • i tryed with "windows update assistant" it passes the short test but fails at the end.
    • i tryed media creation tool to create a usb stick it failed but that's because i discovered the stick has a problem.


    However i do see a problem every time i run "windows update troubleshooter" it finds and solves the same problem(s) but it continues to offer the same updates multiple times also i can't read the windows update log the logs says

    1601/01/01 01:00:00.0000000 528 11776 Unknown( 15): GUID=1f9e54c8-9e31-3e53-867d-d9f39756ad7f (No Format Information found).
    1601/01/01 01:00:00.0000000 528 11776 Unknown( 10): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).
    I know there is an update for the windows update log problem Windows update log problem in 1607 Solved - Windows 10 Forums however i'm on Windows 10 Pro 1607 build 14393.1066 and since windows update is not offering me updates i don't know howto solve the problem i tryed to reset the windows update components several times always the same result it keeps offering the same updates i'm out of ideas i'm just guessing now but could the problem be caused by my wifi connection ? hmmm i feel like trying an utp cable .
      My ComputerSystem Spec

  2.    30 Dec 2017 #2

    Hi,
    Please post a screenshot of your partition layout using Minitool Partition Wizard, expanding columns as necessary to show all text - for all disks. Do not use Disk Management.
    To post a screenshot please use the icon above your post to the left of the video icon.

    Troubleshooting:
    Try post #14 here
    1709 Fails to install and how to remove multiple recovery partitions? - Page 2 - Windows 10 Forums

    You can try deleting the content of
    %temp%
    and
    C:\Windows\SoftwareDistribution\Download

    and
    Reset Windows Update in Windows 10 Windows Update Activation Tutorials

    You could try an in-place upgrade repair which keeps all programs and data on your anniversary build, then try upgrading to 1709. If you don't still have an iso, it's possible to get one.
    E.g.
    Microsoft Windows 10 Anniversary Update 1607 Download (Build 14393.0)

    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
    - but use the 1607 iso.

    Then you can download the iso for build 1709 and try upgrading manually.

    As ever, and we recommend this strongly to be used routinely, create or update a full disk image of Windows using e.g. Macrium reflect (free), to a external storage in case things go badly wrong and your PC becomes unbootable.
      My ComputerSystem Spec


  3. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
    Thread Starter
       30 Dec 2017 #3

    hi,

    Click image for larger version. 

Name:	partitions.JPG 
Views:	3 
Size:	91.6 KB 
ID:	170159

    Yes i've readed this somewhere while looking for information as i understand my system is several updates behind and windows update must first work correctly in order to get fall creator update.The "bad disk" in the image is that usb stick i mentioned earlier suddenly it became write protected no idea why there is no switch for this on the stick body.

    thank you for the help
      My ComputerSystem Spec


  4. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
    Thread Starter
       30 Dec 2017 #4

    Another thing i notice is that the services windows update uses like the bits service do not start when i set the service to automatic it seems to stop while i didn't do anything except trying to fix windows update
      My ComputerSystem Spec

  5.    30 Dec 2017 #5

    Hi,
    Before making any changes, ensure you have a current disk image of Windows on an external disk.

    Two things occur looking at your partitions:
    1. There's no free unallocated space. You should have, say, 1.5Gb (it's up from around 450Gb formerly) free for the creation of a new Recovery partition. So you need to use a partition manager to create that space.

    2. Your Boot partition is wrong.

    Compare the right hand column of mine with yours:
    Click image for larger version. 

Name:	Partitions.jpg 
Views:	1 
Size:	25.3 KB 
ID:	170170

    I suggest you try booting your PC from either a Macrium Reflect bootable disk (free) or Kyhi's boot disk - available from the top of the Software and Apps section here, which also has Macrium on it.

    Run Macrium's Fix boot utility and see if that helps.

    Please advise try that first before anything else and again post a screenshot of your partitions when done.

    Obviously there's more to do, best proceed step by step.

    If you have an external disk, you can also download the two iso's if you don't already have them, one for 1607 in case an in-place upgrade repair install is needed, & one for 1709.
      My ComputerSystem Spec


  6. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
    Thread Starter
       30 Dec 2017 #6

    hi,

    Oh no i'm scared to mess with partitions if i screw up i got nothing left i guess i'll have to give up or find somebody who knows the partition stuff better then i do so HP messed up when i bought that laptop i guess i could exspect the manufacterer to know there job apparently not i never changed anything on that partitions.
    Last edited by rscalover; 30 Dec 2017 at 14:12.
      My ComputerSystem Spec

  7. topgundcp's Avatar
    Posts : 2,438
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       30 Dec 2017 #7

    According to the error, there's a partition with GUID that was not recognized by Windows.
    Open Admin command prompt and type:
    diskpart
    select disk 0
    list partition
    exit

    Also type:
    bcdedit /enum all

    Post both results
      My ComputerSystem Spec


  8. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
    Thread Starter
       30 Dec 2017 #8

    Click image for larger version. 

Name:	diskpart.JPG 
Views:	58 
Size:	54.2 KB 
ID:	170185


    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    {ed535265-6231-11e5-8330-806e6f6e6963}
    {21d4301b-3b7a-11e4-95e7-b57d49463b72}
    {4801c3c8-3adb-11e5-82fd-806e6f6e6963}
    timeout 0

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale nl-NL
    inherit {globalsettings}
    default {current}
    resumeobject {21d43032-3b7a-11e4-95e7-b57d49463b72}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 0

    Firmware Application (101fffff)
    -------------------------------
    identifier {21d4301b-3b7a-11e4-95e7-b57d49463b72}
    description Internal CD/DVD ROM Drive(UEFI)

    Firmware Application (101fffff)
    -------------------------------
    identifier {4801c3c8-3adb-11e5-82fd-806e6f6e6963}
    description USB Drive (UEFI)

    Firmware Application (101fffff)
    -------------------------------
    identifier {ed535265-6231-11e5-8330-806e6f6e6963}
    device partition=\Device\HarddiskVolume2
    description Internal Hard Disk

    Windows Boot Loader
    -------------------
    identifier {21d43025-3b7a-11e4-95e7-b57d49463b72}
    device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{21d43026-3b7a-11e4-95e7-b57d49463b72}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale nl-NL
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{21d43026-3b7a-11e4-95e7-b57d49463b72}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {21d4302a-3b7a-11e4-95e7-b57d49463b72}
    device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d4302b-3b7a-11e4-95e7-b57d49463b72}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale nl-NL
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d4302b-3b7a-11e4-95e7-b57d49463b72}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {21d4302f-3b7a-11e4-95e7-b57d49463b72}
    device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d43030-3b7a-11e4-95e7-b57d49463b72}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale nl-NL
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d43030-3b7a-11e4-95e7-b57d49463b72}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \WINDOWS\system32\winload.efi
    description Windows 10
    locale nl-NL
    inherit {bootloadersettings}
    recoverysequence {21d43034-3b7a-11e4-95e7-b57d49463b72}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \WINDOWS
    resumeobject {21d43032-3b7a-11e4-95e7-b57d49463b72}
    nx OptIn
    bootmenupolicy Legacy

    Windows Boot Loader
    -------------------
    identifier {21d43034-3b7a-11e4-95e7-b57d49463b72}
    device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d43035-3b7a-11e4-95e7-b57d49463b72}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale nl-NL
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{21d43035-3b7a-11e4-95e7-b57d49463b72}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {21d43023-3b7a-11e4-95e7-b57d49463b72}
    device partition=C:
    path \WINDOWS\system32\winresume.efi
    description Windows Resume Application
    locale nl-NL
    inherit {resumeloadersettings}
    recoverysequence {21d43025-3b7a-11e4-95e7-b57d49463b72}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {21d43028-3b7a-11e4-95e7-b57d49463b72}
    device partition=C:
    path \WINDOWS\system32\winresume.efi
    description Windows Resume Application
    locale nl-NL
    inherit {resumeloadersettings}
    recoverysequence {21d4302a-3b7a-11e4-95e7-b57d49463b72}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {21d4302d-3b7a-11e4-95e7-b57d49463b72}
    device partition=C:
    path \WINDOWS\system32\winresume.efi
    description Windows Resume Application
    locale nl-NL
    inherit {resumeloadersettings}
    recoverysequence {21d4302f-3b7a-11e4-95e7-b57d49463b72}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Resume from Hibernate
    ---------------------
    identifier {21d43032-3b7a-11e4-95e7-b57d49463b72}
    device partition=C:
    path \WINDOWS\system32\winresume.efi
    description Windows Resume Application
    locale nl-NL
    inherit {resumeloadersettings}
    recoverysequence {21d43034-3b7a-11e4-95e7-b57d49463b72}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Geheugencontrole
    locale nl-NL
    inherit {globalsettings}
    badmemoryaccess Yes

    EMS Settings
    ------------
    identifier {emssettings}
    bootems No

    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Serial
    debugport 1
    baudrate 115200

    RAM Defects
    -----------
    identifier {badmemory}

    Global Settings
    ---------------
    identifier {globalsettings}
    inherit {dbgsettings}
    {emssettings}
    {badmemory}
    integrityservices Enable

    Boot Loader Settings
    --------------------
    identifier {bootloadersettings}
    inherit {globalsettings}
    {hypervisorsettings}

    Hypervisor Settings
    -------------------
    identifier {hypervisorsettings}
    hypervisordebugtype Serial
    hypervisordebugport 1
    hypervisorbaudrate 115200

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}

    Device options
    --------------
    identifier {21d43026-3b7a-11e4-95e7-b57d49463b72}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume1
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {21d43027-3b7a-11e4-95e7-b57d49463b72}
    description Windows Setup
    ramdisksdidevice partition=C:
    ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options
    --------------
    identifier {21d4302b-3b7a-11e4-95e7-b57d49463b72}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume5
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {21d4302c-3b7a-11e4-95e7-b57d49463b72}
    description Windows Setup
    ramdisksdidevice partition=C:
    ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options
    --------------
    identifier {21d43030-3b7a-11e4-95e7-b57d49463b72}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume5
    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options
    --------------
    identifier {21d43031-3b7a-11e4-95e7-b57d49463b72}
    description Windows Setup
    ramdisksdidevice partition=C:
    ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options
    --------------
    identifier {21d43035-3b7a-11e4-95e7-b57d49463b72}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume5
    ramdisksdipath \Recovery\WindowsRE\boot.sdi
      My ComputerSystem Spec

  9. topgundcp's Avatar
    Posts : 2,438
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       30 Dec 2017 #9

    Looked at the result. I did not see anything related to the GUID error in your post, looks normal to me.
    Your C drive is almost 3/4 full and normally Windows updates will try to shrink it to make room for an extra Recovery partition. If C drive is badly fragmented then it might prevent the creation. Try to defrag C drive and consolidate free space then try Windows Updates again.
      My ComputerSystem Spec


  10. Posts : 22
    Microsoft Windows 10 Pro 1709 (16299.214)
    Thread Starter
       30 Dec 2017 #10

    Hi,

    I have allot of large videos on that drive i no longer need i'll remove them to create space also "cleanmgr" could come in handy if that is the problem.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
So I used Upgrade Assistant tool to upgrade my Windows 10 Anniversary copy to Creators Update. As soon as copying files is done, the computer restarts as usual. But there's something uncommon, my computer did not boot and entered straight to BIOS...
Not cause by virus .. this just started today. I tried a restore point of yesterday .. nothing. I have tried several suggestions from the web but nothing seems to do it? I know it would be better if i could name them but can't remember the exact...
Solved Windows 10 fails to upgrade. in Installation and Upgrade
Have followed instructions & downloaded upgrade only to find every time it gets to 32% it fails & will not go any further, have done this four times outcome always the same can someone help I have 74gb of hard drive free so there should be enough to...
Hi guys, My installation of Windows 10 from Windows 8.1 always fails at the 22% mark. This has happened about 6-7 times. I've tried deleting the items in the download folder, as well as the setupprep.exe in the Windows WS folder. I'm using the...
Hi, I tried updating my Win8.1 to Win10 twice. The first time, it hung at 26% total, 89% copying files. Then it bricked my system completely so I made a clean install of Windows 8.1. There was nothing else installed than Windows & Updates....
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 19:08.
Find Us