Failed to update to windows 11 help?

Anonymous
2024-07-19T07:56:57+00:00

Hello, I've recently tried updating to windows 11 using 'Windows11InstallationAssistant.exe' but once my pc was restarted at the 30min mark and booted back up, I was still running windows 10 and all it added was a SYSTEM (E:) drive that I can't access. Did I do something wrong or what happened? I did run the windows pc health check tool to check if my pc can run windows 11 and was confirmed I could.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

52 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-21T09:04:42+00:00

    STEP 5 A) Overview-- D: Drive

    Image

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-07-21T08:52:43+00:00

    STEP 2:

    Disk 0 : HDD. It has 2 partition(s). Model: WDC WD10EZEX-08WN4A0    
    
    Disk 1 : SSD. It has 4 partition(s). Model: ADATA SU630    
    
    The script has found the above 2 storage device(s) in total. 
    

    =======================================================================

    Microsoft DiskPart version 10.0.19041.3636

    Copyright (C) Microsoft Corporation.

    On computer: DESKTOP-6FFOV2U

    Disk ### Status Size Free Dyn Gpt


    Disk 0 Online 931 GB 1024 KB *

    Disk 1 Online 223 GB 1024 KB *

    Volume ### Ltr Label Fs Type Size Status Info


    Volume 0 D New Volume NTFS Partition 931 GB Healthy

    Volume 1 C Windows NTFS Partition 222 GB Healthy System

    Volume 2 SYSTEM FAT32 Partition 100 MB Healthy Hidden

    Volume 3 Recovery NTFS Partition 500 MB Healthy Hidden

    Disk 0 is now the selected disk.

    WDC WD10EZEX-08WN4A0

    Disk ID: {0972650A-DD3F-4812-8588-B7AEF5CC98A4}

    Type : SATA

    Status : Online

    Path : 0

    Target : 0

    LUN ID : 0

    Location Path : PCIROOT(0)#PCI(1700)#ATA(C00T00L00)

    Current Read-only State : No

    Read-only : No

    Boot Disk : No

    Pagefile Disk : No

    Hibernation File Disk : No

    Crashdump Disk : No

    Clustered Disk : No

    Volume ### Ltr Label Fs Type Size Status Info


    Volume 0 D New Volume NTFS Partition 931 GB Healthy

    Partition ### Type Size Offset


    Partition 1 Reserved 15 MB 17 KB

    Partition 2 Primary 931 GB 16 MB

    Partition 1 is now the selected partition.

    Partition 1

    Type : e3c9e316-0b5c-4db8-817d-f92df00215ae

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 17408

    There is no volume associated with this partition.

    Partition 2 is now the selected partition.

    Partition 2

    Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    Hidden : No

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 16777216

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 0 D New Volume NTFS Partition 931 GB Healthy

    Disk 1 is now the selected disk.

    ADATA SU630

    Disk ID: {0A9CFAE5-FD6B-4BA2-A4DF-4B9B6576EF6B}

    Type : SATA

    Status : Online

    Path : 1

    Target : 0

    LUN ID : 0

    Location Path : PCIROOT(0)#PCI(1700)#ATA(C01T00L00)

    Current Read-only State : No

    Read-only : No

    Boot Disk : Yes

    Pagefile Disk : Yes

    Hibernation File Disk : No

    Crashdump Disk : Yes

    Clustered Disk : No

    Volume ### Ltr Label Fs Type Size Status Info


    Volume 1 C Windows NTFS Partition 222 GB Healthy System

    Volume 2 SYSTEM FAT32 Partition 100 MB Healthy Hidden

    Volume 3 Recovery NTFS Partition 500 MB Healthy Hidden

    Partition ### Type Size Offset


    Partition 1 System 100 MB 1024 KB

    Partition 2 Reserved 16 MB 101 MB

    Partition 3 Recovery 500 MB 117 MB

    Partition 4 Primary 222 GB 617 MB

    Partition 1 is now the selected partition.

    Partition 1

    Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b

    Hidden : Yes

    Required: No

    Attrib : 0X8000000000000000

    Offset in Bytes: 1048576

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 2 SYSTEM FAT32 Partition 100 MB Healthy Hidden

    Partition 2 is now the selected partition.

    Partition 2

    Type : e3c9e316-0b5c-4db8-817d-f92df00215ae

    Hidden : Yes

    Required: No

    Attrib : 0X8000000000000000

    Offset in Bytes: 105906176

    There is no volume associated with this partition.

    Partition 3 is now the selected partition.

    Partition 3

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: Yes

    Attrib : 0X8000000000000001

    Offset in Bytes: 122683392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 3 Recovery NTFS Partition 500 MB Healthy Hidden

    Partition 4 is now the selected partition.

    Partition 4

    Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    Hidden : No

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 646971392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 1 C Windows NTFS Partition 222 GB Healthy System

    ===============================================================================

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information:

    Windows RE status:         Disabled 
    
    Windows RE location:        
    
    Boot Configuration Data (BCD) identifier: d9f8db7e-cd56-11ea-ba54-c14a2ddc2630 
    
    Recovery image location:    
    
    Recovery image index:      0 
    
    Custom image location:      
    
    Custom image index:        0 
    

    REAGENTC.EXE: Operation Successful.

    ===============================================================================

    Firmware Boot Manager


    identifier {fwbootmgr}

    displayorder {778d04f5-d218-11ea-aaf3-806e6f6e6963}

                        {bootmgr} 
    
                        {5ebcea28-3c06-11ea-aa9f-806e6f6e6963} 
    

    timeout 1

    Windows Boot Manager


    identifier {bootmgr}

    device partition=\Device\HarddiskVolume3

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    locale en-US

    inherit {globalsettings}

    default {default}

    resumeobject {d9f8db7c-cd56-11ea-ba54-c14a2ddc2630}

    displayorder {default}

    bootsequence {default}

    toolsdisplayorder {memdiag}

    timeout 30

    Firmware Application (101fffff)


    identifier {5ebcea28-3c06-11ea-aa9f-806e6f6e6963}

    description Hard Drive

    Firmware Application (101fffff)


    identifier {778d04f5-d218-11ea-aaf3-806e6f6e6963}

    device partition=C:

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    Windows Boot Loader


    identifier {00a9fb44-52ed-11ea-b794-a2b3b2eb1f90}

    device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{00a9fb45-52ed-11ea-b794-a2b3b2eb1f90}

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    locale en-US

    inherit {bootloadersettings}

    displaymessage Recovery

    osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{00a9fb45-52ed-11ea-b794-a2b3b2eb1f90}

    systemroot \windows

    nx OptIn

    bootmenupolicy Standard

    winpe Yes

    Windows Boot Loader


    identifier {default}

    device partition=C:

    path \WINDOWS\system32\winload.efi

    description Windows 10

    locale en-US

    inherit {bootloadersettings}

    recoverysequence {d9f8db7e-cd56-11ea-ba54-c14a2ddc2630}

    displaymessageoverride Recovery

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \WINDOWS

    resumeobject {d9f8db7c-cd56-11ea-ba54-c14a2ddc2630}

    nx OptOut

    bootmenupolicy Standard

    Windows Boot Loader


    identifier {d9f8db7e-cd56-11ea-ba54-c14a2ddc2630}

    device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{d9f8db7f-cd56-11ea-ba54-c14a2ddc2630}

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    locale en-US

    inherit {bootloadersettings}

    displaymessage Recovery

    osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{d9f8db7f-cd56-11ea-ba54-c14a2ddc2630}

    systemroot \windows

    nx OptIn

    bootmenupolicy Standard

    winpe Yes

    Resume from Hibernate


    identifier {00a9fb42-52ed-11ea-b794-a2b3b2eb1f90}

    device partition=C:

    path \WINDOWS\system32\winresume.efi

    description Windows Resume Application

    locale en-US

    inherit {resumeloadersettings}

    recoverysequence {00a9fb44-52ed-11ea-b794-a2b3b2eb1f90}

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    filedevice partition=C:

    filepath \hiberfil.sys

    bootmenupolicy Standard

    debugoptionenabled No

    Resume from Hibernate


    identifier {d9f8db7c-cd56-11ea-ba54-c14a2ddc2630}

    device partition=C:

    path \WINDOWS\system32\winresume.efi

    description Windows Resume Application

    locale en-US

    inherit {resumeloadersettings}

    recoverysequence {d9f8db7e-cd56-11ea-ba54-c14a2ddc2630}

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    filedevice partition=C:

    filepath \hiberfil.sys

    bootmenupolicy Standard

    debugoptionenabled No

    Windows Memory Tester


    identifier {memdiag}

    device partition=\Device\HarddiskVolume3

    path \EFI\Microsoft\Boot\memtest.efi

    description Windows Memory Diagnostic

    locale en-US

    inherit {globalsettings}

    badmemoryaccess Yes

    EMS Settings


    identifier {emssettings}

    bootems No

    Debugger Settings


    identifier {dbgsettings}

    debugtype Local

    RAM Defects


    identifier {badmemory}

    Global Settings


    identifier {globalsettings}

    inherit {dbgsettings}

                        {emssettings} 
    
                        {badmemory} 
    

    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 {00a9fb45-52ed-11ea-b794-a2b3b2eb1f90}

    description Windows Recovery

    ramdisksdidevice partition=\Device\HarddiskVolume5

    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options


    identifier {00a9fb46-52ed-11ea-b794-a2b3b2eb1f90}

    description Windows Setup

    ramdisksdidevice partition=C:

    ramdisksdipath $WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options


    identifier {d9f8db7f-cd56-11ea-ba54-c14a2ddc2630}

    description Windows Recovery

    ramdisksdidevice partition=\Device\HarddiskVolume5

    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-07-21T08:49:54+00:00

    STEP 1:

    Tuneup_log 2024-07-21 at 02-36-26.zip

    I will be uploading each piece as I complete each step

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-21T08:38:29+00:00

    Should I do this before or after the steps 'questions_' asked me to do?

    Was this answer helpful?

    0 comments No comments
  5. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2024-07-21T08:22:36+00:00

    Bryan,

    Please create a Restore Point.

    Create a USB setup disk. You may not need it. But it's good to keep it ready.

    • Download fixlist.txt [https://1drv.ms/t/s!AjVYLGw0OBWU1HKt1T-cv4xqto3...]

    • Save Fixlist.txt in the same folder where FRST64English.exe is.

    • Close all program windows.

    • Launch the Farbar Scanner tool and click "Fix".

    • Reboot Windows when prompted.

    • Upload the output log file (FixLog.txt) to your OneDrive.

    The above fixlist removes some old drivers (RGB drivers) that may be interrupting the setup.

    Please retry the Windows 11 upgrade. If the setup fails, please share the latest setup logs.

    Was this answer helpful?

    0 comments No comments