Build 14393 vs. 15063 - different format???

Discussion in 'Windows 10' started by MonarchX, Jul 20, 2017.

  1. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,732
    313
    60
    If I make an ISO with Win10 Pro 14393, make a bootable USB, and use it to create and format the necessary partitions for the installation of Win10 Pro 14393, then I cannot use a similar ISO with 15063 to format the extra partitions once build 14393 was installed. I can only format the main OS partition. In other words I can format all 4 partitions - the Recovery 450MB one, the 100MB one, the 16MB one, and the main one (30.4GB in my case) with 14393 ISO USB, install Win10 14393, BUT if I then load 15063 Win10 USB and attempt to just format those extra partitions - it will not let me format the already created partitions, at least not the 450MB one and the 100MB one. I have to delete and re-create partitions every time I switch builds! Why is that? In each case I used RUFUS GPT UEFI FAT32.

    Then today I find out that I also cannot restore Acronis True Image (full) backup of Windows 14393 onto partitions created with 15063! I had to delete 15063 partitions, re-create them with 14393, and only then Acronis True Image backup of Windows 14393 could be restored without problems! I only use Acronis True Image bootable USB - never install it as software. In each and every single case partition sizes and formats are identical.
     
  2. #2 Deleted member 578156, Jul 23, 2017
    Last edited by a moderator: Jul 23, 2017
    Wow that is weird, you`d think being formatted for GPT UEFI FAT32 for windows 10 14393 that the same should also work for 15063 without reformatting, Unless there is special instructions in the bootloader for 15063 i`m not sure. I don`t think it has anything to do with Rufus though. Is there anyone out there that can help this gentlemen with this problem? I`ll do some digging, if i find anything i`ll post it!, Say bud do you have the Latest version on Rufus? as it just might be that although i highly doubt it.
     
  3. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,732
    313
    60
    Yeah, latest everything. Could this be because I integrate cumulative updates (+ResetBase) not only into Install.wim, but also into both Boot.wim indexes (WinSetup and WinPE) and WinRE.wim? AFAIK MS does not do that... I think MS still uses WinPE from Windows 8 in Windows 10 Boot.wim.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,672
    450
    Every MSFT refresh iso has the updates pre-integrated into boot.wim, winre.wim and install.wim.
     
  5. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,732
    313
    60
    Yeah, but I just like to keep them updated, so I integrate CU's into them.
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,672
    450
    My reply was about the orange marked txt, you presumed MSFT doesn't do that, i said they do...