Page 1 of 2 12 LastLast
  1.    19 Aug 2015 #1
    Join Date : Oct 2014
    Hartselle
    Posts : 488
    Windows 10 Pro 16299.98

    10525 Upgrade adds new Recovery Partition


    After upgrade to 10525 yesterday, I found that Windows without notification or warning had decided to create a new unwanted Recovery Partition. I have never had one before. I have done probably 10 Insider upgrades since last October and this is first time that Windows has created a separate Recovery Partition. The 451 MB partition was carved out of the Windows 10 partition being upgraded. Does anyone have any idea why this happened on this particular upgrade? More importantly how do I prevent this from happening in the future?

    Click image for larger version. 

Name:	PJNrf5W.jpg 
Views:	16 
Size:	176.3 KB 
ID:	32540
    Last edited by tracit99; 19 Aug 2015 at 10:59.
      My ComputerSystem Spec
  2.    19 Aug 2015 #2
    Join Date : Sep 2014
    Posts : 91
    64-bit 10240 10 Pro

    It did not for me. maybe due to the fact I never had one.
      My ComputerSystem Spec
  3.    19 Aug 2015 #3
    Join Date : Aug 2015
    Posts : 9
    Windows 10

    For me, the upgrade from Win 8.1 to Win 10 10240 RTM added that partition, which was a surprise to me.
    It is 503MB.
    I have also been running Build 10240 on a Virtual Machine that did *not* have that partition, but its path to 10240 was via several Insider previews, not a direct install.


    bv
      My ComputerSystem Spec
  4.    19 Aug 2015 #4
    Join Date : Jun 2015
    Posts : 1,929
    Windows 3.1 to Windows 10

    when you upgrade or install windows 10, Windows 8/8.1/1. likes to create a separate partition to place the WinRE.wim
    this is so as to protect the WinRE.wim form corruption or infection

    WinRE.wim is a bootable recovery environment (it is basically a boot.wim. but for recovery)

    the reason the size of the winRE partition may very is because windows 10 adds the boot critical drivers to the WinRE.wim

    And in some cases the WinRE partition is shared with the System partition.. The system partition being the System Boot partition

    On MBR type disk this sharing is normal = usually 500MB partition, due to partition limitation
    If you only have a 100MB System partition = it is also not uncommon to find the recovery (winRE.wim) hidden on C:

    Windows tries to keep the Boot and recovery options - away from the OS
      My ComputerSystem Spec
  5.    19 Aug 2015 #5
    Join Date : Aug 2015
    Posts : 9
    Windows 10

    @Kyhi
    In my scenario, I had 8.1 on MBR w only a small, 100MB system boot partition (plus C: & D:, of course).
    When I tried to upgrade to 10, it complained that it couldn't use the "system reserved" partition.
    So, using MiniTool partition mgr, I basically slid C: & D: up the drive and increased the system boot part to 400MB, figuring that that would be enough.


    It then *did* allow the upgrade,
    but it *inserted* the new 500MB recovery part between C: & D:, I guess by shrinking C:,
    although I didn't check the exact before/after sizes.


    Anyway, it sounds like you're saying that if I had made the system boot part, say 600MB, it would have, as you say, "shared" the System Boot part as the Recovery part. as well ?


    bv
      My ComputerSystem Spec
  6.    19 Aug 2015 #6
    Join Date : Apr 2014
    Posts : 627
    Windows 10 Pro Insider Preview (14971)

    I have found that if I clean install into an unformatted partition, Win10 will make a Recovery Partition, but if I install it into a prepared NTFS partition, it won't. I've never seen it make a Recovery Partition on an upgrade - including this upgrade to 525.
      My ComputerSystem Spec
  7.    19 Aug 2015 #7
    Join Date : Nov 2013
    Idaho USA
    Posts : 4,826
    OS X, Win 10

    Whatever. . .if you don't think you'll need it then make it go away. . .. . .but remember to do a backup. . .
      My ComputerSystem Spec
  8.    19 Aug 2015 #8
    Join Date : Aug 2015
    Posts : 9
    Windows 10

    I was the normal in-place upgrade to 10240 RTM on the running disk and it created it.
    It's not a problem, except that now I've used all 4 MBR parts.
    But it was interesting to me.
    Of course I could always convert to Logical partition for D: when I need to add another part.

    bv
      My ComputerSystem Spec
  9.    19 Aug 2015 #9
    Join Date : Sep 2014
    Posts : 91
    64-bit 10240 10 Pro

    My Windows 7 did not have a recovery partition, probably why when I upgraded I did not get one. I did notice that when I did Clean Install a 450MB partition was created.
      My ComputerSystem Spec
  10.    19 Aug 2015 #10
    Join Date : Sep 2014
    Posts : 91
    64-bit 10240 10 Pro

    If I did have one I would not remove it.
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Re-Create that 450MB Recovery Partition?
In a fit of over zealous tidying up after installing Win 10 on my lappie, I deleted the 450MB Recovery Partition that the upgrade from Windows 7 created at the end of the main partition. 1) What was actually in that partition and why would I want...
General Support
Build 10525 Stopped at 92% of the upgrade.
After updating fine for a while, the update stopped running. On the black background the title is: Upgrading Windows 92% show inside the blue circle outline At the bottom of the screen is the following information: Configuring settings...
Windows Insider
Making a Recovery Partition?
The thread above reminded me... My laptop has a partition with Windows 7 on it for recovery purposes. It was a long time ago, but I think I created it from an ISO. I can't even remember how it should be used! Is it possible to create the same...
Installation and Upgrade
Solved 250mg recovery partition ?
Hi, Okay this last install of 9926 installed without the 250mg recovery partition that prior builds have produced ? Anyone else seeing this ? I have since removed the build I had enough looking at it.... But found that interesting the recovery...
Installation and Upgrade
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:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums