reagntc Command Shows Wrong Win RE Partition after Windows 10 Upgrade

Page 1 of 2 12 LastLast

  1. Posts : 7,871
    Windows 11 Pro 64 bit
       #1

    reagntc Command Shows Wrong Win RE Partition after Windows 10 Upgrade


    I just upgraded from Windows 8.1 to Windows 10 and my system disk map looks like this:

    Attachment 84400

    The reagentc / info command shows this:
    Attachment 84402

    The Win RE location is partition 5 which dates from 2104 (W8.1):
    Attachment 84403
    But the Windows 10 RE files are on partition 4:
    Attachment 84406

    It seems the wrong partition is selected for the Windows 10 RE files. Why has the Windows 10 installation done this and how do I ensure the correct Windows 10 Win RE partition is selected?
      My Computers


  2. Posts : 18,424
    Windows 11 Pro
       #2

    REAgentC Command-Line Options

    reagentc /setreimage /path F:\Recovery

    You will have to assign a drive letter to the recovery partition and use that drive letter in the command above. That resets the location of the WindowsRE file.
      My Computer


  3. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #3

    If you can't assign a driver letter, The Recovery part might be a hidden partition.

    Command Prompt (Admin)
    diskpart
    sel dis 0
    lis par
    sel par 4
    det par
    det vol

    Post the output from diskpart
      My Computer


  4. Posts : 4,131
    Windows 3.1 to Windows 11
       #4

    You have a hidden partition > so verify partition layout..

    diskpart
    select disk 0
    list partition

    if sure win10 recovery is on disk 0 partition 4 then

    reagentc /disable
    Reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    reagentc /enable

    reagentc /info
      My Computer


  5. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #5

    Kyhi said:
    You have a hidden partition > so verify partition layout.
    Yeah, I forgot about the MSR and asked only for det(ails) on par(tiition) 4

    Thanks for adding what Steve C needs to do after verifying the schema.

    par1: 300MB Recovery
    par2: EFI
    par3: MSR - hidden
    par4: System c:
    par5: 450 MB Recovery
    par6: 450 MB Recovery

    Steve C can probably eliminate the 300MB Recovery (par1) and the last 450 MB Recovery partitions (par6)
    They're only 750 MB in total - so you can leave them with no harm.

    Any thoughts Kyhi?

    Don't take any action Steve - there's not enough information about the partitions yet.
      My Computer


  6. Posts : 4,131
    Windows 3.1 to Windows 11
       #6

    or he can copy winre.wim from partition win10 re to partition 1
    and delete the last 2 partitions and gain the space back into c

    as PC appears to have been upgraded twice to win10 - thus the 2 extra partitions...
      My Computer


  7. Posts : 7,871
    Windows 11 Pro 64 bit
    Thread Starter
       #7

    Thanks to Kyhi & Slartybart for spotting I was counting partitions based on Disk Management and missed the hidden partition. The original installation was Windows 8 Pro then upgraded to Windows 8.1 Pro and to Windows 10 Pro yesterday. The full partition layouts from Diskpart and Partition Wizard are shown below:
    Attachment 84506
    Attachment 84507
    Here are the partition contents of Disk 0 (Diskpart) / Disk 1 (Partition Wizard):

    Partition 1:
    Attachment 84508
    Partition 5:
    Attachment 84512
    Partition 6:
    Attachment 84513
    It looks like Windows 10 is using the right recovery partition - Partition 5 according to reagentc /info.

    Was Partition 1 which now has no Win RE files the original Windows 8 recovery partition?
    The idea of moving Win RE files to the first partition is attractive but I don't seem to have enough space since I only have 162Mb free. How would I do this without trashing my PC?

    An easier fix would be to delete partition 6 (from Windows 8,1?), move Partition 5 to the end of the disk then expand current Partition 4 [Drive C] to use the empty space.
      My Computers


  8. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #8

    Steve C said:
    ...
    An easier fix would be to delete partition 6 (from Windows 8,1?), move Partition 5 to the end of the disk then expand current Partition 4 [Drive C] to use the empty space.
    Seems like a lot of work to reclaim 450 MB of disk space at the end of the drive.

    I would relabel part 1 to Kaspersky Rescue, just to avoid any ambiguity
    Then delete part 6, leaving the 450 MB unallocated

    Who knows what the next Windows drop (Redstone 1 - 29 July 2016) is going to do? It might change the disk schema once again !
      My Computer


  9. Posts : 7,871
    Windows 11 Pro 64 bit
    Thread Starter
       #9

    Good point - I'll decide what to do after 29 July. Wasn't partition 1 created by Windows 8 and Kaspersky Anti-Virus has added more files to that partition?
      My Computers


  10. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #10

    Kyhi said:
    or he can copy winre.wim from partition win10 re to partition 1
    and delete the last 2 partitions and gain the space back into c

    as PC appears to have been upgraded twice to win10 - thus the 2 extra partitions...
    @Kyhi
    This won't work since partition 1 is 300MB and the WinRe.wim in partition 6 alone is 335.45MB.

    @steve C
    FYI, Each time you upgrade or perform in place repair, another 450MB Recovery will be created. The WinRE.wim for Win8.1 is removed from the 300MB partition and replaced by a new WinRE.wim for Win10 in the new 450MB partition.

    For Win 8.1 the GPT partition scheme is: 300MB Recovery, 100MB EFI System, 128MB MSR and C drive.
    For Win10, the GPT partition scheme is: 450MB Recovery, 100MB EFI System, 16MB MSR and C drive.

    If you wish, you can re-align the partition scheme as shown in this post:
    GPT disk conversion for both data drives and C drive - Windows 10 Forums
      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 11:08.
Find Us




Windows 10 Forums