Can I delete the system reserved partition from 100MB

Anonymous
2009-06-06T22:02:00+00:00

Is there a possibility to install windows 7 (clean install) without making a extra (hidden) partition "system reserved" from 100mb?

or how can I delete this partition after install ?

Why is it for?

I have the meaning that this slows down my hard drive a little ? 

thanks

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2009-06-11T15:08:03+00:00

Hi Johan G,

Thanks for posting to Getting Ready for Windows 7 .

The 100MB partition is a system partition and contains boot files. Disk Manager will not allow you to remove this partition because removing this partition could cause the system to not boot.

Thanks for posting your question to Getting Ready for Winodws 7 community group.

Regards,


Debbie

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forumand let us know what you think.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2009-06-06T22:56:08+00:00

Thanks anyway,

i wil try a install with an different harddisk.

Was this answer helpful?

0 comments No comments

149 additional answers

Sort by: Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2010-07-23T13:12:25+00:00

    Here is why the system partition is going to be a problem in the very near future, and why Microsoft needs to address the problem right now.

    Consider the following scenario, which is going the be very common soon enough:

    • standard BIOS PC (not EFI => can only boot from MBR disk), i.e. 99% of the existing machines out there
    • HDD 1: SSD, for the Windows 7 system files and boot (or any disk that can be booted from by standard BIOS)
    • HDD 0: >2TB HDD, to store data, media files, etc.

    As you might be aware, the only way to address a whole >2TB disk space is if the disk is GPT instead of MBR, as MBR can only use 2 TB space ever. However, GPT disks are not bootable on a BIOS system (only on EFI). But then, the Windows 7 installer insists on creating the System Reserved partition on a different disk as the system one (or it might be HDD 0 as pointed above - I had the issue with a >2TB RAID5 array, which would always be detected as first drive), and the disk on which it creates it needs to be bootable . Therefore, if left unchecked, Windows 7 will set the >2TB HDD to MBR, and, even if your disk has 3 or 4 TB of disk space, you will not be able to access anything beyond the 2 TB mark. This is sure to leave >2TB disks users extremely unhappy with Windows 7...

    Now, if you try to partition your >2TB disk to GPT beforehand, so that Windows cannot partition it to MBR, the Windows 7 installer will throw error 0x80300024 and refuse to install. The only workaround to avoid 0x80300024, and keep a GPT disk is to actually unplug your >2TB disk during installation, and only plug it in after the installation is done. This is far from the straightforward Windows 7 installation Microsoft promised to its customers...

    In short, Microsoft's non optional installation of the System Reserved partition IS going to be a headache for Windows 7 users in the near future.

    The creation of this partition MUST either be made optional in the upcoming Windows 7 releases, or Microsoft needs to tell us how it is possible to bypass it during installation.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-08-12T16:29:09+00:00

    This problem should not be occurring with a 1TB drive.  Adding one required initialization, which removed my boot partition and moved it to the large drive.  I had to create a boot partition on the C drive and delete the new boot partition.  Now I have a separate E system reserved drive on C.  The first large drive had to be RMAed.  Backup on another system with smaller drives found bad clusters that were removed.  I had not found this before and the sizes reported show no removal of clusters.  This may have been due to my abuses but the 1TB issue is not.

    Was this answer helpful?

    0 comments No comments