In the past I used Norton Ghost 2003 to create images of my installation to allow me a very quick reinstallation of Windows and the most important programs. I might retire NG 2003 and instead use DriveImage XML. In any case, Win7 creates a new partition "System Reserved" (100MB) but DriveImage XML does not see it for backup. Do I need to image that or is it enough to image C which I could play back on a newly partitioned HD, i.e. "System Reserved" is missing? What is that partition for anyways? Note that I have Windows 7 Home Premium.
Hello hama, welcome to Seven Forums!
The Windows 7 created "System Reserved" partition is where the boot files needed to boot/start Windows are stored and if it is not included in a created image of Windows 7 you will not be able to use that image and Windows 7 will not start without doing startup repairs to create new boot files to the re-imaged Windows 7 partition.
Below is an excellent free program fully compatible with Windows 7 for creating system images; have a look at this tutorial at the link below and be sure to post back with any further questions you may have and to keep us informed.
Imaging with free Macrium
The Windows 7 created "System Reserved" partition is where the boot files needed to boot/start Windows are stored and if it is not included in a created image of Windows 7 you will not be able to use that image and Windows 7 will not start without doing startup repairs to create new boot files to the re-imaged Windows 7 partition.
Below is an excellent free program fully compatible with Windows 7 for creating system images; have a look at this tutorial at the link below and be sure to post back with any further questions you may have and to keep us informed.
Imaging with free Macrium
Bare Foot Kid, thanks for the reply. I just found the "Backup and Restore" feature built into Windows 7. It looks like this will create an image with Windows and all my programs and I can also create a repair disc which I assume allows me to partition the HD before putting the image back. How does the "Backup and Restore" differ with the program you mentioned?
Btw, the link you gave indicates there is an option not to have this separate 100Mbyte partition. Windows 7 did not give me any option NOT to have that partition. So how do you achieve not to have it?
Btw, the link you gave indicates there is an option not to have this separate 100Mbyte partition. Windows 7 did not give me any option NOT to have that partition. So how do you achieve not to have it?
Create a partition, format it as NTFS, install Windows to it - instead of just selecting a disk and be done with it...
zzz2496
zzz2496
If you have the 100MB System reserved partition it is best left in place and included in the created images; removing it is more trouble than it's worth. 
I'm not really the best at backup questions, keep checking back though as I'm sure someone will answer these questions for you.
I'm not really the best at backup questions, keep checking back though as I'm sure someone will answer these questions for you.
Generally there is no need to image the 100MB boot partition. It is enough if you image your C partition and leave the little partition alone. Just make sure that you do not mark the C partition as "active" and do not check "restore MBR" during a possible recovery. Both those functions pertain to the 100MB boot partition. If you read the instructions of the tutorial and follow the video, you will know what I am talking about.
�� Quote: Originally Posted by zzz2496 
Create a partition, format it as NTFS, install Windows to it - instead of just selecting a disk and be done with it...
zzz2496
zzz2496
Btw, I am using an upgrade (Windows 7 Home Premium). The original HD only had one partition so I had to delete it and create the OS partition as described above.
When Windows 7 is installed to a new (unallocated) Hard Disk Drive it automatically creates the System reserved partition.
If you really want to recover that space, have a look at Option Two in this tutorial at the link below.
Partition Wizard : Use the Bootable CD
If you really want to recover that space, have a look at Option Two in this tutorial at the link below.
Partition Wizard : Use the Bootable CD
I actually don't care too much about having these last 100Mbytes. The only thing I want to avoid is any complications later on when putting the image back on the machine. It seems to me there is much less risk doing this if you only have one partition to recover than some 'secret' additional partition.
Having said all that, I guess the built in "Backup and Restore" should work just fine. That actually makes me wonder why there is this Macrium software. What is the advantage over the "Backup and Restore" function for simple disk images and restores? I checked their website but did not find a clear answer.
Having said all that, I guess the built in "Backup and Restore" should work just fine. That actually makes me wonder why there is this Macrium software. What is the advantage over the "Backup and Restore" function for simple disk images and restores? I checked their website but did not find a clear answer.
�� Quote: Originally Posted by hama I actually don't care too much about having these last 100Mbytes. The only thing I want to avoid is any complications later on when putting the image back on the machine. It seems to me there is much less risk doing this if you only have one partition to recover than some 'secret' additional partition.
Having said all that, I guess the built in "Backup and Restore" should work just fine. That actually makes me wonder why there is this Macrium software. What is the advantage over the "Backup and Restore" function for simple disk images and restores? I checked their website but did not find a clear answer.
Having said all that, I guess the built in "Backup and Restore" should work just fine. That actually makes me wonder why there is this Macrium software. What is the advantage over the "Backup and Restore" function for simple disk images and restores? I checked their website but did not find a clear answer.
�� Quote: Originally Posted by whs The difference is complicated versus easy. If you are a seasoned Geek and can wrestle with the /7 imaging, then use it. If you want to make your life easy, use Macrium.
+1
The bottom line is that Windows imaging will gray out the option to untick the 100MB System Reserved Partition because it knows it is an essential link in the boot sequence. Windows will also store away the critical Master Boot Record (MBR) which lives on the first physical sector of the disk. When windows reimages it puts the MBR, System reserved (100MB), C:, selected other partitions back in exactly the same position they were imaged from. This way you can even put them back on a new disk.
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. Reimaging C: alone will often work because the system reserved partition has not been changed or damaged. But when it has been damaged or altered you will need the correct image. A simple example your BCD store gets screwed up - you will need your image of the 100MB partition because that's where the BCD lives.
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. Reimaging C: alone will often work because the system reserved partition has not been changed or damaged. But when it has been damaged or altered you will need the correct image. A simple example your BCD store gets screwed up - you will need your image of the 100MB partition because that's where the BCD lives.
Ok, I will give this a try but have one initial question. It says
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
�� Quote: Originally Posted by hama Ok, I will give this a try but have one initial question. It says
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
�� Quote: Originally Posted by mjf ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Second question: What you said contradicts with what was advised, i.e. "Rather mark the partition as primary and answer the MBR question with do not replace. Else, your restored system will become unbootable." With your suggestion the first part still applies (mark as primary). The contradiction is on the second part where they claim the system will become unbootable. So what is correct?
�� Quote: Originally Posted by mjf �� Quote: Originally Posted by hama Ok, I will give this a try but have one initial question. It says
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
Imaging with free Macrium
�� Quote: Originally Posted by hama Ok, I will give this a try but have one initial question. It says
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
"mark the partition as primary and answer the MBR question with do not replace."
So how would I handle the case to make a complete new install (including the MBR) or loading the image onto a bigger HD? Will I have to do two images, one for the C/OS drive and one for the "System Reserved" partition? Then I would first restore the MBR and have that marked as Active and DO REPLACE MBR (which on a new HD would not be there). Then in a second step I would restore the C/OS drive marking the partition as primary and NOT replacing the MBR? In other words, I would use a two step process both for backup and restore as described above?
�� Quote: Originally Posted by hama �� Quote: Originally Posted by mjf ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Second question: What you said contradicts with what was advised, i.e. "Rather mark the partition as primary and answer the MBR question with do not replace. Else, your restored system will become unbootable." With your suggestion the first part still applies (mark as primary). The contradiction is on the second part where they claim the system will become unbootable. So what is correct?
2. in that case, the C partition is a normal primary partition and the boot part is solely with the 100MB boot partition (active partition).
�� Quote: Originally Posted by whs �� Quote: Originally Posted by hama �� Quote: Originally Posted by mjf ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Second question: What you said contradicts with what was advised, i.e. "Rather mark the partition as primary and answer the MBR question with do not replace. Else, your restored system will become unbootable." With your suggestion the first part still applies (mark as primary). The contradiction is on the second part where they claim the system will become unbootable. So what is correct?
2. in that case, the C partition is a normal primary partition and the boot part is solely with the 100MB boot partition (active partition).
2. don't understand.
�� Quote: Originally Posted by hama �� Quote: Originally Posted by mjf ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Macrium stores away the MBR with each partition it images and gives you the option to replace it each time you reimage a partition. Generally you have to reimage each partition in turn. The 100MB system reserved partition is treated like any other partition and is optional. I suggest do image it each time. ...
Second question: What you said contradicts with what was advised, i.e. "Rather mark the partition as primary and answer the MBR question with do not replace. Else, your restored system will become unbootable." With your suggestion the first part still applies (mark as primary). The contradiction is on the second part where they claim the system will become unbootable. So what is correct?
Now we are talking Macrium OK.
Imaging: Tick the partition you want to image. Macrium doesn't view the 100MB partition as anything other than another partition. Tick it. C: containing your Windows 7 operating system (Boot, page file,.......). Tick it. You image the multiple partitions ticked.
Reimaging to the existing disk: Macrium stores the partition set you ticked. From the set you restore which partitions you want to. In many (most?) case simply restoring c: is all you need. Because the MBR and System reserved are ok. IF you have problems go back and replace system reserved. If you still have problems go back and select replace MBR. Reimage each partition in turn (for Macrium free).
MS imaging doesn't give you these options. It replaces the lot from the image!
Reimaging a new disk: You will need MBR, Active system reserved, and C:
Reimaging to a larger disk you will get a region of "Unallocated Space". Use MS disk management or the more flexible Partition Wizard to make this usable space.
As for cloning - why bother.
It is always the best strategy to do away with the System reserved partition when clean installing Windows 7.
I do not know whether this has been mentioned before or exists in some form here. Even if, I consider it is worth repeating and give it repeated visibility.
I always resort to method 3 enunciated in this article for a clean install of Windows 7. Another nice tutorial on this here.
Bye bye System Reserved Partition. Don't bother me ever.
I do not know whether this has been mentioned before or exists in some form here. Even if, I consider it is worth repeating and give it repeated visibility.
I always resort to method 3 enunciated in this article for a clean install of Windows 7. Another nice tutorial on this here.
Bye bye System Reserved Partition. Don't bother me ever.
�� Quote: Originally Posted by Ponmayilal It is always the best strategy to do away with the System reserved partition when clean installing Windows 7.
I do not know whether this has been mentioned before or exists in some form here. Even if, I consider it is worth repeating and give it repeated visibility.
I always resort to method 3 enunciated in this article for a clean install of Windows 7. Another nice tutorial on this here.
Bye bye System Reserved Partition. Don't bother me ever.
I do not know whether this has been mentioned before or exists in some form here. Even if, I consider it is worth repeating and give it repeated visibility.
I always resort to method 3 enunciated in this article for a clean install of Windows 7. Another nice tutorial on this here.
Bye bye System Reserved Partition. Don't bother me ever.
While doing the install as mentioned one is not curtailing anything.
It is as good as creating a partition and formatting it beforehand using any other tool/utility and then installing Windows 7 on it - which is the normal method suggested when one is averse to seeing an ugly 100 MB System Reserved Partition.
Here without taking recourse to any other tool/utility, we are using the in-built functionality of the set-up disk to do the same and create a single partition , format it and then install Windows 7, all at one go.
That said, I stand to be corrected, if anyone can categorically establish that the install as mentioned does away with any role that is played by the System Reserved Partition. So far, I have not come across any mention of it.
It is as good as creating a partition and formatting it beforehand using any other tool/utility and then installing Windows 7 on it - which is the normal method suggested when one is averse to seeing an ugly 100 MB System Reserved Partition.
Here without taking recourse to any other tool/utility, we are using the in-built functionality of the set-up disk to do the same and create a single partition , format it and then install Windows 7, all at one go.
That said, I stand to be corrected, if anyone can categorically establish that the install as mentioned does away with any role that is played by the System Reserved Partition. So far, I have not come across any mention of it.
�� Quote: Originally Posted by Ponmayilal While doing the install as mentioned one is not deleting or curtailing anything.
It is as good as creating a partition and formatting it beforehand using any other tool/utility and then installing Windows 7 on it - which is the normal method suggested when one is averse to seeing an ugly 100 MB System Reserved Partition.
Here without taking recourse to any other tool/utility, we are using the in-built functionality of the set-up disk to do the same and create a single partition , format it and then install Windows 7, all at one go.
That said, I stand to be corrected, if anyone can categorically establish that the install as mentioned does away with any role that is played by the System Reserved Partition. So far, I have not come across any mention of it.
It is as good as creating a partition and formatting it beforehand using any other tool/utility and then installing Windows 7 on it - which is the normal method suggested when one is averse to seeing an ugly 100 MB System Reserved Partition.
Here without taking recourse to any other tool/utility, we are using the in-built functionality of the set-up disk to do the same and create a single partition , format it and then install Windows 7, all at one go.
That said, I stand to be corrected, if anyone can categorically establish that the install as mentioned does away with any role that is played by the System Reserved Partition. So far, I have not come across any mention of it.
Here's a specific example where it is quite useful.
Boot Logical Partitions
Agreed, that in a multiboot environment, it may be preferable to keep it in tact.
But then think of it, that almost 90% of the users are one-OS oriented and then questions like in this thread emanate. For all of them, it is better to get away with it.
I have done away with it in all my systems. No problemo.
But then think of it, that almost 90% of the users are one-OS oriented and then questions like in this thread emanate. For all of them, it is better to get away with it.
I have done away with it in all my systems. No problemo.
Looking at the 100MB reserved boot partition, it really reminds me how MS took many cues from *nix world. Maybe in the next version of Windows, MS will finally let go of Win32 compatibility altogether, and lets go of the drive letters...
Btw, for those who are curious - the 100MB boot partition is used when you need to boot Windows 7 contained in VHD.
zzz2496
Btw, for those who are curious - the 100MB boot partition is used when you need to boot Windows 7 contained in VHD.
zzz2496
The 100mb System Reserved partition also makes the Repair My Computer console on DVD and Repair CD conveniently available on Advanced Boot Tools accessed by tapping F8 at bootup. This may be reason enough to accept it during install - you can repair your laptop in a coffee shop, etc.
If an imaging app won't let you include that partition in your C image, then choose to include MBR which should cover it. If not and reimaged Win7 won't start, mark it's partition active and run Startup Repair up to 3 separate times with reboots to write the System MBR to Win7.
To avoid the Sys Reserved partition during install: either pre-partition, or delete the install partition and enlarge the 100mb partiition the installer creates to install Win7 upon it.
If an imaging app won't let you include that partition in your C image, then choose to include MBR which should cover it. If not and reimaged Win7 won't start, mark it's partition active and run Startup Repair up to 3 separate times with reboots to write the System MBR to Win7.
To avoid the Sys Reserved partition during install: either pre-partition, or delete the install partition and enlarge the 100mb partiition the installer creates to install Win7 upon it.
�� Quote: Originally Posted by gregrocker The 100mb System Reserved partition also makes the Repair My Computer console on DVD and Repair CD conveniently available on Advanced Boot Tools accessed by tapping F8 at bootup. This may be reason enough to accept it during install - you can repair your laptop in a coffee shop, etc.
�� Quote: Originally Posted by gregrocker If an imaging app won't let you include that partition in your C image, then choose to include MBR which should cover it. ...
�� Quote: Originally Posted by gregrocker To avoid the Sys Reserved partition during install: either pre-partition, or delete the install partition and enlarge the 100mb partiition the installer creates to install Win7 upon it.
Here is the boot sequence of a BIOS booted PC (virtually every PC out there)
BIOS --> MBR (inc partition table) at start of disk --> [ PBR (at start of active partition) --> Boot Manager (Using BCD) ] --> C:\windows\system32\winload.exe
[....] Key elements of 100MB system reserved for booting
The Master Boot Record (MBR) is on the first physical sector of your boot HDD. Windows imaging copies it automatically when you make an image and replaces it automatically when you reimage. It does the same thing for the system reserved partition. You have no choice and most non technical users don't even know they exist.
Macrium also makes a copy of the MBR when it creates a partition image set. It lets the user decide whether to replace it or not when you reimage. Macrium does not automatically select the 100MB system reserved partition you must select it. When you backup your Windows Operating system (eg. C: (Boot,...)) with Macrium I firmly believe you should also select the System reserved active partition if you have one. When you reimage you can either select it or not.
Ponmayilad,
You made a sweeping statement about the 100MB system reserved partition which was clearly incorrect as I politely demonstrated to you. It has a purpose and unless it is causing a problem just leave it alone.
For most users the inbuilt Windows imaging program works and couldn't be easier for the non technical user. They don't need to know the existence of anything called an MBR or a system reserved partition. They just need to press a couple of buttons. With this ease of use comes some lack of flexibility which doesn't suite some more technically aware.
Next comes Macrium Reflect (Free edition) in terms of ease of use but more flexibility.
After that comes Paragon (Free edition). This has more complexity and flexibility again in my opinion. I wouldn't recommend it over the others to the non technical in a pink fit.
All 3 imaging programs are good in their own right.
BIOS --> MBR (inc partition table) at start of disk --> [ PBR (at start of active partition) --> Boot Manager (Using BCD) ] --> C:\windows\system32\winload.exe
[....] Key elements of 100MB system reserved for booting
The Master Boot Record (MBR) is on the first physical sector of your boot HDD. Windows imaging copies it automatically when you make an image and replaces it automatically when you reimage. It does the same thing for the system reserved partition. You have no choice and most non technical users don't even know they exist.
Macrium also makes a copy of the MBR when it creates a partition image set. It lets the user decide whether to replace it or not when you reimage. Macrium does not automatically select the 100MB system reserved partition you must select it. When you backup your Windows Operating system (eg. C: (Boot,...)) with Macrium I firmly believe you should also select the System reserved active partition if you have one. When you reimage you can either select it or not.
Ponmayilad,
You made a sweeping statement about the 100MB system reserved partition which was clearly incorrect as I politely demonstrated to you. It has a purpose and unless it is causing a problem just leave it alone.
For most users the inbuilt Windows imaging program works and couldn't be easier for the non technical user. They don't need to know the existence of anything called an MBR or a system reserved partition. They just need to press a couple of buttons. With this ease of use comes some lack of flexibility which doesn't suite some more technically aware.
Next comes Macrium Reflect (Free edition) in terms of ease of use but more flexibility.
After that comes Paragon (Free edition). This has more complexity and flexibility again in my opinion. I wouldn't recommend it over the others to the non technical in a pink fit.
All 3 imaging programs are good in their own right.
^Your viewpoint is well taken. By the same token, my appreciation goes to gregrocker who put everything in a nice little package.
I have also gone through a related thread here which reinforces my perception that except in a mutiboot environment and in Windows Ultimate in which it plays some role in bitlocker encryption, it is safe to do away with the SRP if one is averse to it and that it makes life that much easier and less confusing when imaging.
On the question of using the Windows in-built backup, I am now perplexed. If it were that sufficient and capable even for a novice, why at all one should look at Macriumreflect or for any other imaging software and discuss the how-to in multiple posts just for the simple task of imaging and restoring?? I also refer to post #10 in this thread.
Sorry, I stick to my perception. Individual mileage varies.
I have also gone through a related thread here which reinforces my perception that except in a mutiboot environment and in Windows Ultimate in which it plays some role in bitlocker encryption, it is safe to do away with the SRP if one is averse to it and that it makes life that much easier and less confusing when imaging.
On the question of using the Windows in-built backup, I am now perplexed. If it were that sufficient and capable even for a novice, why at all one should look at Macriumreflect or for any other imaging software and discuss the how-to in multiple posts just for the simple task of imaging and restoring?? I also refer to post #10 in this thread.
Sorry, I stick to my perception. Individual mileage varies.
�� Quote: Originally Posted by Ponmayilal ^Your viewpoint is well taken. By the same token, my appreciation goes to gregrocker who put everything in a nice little package.
I have also gone through a related thread here which reinforces my perception that except in a mutiboot environment and in Windows Ultimate in which it plays some role in bitlocker encryption, it is safe to do away with the SRP if one is averse to it and that it makes life that much easier and less confusing when imaging.
On the question of using the Windows in-built backup, I am now perplexed. If it were that sufficient and capable even for a novice, why at all one should look at Macriumreflect or for any other imaging software and discuss the how-to in multiple posts just for the simple task of imaging and restoring??
Sorry, I stick to my perception. Individual mileage varies.
I have also gone through a related thread here which reinforces my perception that except in a mutiboot environment and in Windows Ultimate in which it plays some role in bitlocker encryption, it is safe to do away with the SRP if one is averse to it and that it makes life that much easier and less confusing when imaging.
On the question of using the Windows in-built backup, I am now perplexed. If it were that sufficient and capable even for a novice, why at all one should look at Macriumreflect or for any other imaging software and discuss the how-to in multiple posts just for the simple task of imaging and restoring??
Sorry, I stick to my perception. Individual mileage varies.
On this matter I disagree with gregrocker. I don't know of any imaging package that doesn't allow you to select the 100MB System Reserved partition (MS imaging forces you to). But more importantly the MBR is a totally different entity to the System reserved partition. Selecting MBR to save or recover has nothing to do with the System reserved.
Your last paragraph indicates you didn't read what I said. Some people appear to have problems with MS imaging, other people prefer the flexibility and features of other imaging software. I primarily use MS imaging but also Macrium as a safeguard and for flexibility when I need it.
^ Sorry, if you had missed the one line I added to my last post. It is this:"I also refer to post #10 in this thread." I go with it. (though not Macrium, since I use others)
Now my straight question.
I do not use or envisage using any other OS. So no multiboot. It is the case with most users.
I do not use bitlocker encryption. Neither do I intend to. Again, it is the case with most users.
Now please tell me categorically, count and specify;
What do I lose if I eliminate the System Reserved Partition and install Windows 7?
Sorry, if you had missed the one line I added to my last post. It is this:"I also refer to post #10 in this thread." I go with it. (though not Macrium, since I use others)Now my straight question.
I do not use or envisage using any other OS. So no multiboot. It is the case with most users.
I do not use bitlocker encryption. Neither do I intend to. Again, it is the case with most users.
Now please tell me categorically, count and specify;
What do I lose if I eliminate the System Reserved Partition and install Windows 7?
You lose having the Repair My Computer console placed on the F8 Advanced Boot Tools menu. You'll need the DVD or Repair CD to access it.
Yep, that I have already said that imaging and restoring is my primary and recommended method of restoration and even geeks fumble and tumble using those hit F8 and try it 3 times stuff.( I think I had tried it once and gave up )
IMO, no non-technical user will be comfortable using it much the same way as he will not be, imaging with the built-in-backup utility. (see post no. 10). It is much easier to image with a third party imaging software and restore and I have practically found that non-technical users are more receptive to this method.
And so finally I have to conclude, that for non-technical users, given that set of conditions, I would rather call it user preferences, doing away with the SRP during the installation, takes nothing else away that he will regret and removes any confusion during the imaging and restore process.
) IMO, no non-technical user will be comfortable using it much the same way as he will not be, imaging with the built-in-backup utility. (see post no. 10). It is much easier to image with a third party imaging software and restore and I have practically found that non-technical users are more receptive to this method.
And so finally I have to conclude, that for non-technical users, given that set of conditions, I would rather call it user preferences, doing away with the SRP during the installation, takes nothing else away that he will regret and removes any confusion during the imaging and restore process.
There are instances it is required and if not there it will be created; have a look at this information from his tutorial at the link below.
BitLocker Drive Encryption - Windows 7 Drive - Turn On or Off with no TPM
BitLocker Drive Encryption - Windows 7 Drive - Turn On or Off with no TPM
Quote:
Have at least two partitions. One partition must include the drive Windows 7 is installed on and must be at least 400 MB. This is the drive that BitLocker will encrypt. The other partition is the active partition, which must remain unencrypted so that the computer can be started. If you have the 100 MB System Reserved partition that Windows 7 creates during installation on a blank drive or partition, then BitLocker will store the key on it instead. If your computer does not have two partitions, BitLocker will create them for you.
For the vast majority of users that use Home Premium, the SRS is really not required. I wonder why they did not reserve it for Umtimate which is the system with the bitlocker facility. It confuses the hell out of everybody and occupies an additional primary which leads to 4 primaries out of the box in many OEM systems. The operational characteristics thereafter are difficult for non-geeks whether it is for creating a data partition, making images, restoring images, etc. That's too bad.
�� Quote: Originally Posted by whs For the vast majority of users that use Home Premium, the SRS is really not required. I wonder why they did not reserve it for Umtimate which is the system with the bitlocker facility. It confuses the hell out of everybody and occupies an additional primary which leads to 4 primaries out of the box in many OEM systems. The operational characteristics thereafter are difficult for non-geeks whether it is for creating a data partition, making images, restoring images, etc. That's too bad.
Maybe it's time for MS to move to Extended/Logicals with a single System Reserved for booting.
System Reserved : Multi Boot from Logical Partitions
That would be the way to go - especially the OEMs should be more sensible and adopt that approach.
�� Quote: Originally Posted by whs That would be the way to go - especially the OEMs should be more sensible and adopt that approach.
That's an even better idea mate!
�� Quote: Originally Posted by Ponmayilal ^ Sorry, if you had missed the one line I added to my last post. It is this:"I also refer to post #10 in this thread." I go with it. (though not Macrium, since I use others)
Now my straight question.
I do not use or envisage using any other OS. So no multiboot. It is the case with most users.
I do not use bitlocker encryption. Neither do I intend to. Again, it is the case with most users.
Now please tell me categorically, count and specify;
What do I lose if I eliminate the System Reserved Partition and install Windows 7?
Sorry, if you had missed the one line I added to my last post. It is this:"I also refer to post #10 in this thread." I go with it. (though not Macrium, since I use others)Now my straight question.
I do not use or envisage using any other OS. So no multiboot. It is the case with most users.
I do not use bitlocker encryption. Neither do I intend to. Again, it is the case with most users.
Now please tell me categorically, count and specify;
What do I lose if I eliminate the System Reserved Partition and install Windows 7?
Under the constraints:
* Using one operating system only.
* Don't need/want any additional functionality that might be provided by the System reserved partition
Can you dispense with the 100MB partition: YES
Some people don't have it.
BUT the critical boot elements (as shown in my little flow diagram) of this system Reserved partition simply have a new home in the now active OS partition.
So what have you gained in the exercise: An extra primary partition letter. Use of extended/logical offsets this apparent gain.
The limitation of 4 primary partitions per disk is imposed by the partition table constraints in the 512 byte MBR. With UEFI this constraint is lifted and Microsoft have a MSR (Microsoft System Reserved) partition which you'll have to live with.
----------------------------------------------------------------
To save an extra Post - responding to misc others.
Any suggest to the novice that this 100MB partition is useless is going to cause them grief when they simply delete it.
Macrium users should always save the 100MB system reserved in their partition set. They don't have to select it in recovery but they will need it if they are recovering to a new disk. Macrium always makes a copy of the MBR with every partition set just in case you need it in recovery.
Any statement that Windows imaging is for Geeks is just baffling.
Quote:
Macrium users should always save the 100MB system reserved in their partition set. They don't have to select it in recovery but they will need it if they are recovering to a new disk
�� Quote: Originally Posted by whs Quote:
Macrium users should always save the 100MB system reserved in their partition set. They don't have to select it in recovery but they will need it if they are recovering to a new disk
I would do it every single time.
�� Quote: Originally Posted by mjf �� Quote: Originally Posted by whs Quote:
Macrium users should always save the 100MB system reserved in their partition set. They don't have to select it in recovery but they will need it if they are recovering to a new disk
I would do it every single time.
�� Quote: Originally Posted by whs �� Quote: Originally Posted by mjf �� Quote: Originally Posted by whs True, but you only need to image it once - just to be prepared for a Hardware problem. Not every morning when you take an image - as I do.
I would do it every single time.
The system reserved partition is so small I think it's just easier to keep a copy each time included in your backup set.
Now I only have a couple of copies of my hidden factory recovery partition because that is larger and is static.
Inasmuch as including the SRP in the image does not hurt much (phew.... its only 100MB), I go with mjf, that it is a good practice.
(Paragon Software does give me the option to select and include the first sector (MBR) and I always do that. (I do not have SRP.) ShadowProtect automatically includes it (first sector) in the system image (no choice) and gives me the choice to restore that too or leave it during the restore process. Default is restore that too.)
(Paragon Software does give me the option to select and include the first sector (MBR) and I always do that. (I do not have SRP.) ShadowProtect automatically includes it (first sector) in the system image (no choice) and gives me the choice to restore that too or leave it during the restore process. Default is restore that too.)
�� Quote: Originally Posted by gregrocker [If System Reserved is deleted] You lose having the Repair My Computer console placed on the F8 Advanced Boot Tools menu. You'll need the DVD or Repair CD to access it.
1) Is it possible to perform Startup Repair using a Windows 7 SP1-U.iso burnt to DVD ?
2) I understand that the size of the System Repair Disc created from within the Windows environment is ~165MB for Win 7 (64 bit) & ~143MB for Win 7 (32 bit). How then do the system repair tools fit into the "100MB System Reserved" ? Do the said tools exist in inactive compressed form while inside the System Reserved partition ?
3) My System Reserved partition (Win 7 Home Premium SP1, 64 bit) is 199MB in size (with 166MB free space). Why the size discrepancy ? I have not done anything to it before, & I don't use BitLocker.
4) Incidentally, I had experienced unexpected bootup failure in mid-Dec 2014 (the 1st ever after 4 years of very active use of my OEM laptop), & had to repeatedly run Startup Repair via Windows Recovery environment.
Since then, I have no idea if all the bootup & other system files had been repaired or not. sfc /scannow initially kept showing unrepairable corrupt files, but oddly enough, the CBS logs provided no indication of the said corrupted files but merely said that 0 files had been repaired � this & other problems are identical to those described in this thread. Then miraculously a week ago, it suddenly reported zero integrity violations, although all that while, I had (out of apprehension) deliberately avoided restarting the system, as well as avoided Windows Update until the newly-arisen OS problems are resolved.
Unfortunately, ever since recovery from the said bootup failure, the OS has started to fall apart bit by bit. The symptoms & errors are wide-ranging, quite severe, & very coincidentally enough, identical to the long list of various problems reported for the buggy Windows Update KB3004394 (09 Dec 2014 Patch Tuesday), although I do not have KB3004394 (the pulled update) &/or KB3024777 (the hotfix) installed. My Windows Update is turned off by default, because my SOP is to keep watch before attempting updates 1 or 2 weeks after Patch Tuesday or the issue of any out-of-band patches.
Bearing (4) in mind, is my current System Reserved partition itself in good condition ? I am planning to clean-install over my obviously-failing Windows 7 (OEM with manual SP1 upgrade), & I'm wondering whether the installation would retain the current System Reserved partition, or write over it.
Thanks !
Không có nhận xét nào:
Đăng nhận xét