Windows 7 and the System Reserved Partition

Archive
1

If you install Win7 to unallocated space or let Win7 create the install partition, you will get a 100 MB SRP in addition to the Win7 partition. The SRP contains the boot files and is the Active partition.

 

When we have restored Ghost OS images in the past we have chosen, "Set drive active for booting". Now we must remember to NOT choose this option if there is a SRP. If Win7 becomes the Active partition, it will not boot.

 

The SRP takes up one of the 4 partition slots in the MBR and may limit future primary partition creation. I can see it causing issues with image restores, especially to new HDs. The SRP can be removed.

2

If you install Win7 to unallocated space or let Win7 create the install partition, you will get a 100 MB SRP in addition to the Win7 partition. The SRP contains the boot files and is the Active partition.

 

When we have restored Ghost OS images in the past we have chosen, "Set drive active for booting". Now we must remember to NOT choose this option if there is a SRP. If Win7 becomes the Active partition, it will not boot.

 

The SRP takes up one of the 4 partition slots in the MBR and may limit future primary partition creation. I can see it causing issues with image restores, especially to new HDs. The SRP can be removed.

3

RKutash,

 

I expect other partitioning tools can be used but I've only tested with BING (BootIt NG).

 

1. Use a VistaPE boot CD to copy, not move, the contents of the SRP to the Win7 partition. A BartPE CD can be used instead.
From a BING CD, delete the SRP. In View MBR, set the Win7 partition active. Win7 then boots normally.

