Using DISKPART & DISM to Clean Install.

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
    Thread Starter
       #41

    Matthew Wai said:
    Do you mean something like the following?
    Yes.

    I do NOT have a Recovery Partition which is the way that I want it, as per previous posts.

    Do I need to change the Boot Mode Selection that is currently set to UEFI and Legacy to UEFI Only on my GIGABYTE - UEFI DualBIOS please?

    Fast Boot is Disabled.
    Secure Boot State is Disabled.
      My Computer


  2. Posts : 7,606
    Windows 10 Home 20H2
       #42

    Do you want to install Windows in UEFI mode or Legacy mode?
      My Computer


  3. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
    Thread Starter
       #43

    Matthew Wai said:
    Do you want to install Windows in UEFI mode or Legacy mode?
    Since I have converted the Disk to GPT in the Script, UEFI Mode.
      My Computer


  4. Posts : 7,606
    Windows 10 Home 20H2
       #44

    Did you select a device with the "UEFI" prefix on the boot menu?



    Paul Black said:
    Do I need to change the Boot Mode Selection that is currently set to UEFI and Legacy to UEFI Only on my GIGABYTE - UEFI DualBIOS please?
    I have never changed it on my GIGABYTE. I have installed Windows in UEFI mode.

    Using DISKPART & DISM to Clean Install.-bios-features-4.jpg
    Paul Black said:
    Did you read the whole thread?
    No, I did not.
      My Computer


  5. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
    Thread Starter
       #45

    I am just creating another Bootable USB as the one I am using is quite old.
      My Computer


  6. Posts : 7,606
    Windows 10 Home 20H2
       #46

    If I recall correctly, you use Ventoy.
      My Computer


  7. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
    Thread Starter
       #47

    Matthew Wai said:
    If I recall correctly, you use Ventoy.
    You are correct, BUT, on this occasion I am just using a USB created using Rufus because it is NOT a straight forward install as I am using Scripts, which I just add to the Root. As you can see from above, the Scripts worked great!

    It is about half way through.
      My Computer


  8. Posts : 7,606
    Windows 10 Home 20H2
       #48

    The added scripts could be the culprit.
      My Computer


  9. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
    Thread Starter
       #49

    Matthew Wai said:
    The added scripts could be the culprit.
    It appears that the Bootable USB was at fault. I recreated it . . .

    Using DISKPART & DISM to Clean Install.-rufus_uefi-gpt.jpg

    This is the output results of the Script . . .

    Code:
    
    Microsoft DiskPart version 10.0.18362.1
    
    Copyright (C) Microsoft Corporation.
    On computer: MINWINPC
    
    Disk 0 is now the selected disk.
    
    DiskPart succeeded in cleaning the disk.
    
    DiskPart successfully converted the selected disk to GPT format.
    
    DiskPart succeeded in creating the specified partition.
    
      100 percent completed
    
    DiskPart successfully formatted the volume.
    
    DiskPart successfully assigned the drive letter or mount point.
    
    DiskPart succeeded in creating the specified partition.
    
    DiskPart succeeded in creating the specified partition.
    
      100 percent completed
    
    DiskPart successfully formatted the volume.
    
    DiskPart successfully assigned the drive letter or mount point.
    
    DiskPart succeeded in creating the specified partition.
    
      100 percent completed
    
    DiskPart successfully formatted the volume.
    
    DiskPart successfully assigned the drive letter or mount point.
    
    DiskPart succeeded in creating the specified partition.
    
      100 percent completed
    
    DiskPart successfully formatted the volume.
    
    DiskPart successfully assigned the drive letter or mount point.
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     H                       DVD-ROM         0 B  No Media
      Volume 1     W   W10          NTFS   Partition     30 GB  Healthy
      Volume 2     D   Data         NTFS   Partition     50 GB  Healthy
    * Volume 3     I   Image        NTFS   Partition     20 GB  Healthy
      Volume 4     S   SYSTEM       FAT32  Partition    100 MB  Healthy    Hidden
      Volume 5     F   CCCOMA_X64F  NTFS   Removable   7644 MB  Healthy
      Volume 6     G   UEFI_NTFS    FAT    Removable   1024 KB  Healthy
    
    Leaving DiskPart...
    
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1
    
    Applying image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Boot files successfully created.
    
    >Processing Complete. Press ANY key to EXIT . . .
    
    
    

    I then selected the Language/Keyboard, accepted the EULA, and it went straight to, and Highlighted the Win 10 Partition, I clicked Next, and it is NOW installing.

    So it turns out that it was a Faulty USB.



    I just thought that I would post [ Document ] this in case anybody is following this thread and wants to Apply it to their Computer.

    I Assigned the USB in Diskpart as Z:\.

    There were NO BIOS changes needed, see previous posts for details.



    This is the PB_Desktop_Disk_Config.txt file that I used . . .

    Code:
    
    select disk 0
    clean
    convert gpt
    create partition efi size=100
    format fs=fat32 quick label="System"
    assign letter=S
    create partition msr size=16
    create partition primary size=30720
    format fs=ntfs quick label="W10"
    assign letter=W
    create partition primary size=51200
    format fs=ntfs quick label="Data"
    assign letter=D
    create partition primary size=20480
    format fs=ntfs quick label="Image"
    assign letter=I
    list volume
    exit

    This is the PB_Desktop_Disk_Config.bat file that I used . . .

    Code:
    
    @echo off
    diskpart /s %~d0\PB_Desktop_Disk_Config.txt
    rem timeout /t 20
    set "Index_Number=6"
    dism /Apply-Image /ImageFile:%~d0\Sources\install.wim /index:"%Index_Number%" /ApplyDir:W:\ /Compact /EA
    W:\Windows\System32\bcdboot W:\Windows /s S:
    echo. & echo ^>Processing Complete. Press ANY key to EXIT . . . & pause >nul

    These are the results . . .

    Using DISKPART & DISM to Clean Install.-clean_install_3.png





    Just one small point that I could NOT work out why it happened.

    Although I used I: for the Image Partition [ Where I will create a System Image on completion of the installation ], which shows in the output results of the Script above, it showed as E: AFTER a Restart. I had to change the Drive Letter in Disk Management!

    Any ideas why please?

    I am going to run through the WHOLE process again tomorrow if anyone has got any ideas.
      My Computer


  10. Posts : 7,606
    Windows 10 Home 20H2
       #50

    Paul Black said:
    Any ideas why please?
    I am now running Windows PE. I just ran the following command:

    diskpart /s F:\PB_Desktop_Disk_Config.txt

    The above .txt file contains the following commands:
    Code:
    select disk 3
    clean
    convert gpt
    create partition primary size=1024
    format fs=ntfs quick label="Image"
    assign letter=I
    list volume
    exit

    The following is the output:
    Code:
    Microsoft Windows [Version 10.0.18362.30]
    (c) 2019 Microsoft Corporation. All rights reserved.
    
    X:\windows\SYSTEM32>diskpart /s F:\PB_Desktop_Disk_Config.txt
    
    Microsoft DiskPart version 10.0.18362.1
    
    Copyright (C) Microsoft Corporation.
    On computer: My_PC
    
    Disk 3 is now the selected disk.
    
    DiskPart succeeded in cleaning the disk.
    
    DiskPart successfully converted the selected disk to GPT format.
    
    DiskPart succeeded in creating the specified partition.
    
      100 percent completed
    
    DiskPart successfully formatted the volume.
    
    DiskPart successfully assigned the drive letter or mount point.
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     K                       DVD-ROM         0 B  No Media
      Volume 1     L   BOOTPE       UDF    DVD-ROM      598 MB  Healthy
      Volume 2     C   Windows 10   NTFS   Partition     80 GB  Healthy
      Volume 3         Recovery     NTFS   Partition    499 MB  Healthy
      Volume 4     D   Data         NTFS   Partition    384 GB  Healthy
      Volume 5                      FAT32  Partition    100 MB  Healthy    Hidden
      Volume 6     E   Ventoy       exFAT  Removable     60 GB  Healthy
      Volume 7     U   VTOYEFI      FAT    Removable     32 MB  Healthy
      Volume 8     F   DEVICE       FAT32  Removable   7387 MB  Healthy
    * Volume 9     I   Image        NTFS   Removable   1024 MB  Healthy
      Volume 10    H   EXTRA        FAT32  Removable     20 GB  Healthy
      Volume 11    J   Windows ISO  NTFS   Removable      8 GB  Healthy
    
    Leaving DiskPart...
    
    X:\windows\SYSTEM32>

    I am going to restart my PC and see whether the drive letter "I" will be changed.
    =====================================================

    I have just restarted my PC.
    Code:
    C:\Windows\system32>DiskPart
    
    Microsoft DiskPart version 10.0.19041.610
    
    Copyright (C) Microsoft Corporation.
    On computer: DESKTOP
    
    DISKPART> List Volume
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     Z                       DVD-ROM         0 B  No Media
      Volume 1     C   Windows 10   NTFS   Partition     80 GB  Healthy    Boot
      Volume 2     D   Data         NTFS   Partition    384 GB  Healthy
      Volume 3                      FAT32  Partition    100 MB  Healthy    System
      Volume 4         Recovery     NTFS   Partition    499 MB  Healthy    Hidden
      Volume 5     X   Ventoy       exFAT  Removable     60 GB  Healthy
      Volume 6         VTOYEFI      FAT    Removable     32 MB  Healthy
      Volume 7     F   EXTRA        FAT32  Removable     20 GB  Healthy
      Volume 8     H   Windows ISO  NTFS   Removable      8 GB  Healthy
      Volume 9     E   DEVICE       FAT32  Removable   7387 MB  Healthy
      Volume 10    G   Image        NTFS   Removable   1024 MB  Healthy
    
    DISKPART>

    It goes to show that an installed version of Windows 10 either does not know or will ignore the drive letter assigned by Windows PE.
      My Computer


 

  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 10:31.
Find Us




Windows 10 Forums