2. Delete the SRP from a BING CD (it can't be deleted from Windows). In View MBR, set the Win7 partition active. When you try to boot you will see a "BootMGR is missing" message.
Do two repairs from the Win7 DVD. It is only on the second repair that you will get to a large menu where you can choose "Startup Repair". Win7 then boots normally.

 

Very few of us will want BitLocker so we won't miss it. It isn't available in Win7 Pro and below anyway. F8 still works. 

 

To answer Q3, yes. And they should be restored together. I don't know whether the SRP changes but play safe and assume it can.

 

 

4

Brian -- From what I've read from Microsoft on this the SRP also contains the Recovery Environment? So it isn't just Bitlocker and boot files?

 

If it were only BitLocker I was going to ask whether Home Premium also produced it since that version is likely to be the most used -- whereas a lot of the stuff about getting rid of it that appeared during the summer was from using RC versions all of which were the Ultimate version.

5

huwyngr,

 

My 100 MB partition contained 28 MB of data. Two folders, Boot and System Volume Information. Two files, bootmgr and bootsect.bak.

 

Could I quote from Dan Goodell,

 

"To the best of my knowledge, the System Reserved partition has only two purposes: to allow BitLocker to be used on the Windows partition, and to provide a "safer place" for the Recovery Environment files.  (That's where you get to if you press F8 at boot time and choose "Repair my computer".)

In order to encrypt the Windows partition with BitLocker, you understandably have to have unencrypted access to some place from which you can load the BitLocker driver/program.  IOW, you can't encrypt the entire hard disk ... hence, the minimalist System partition.  In a BitLocker'd system you would begin booting from the unencrypted System partition, it would load the encryption driver, and you'd then have access to the encrypted Boot partition.

The rub is that BitLocker is only available in the Ultimate and Enterprise versions of Windows 7.  So for 99% of us, BitLocker isn't an option--and thus isn't a legitimate excuse to saddle us with a System Reserved partition.

As for the Recovery Environment argument, note that you'll still have a RE with or without a System Reserved partition.  The RE files are put on the System partition, so if you do not have a separate System Reserved partition you can still press F8 and boot into the RE, be the RE files will end up coming from the same partition as Windows.

It's possible the RE might be slightly less vulnerable to corruption or viruses if it's on a different partition--especially when that partition has its drive letter removed (as is the case during a normal Windows 7 bootup).  But I doubt it's really much of an advantage because it's a lot more difficult for a virus to infect the RE than it used to be.  The RE is no longer a bunch of files sitting on your hard drive, it's actually a partition image (another .wim file).  In essence, when you boot the RE I believe you're booting into a virtual drive that is "restored" on demand from the .wim image.  I think it would be pretty difficult to infect the operating system contained in that image.

And of course, for frequenters of this forum the RE is even less useful because we make backup images of our OS ... who needs a RE when we can just restore our OS from a backup image?

So, the advantages of having a System Reserved partition are, IMHO, minor or insignificant, while the disadvantages are:

  • it takes up a slot in the partition table,
  • to backup your OS you have to capture two partitions instead of one, and
  • if you restore to a different DiskID or different partition layout it becomes a lot harder to control the drive letter of the Windows partition (because the System partition may want to become "C")."



 

6

While I was quoting a Microsoft support engineer .... <g>

 

<< The RE files are put on the System partition, so if you do not have a separate System Reserved partition you can still press F8 and boot into the RE, be the RE files will end up coming from the same partition as Windows. >>

 

There was talk of deleting the SRP and of moving the boot files. If one did those then the RE would not be directly available as I understand it although would be if you use the Recovery via the installation media disk.

 

I don't want to argue about it but I'm against messing with Windows although the situation with imaging is important and should be dealt with by the imaging software. Does GHOST detect Windows 7 and how it is installed and warn about the situation if necessary?

7
huwyngr wrote:

There was talk of deleting the SRP and of moving the boot files. If one did those then the RE would not be directly available as I understand it although would be if you use the Recovery via the installation media disk.

 

huwyngr,

 

I knew you were going to ask so I just installed Win7 to unallocated space so that I'd have a SRP. I needed to jog my memory too about the F8 option.  I removed the SRP using the second method from Message #3. Win7 boots and I can guarantee that using F8 still works.

 

I didn't make it clear in my first post that if you create a primary partition (to be used for the Win7 install) prior to booting from the Win7 DVD, you don't get a SRP.  Here is an interesting video on installing Win7 to its own primary partition. It's directed at BING users so some of the concepts will appear strange. Using a mouse is much easier than using a keyboard in BING but the keyboard was used as a demo.

 

http://www.terabyteunlimited.com/videos/bing/win7.wmv

 

That's how I installed Win7 on my main computer and Ghost works fine.

8

Since all of my WIN 7's are multibooted with XP I don't have the SRP either ....

 

And I've always created my partitions first .... except for one time when I  wanted to see how well WIN 7 could shrink an existing XP partiton and do the creation and installation but I don't remember whether that one created the extra partition or not.

 

Most of the controversy about simple deleting arose back in RC days with some MS support staff saying just delete and some saying no you can't ...

9

 

      I was wondering what complications might arise if one decides not to remove the SRP, and just backup up both partitions (SRP and Windows 7) using Ghost.  If they need to recover the Ghost disk images onto a brand new, unformatted hard drive (i.e., in the event of hard drive failure), the new hard drive would presumably be unformatted and unpartitioned when purchased, and may also be a different size as the original drive. 

 

     Are there any extra steps that would need to be taken prior to attempting to recover the images with the recovery environment as a result of the SRP, i.e., formatting and partitioning the new hard drive to match the size and location of the 2 partitions on the old hard drive, or something like that?  Or will Ghost automatically recreate the partition structure on the new drive when it restores the images?

 

Thanks again for all the great information!!

10

RKutash,

 

I haven't done this but I'd expect no problems if done correctly. That is, restore both partitions with the SRP being marked Active. If they are restored to a different LBA you may need to do a Startup Repair but that would also apply to a Win7 system without a SRP.

 

In summary, leave the new HD unpartitioned, restore the SRP and choose Set Active. Then restore the Win7 image. A big improvement in Ghost 15 is you can resize the restored partition, larger or smaller. This wasn't present in previous Ghosts. If you restore to a partition you don't have the resize option but you can delete the partition from the Ghost CD and then Resize is an option.

11

I couldn't resist the temptation. The SRP and Win7 partitions were imaged and then restored to different LBA's (from the original) on another HD. Win7 booted on the first attempt.

 

Interestingly, Ghost knew that the SRP was the active partition. I used the Edit button to give more control over the restore process but Ghost guessed the options quite well.

12
Brian_K wrote:

I couldn't resist the temptation. The SRP and Win7 partitions were imaged and then restored to different LBA's (from the original) on another HD. Win7 booted on the first attempt.

 

Interestingly, Ghost knew that the SRP was the active partition. I used the Edit button to give more control over the restore process but Ghost guessed the options quite well.

 

Brian, you are the best when it comes to this sort of thing! :smileyvery-happy:

 

Allen

13
Brian_K wrote:

I couldn't resist the temptation. The SRP and Win7 partitions were imaged and then restored to different LBA's (from the original) on another HD. Win7 booted on the first attempt.

 

Interestingly, Ghost knew that the SRP was the active partition. I used the Edit button to give more control over the restore process but Ghost guessed the options quite well.

Don't you just love it when a plan comes together? :smileywink:

14
Brubaker wrote:
Brian_K wrote:

I couldn't resist the temptation. The SRP and Win7 partitions were imaged and then restored to different LBA's (from the original) on another HD. Win7 booted on the first attempt.

 

Interestingly, Ghost knew that the SRP was the active partition. I used the Edit button to give more control over the restore process but Ghost guessed the options quite well.

Don't you just love it when a plan comes together? :smileywink:

 

Yes, don't we though? :smileywink:

 

Allen

15

The recovery environment for restores confused me at first. Ghost makes some "educated guesses" about what should be done. You can over ride this.

 

I chose View recovery points by: Filename

Browsed to the recovery point

Next

On the Drives to Recover window you should click Edit if you want to make Option changes

You then see the Edit Target Drive and Options window

Here you can choose where to restore the recovery point and...

  Delete Drive

  Resize Drive after recovery

  Partition type

  Check for file system errors

  Set drive active

  Restore original disk signature

  Restore MBR

 

On the next window there is an option to Verify before recovery. I think this should always be selected. If the recovery point is "corrupted" and fails Verify, no harm is done. But if you don't Verify and the recovery point is "corrupted", the target partition will be deleted and the image won't be restored. If you are restoring to the same HD you will no longer have an OS.

  

16

I know there is a small group loyal to Ghost 2003. Yes, you can do this with Ghost 2003. Win7 didn’t boot on the first attempt. There was a Windows Boot Manager error. A single repair from the Win7 DVD fixed the error and Win7 booted.

17

I just wanted to add to this post for everyone as requards to the Extra partition, and also the other main reason for it

for those of you that dont know wbaout hard drives and fragmentation ect.

 

the more data that is on your drive, the more the drive becomes fragmented. this slows your pc down dramitically

the windows defrag is still uselss at this.

 

if you all notice from the adverts microsoft claim its new windows 7 loads faster than previous versions.

yes , and how ?, becasue by creating the extra 200mb partition, you only have boot files, recovery files NOTHING MORE

 

so when you turn on your pc, that boot partion is so small no fragmentation, windows will load faster, also its about security

 

many of you want to remove this partition WHY, its 200mb, ghost works with it so keep it

 

by placing all your boot files on the same partition as the main OS, gives it more chance of

1 getting corrupted due to maculous software, or a virus, most hackers and people that make virus, now attack your boot files

2 your Os becomes more and more full of data, the partition becomes fragmented so much it takes forever to laod

3 if you look at what is stating up when your pc runs, you should see the main system32 files not listed. as this is being taken over from the new partition.

 

over all i would say keep the partition, if u get the chance just see how non fragmented it gets , see how long your pc takes on average compared to having the hidden partition, excluding all the addons u have on startup !!!

 

hope this is of some help to all thos who are not so clued up

18

Dell has an interesting partition layout in their Win7 computers. Dell has put a Recovery Partition on most computers to allow you to restore to the factory setup. But this Recovery Partition contains the boot files. It is the Active, System partition. Dell don't have a System Reserved Partition.

 

Many tech capable folks make it a practice of deleting the Dell Recovery Partition as they run their own image backups. If they delete the Recovery Partition without realizing it contains the boot files there will be panic.

 

Having boot files in a non OS partition just makes backup/restore a little less certain and more difficult for those who are new to imaging.

19
Brian_K wrote:

I couldn't resist the temptation. The SRP and Win7 partitions were imaged and then restored to different LBA's (from the original) on another HD. Win7 booted on the first attempt.

 

Interestingly, Ghost knew that the SRP was the active partition. I used the Edit button to give more control over the restore process but Ghost guessed the options quite well.

 

I had a problem restoring a ghost 15 image to a raid 0 setup. I have 8 SSD drives setup in raid 0 on the LSI 9260-8i raid card. One of the drives died so I eliminated the one drive and setup the raid 0 on the 7 drives instead of the 8. When I went to restore the image I restored to an unallocated raid setup. The image I was restoring consisted of the 100mb partition and a remaining partition. I was able to install the 100mb partition no problem but when I went to install the second partition from the ghost image I get an error saying there isn't enough disk space on the destination drive. There is like 830gb of free space on the 2nd partition and the data being restored is only around 120gb. It seems like ghost is looking at the first partition which is 100mb and stops me from installing because it thinks there is not enough disk space available. I am restoring from within windows on another raid setup running windows 7. That raid setup is connected to the MB Intel ports. What am I doing wrong here?
20

Could you try doing the full restore, both SRP and Win7, from the Ghost 15 CD recovery environment.