What is the 100mb partition Windows 7 SOMETMES creates on install?


Recommended Posts

  • 9 months later...

if i want to install win7-64bit on a pc now, should i create the partitions myself or let win7 do it and have the 100mb boot partition. Would there be any issues if dual booting with linux for example, or drive imaging software?

^ouch, is that because of dual booting?

Naa its because I was an idiot and tried to install OSX along side Windows - which worked.. but then I wanted rid of it, deleted the partition and tried to repair the windows MBR which failed so had to reinstall Windows 7 on the OSX partition and install EasyBCD to get back into this partition

Its a right mess, later today I am going to delete the 2nd windows partiton, make a new partition as big as free space I have left - copy all my stuff to there, and format - its doing my head in lol

The 100mb is Windows 7 repair partition. Press F8 before Windows boots and you will see a "Repair Your Computer" option. It comes in handy when Windows cannot boot.

Yes, it is also uses for BitLocker, but that's its secondary purpose.

The 100mb is Windows 7 repair partition. Press F8 before Windows boots and you will see a "Repair Your Computer" option. It comes in handy when Windows cannot boot.

Yes, it is also uses for BitLocker, but that's its secondary purpose.

Did you read the thread? The partition does not contain any repair stuff. You can confirm this yourself by simply mounting it. The repair environment is located on the boot volume of the OS it belongs to and is bigger than 100MB (this makes sense if you think about it, since the recovery feature is specific to a single OS, and not the entire system.) The partition is used only to host the boot loader. It is the system volume. The only purpose it serves in current versions of Windows is to enable full volume encryption and to separate the system volume from the boot volumes. In versions before Vista it was common that the system and boot volume was the same, which added complications for systems with multiple OSes installed. You couldn't reformat the volume that was set as both system and boot without also losing the ability to boot from all other boot volumes you had. Having the system volume be a separate dedicated partition makes this easier. It also makes it slightly more difficult to accidentally delete the boot loader. It wasn't that uncommon for novices to delete the "random" files in the root of the disk to "clean it up" and thus end up with an unbootable system.

If none of this is an issue for you, there is absolutely no reason to create the partition if you don't want to. You can manually create the partitions you want in the installer instead, and doing so has no negative consequences.

Did you read the thread? The partition does not contain any repair stuff. You can confirm this yourself by simply mounting it. The repair environment is located on the boot volume of the OS it belongs to and is bigger than 100MB (this makes sense if you think about it, since the recovery feature is specific to a single OS, and not the entire system.) The partition is used only to host the boot loader. It is the system volume. The only purpose it serves in current versions of Windows is to enable full volume encryption and to separate the system volume from the boot volumes. In versions before Vista it was common that the system and boot volume was the same, which added complications for systems with multiple OSes installed. You couldn't reformat the volume that was set as both system and boot without also losing the ability to boot from all other boot volumes you had. Having the system volume be a separate dedicated partition makes this easier. It also makes it slightly more difficult to accidentally delete the boot loader. It wasn't that uncommon for novices to delete the "random" files in the root of the disk to "clean it up" and thus end up with an unbootable system.

If none of this is an issue for you, there is absolutely no reason to create the partition if you don't want to. You can manually create the partitions you want in the installer instead, and doing so has no negative consequences.

The 100 MB system partition is used primarily as BitLocker partition for BitLocker encryption. Additionally, it also holds the Windows Recovery Environment (WinRE) and boot files with boot manager for booting up the computer for troubleshooting when there is no Windows 7 installation DVD disc on hand.

If you don't believe me, try deleting the partition.

The 100 MB system partition is used primarily as BitLocker partition for BitLocker encryption. Additionally, it also holds the Windows Recovery Environment (WinRE) and boot files with boot manager for booting up the computer for troubleshooting when there is no Windows 7 installation DVD disc on hand.

No, it does not. I explained this. The recovery environment is OS-specific. You can't have a single one for all installed OSes. For this reason, it's located in the \Recovery folder on the individual boot volumes (a boot volume is a volume that contains OS files, a system volume is a volume that contains the boot loader). You can confirm this yourself by looking at this folder. You can also confirm that the recovery environment is larger than 100MB by looking at this folder. You can also confirm that it's not located on the 100MB partition by simply mounting it and looking on it. It's a standard NTFS partition. There is no need to wonder or speculate here, you can easily confirm it all yourself.

If you don't believe me, try deleting the partition.

I never create it on my systems in the first place.

  • 4 weeks later...

Its for bitlocker

Actually, it's only created if a partition is the first (or only) primary partition *and* it is greater than 175 GB (the smallest drive or partition I've seen with that dreaded 100 MB unlettered System Restore partition is my 200 GB SATA-150 DiamondMax). My current 500 GB WD Caviar Green WD500AVVS has the same size System Restore partition (it's still unlettered; therefore, it only shows in Disk Management).

In both cases, Windows was installed clean (onto a hard drive without partitions).

Considering that the same 500 GB WD can now officially be considered *paltry* for a desktop drive, 100 MB is chimp-change (no, that is NOT a mis-spelling).

It is the system partition (the proper name for the partition that contains the boot loader), not system restore partition. There's nothing related to system restore or repair on it, just the boot loader. After all these pages, I can't believe this still isn't clear.

It is the system partition (the proper name for the partition that contains the boot loader), not system restore partition. There's nothing related to system restore or repair on it, just the boot loader. After all these pages, I can't believe this still isn't clear.

Err, yes it is a somewhat system repair partition. If you create a managed install with the WAIK (like a lot of OEMs do) you can use that partition to house your OS recovery files, etc. By default it has a few system files and also the boot files, etc, but you CAN use it to repair your computer if you set it up that way.

Err, yes it is a somewhat system repair partition. If you create a managed install with the WAIK (like a lot of OEMs do) you can use that partition to house your OS recovery files, etc. By default it has a few system files and also the boot files, etc, but you CAN use it to repair your computer if you set it up that way.

It's a 100MB partition, so no, you can't fit all these things on it. It should also have been obvious that we are talking about what Windows uses it for by default, since it is the one creating it. You could also mount it and store your porn on it if you wanted, but that doesn't mean porn storage is its purpose. I can't believe it's such a "mystery." It's a standard NTFS partition and you can freely check what's on it.

It's a 100MB partition, so no, you can't fit all these things on it. It should also have been obvious that we are talking about what Windows uses it for by default, since it is the one creating it. You could also mount it and store your porn on it if you wanted, but that doesn't mean porn storage is its purpose. I can't believe it's such a "mystery." It's a standard NTFS partition and you can freely check what's on it.

Yes, the default contents of that drive are basically the boot manager & system volume info, as well as a few more random files (plus bitlocker if you are using it).

But you are totally wrong in the fact that you can't put a recovery image on there. With WAIK you can put whatever you want, and create the partition as big as you want. This is what OEMs are now using for Win7, and we have done the same at my workplace (usually a 5GB partition with a custom image.wim with our default image/software).

But you are totally wrong in the fact that you can't put a recovery image on there. With WAIK you can put whatever you want, and create the partition as big as you want. This is what OEMs are now using for Win7, and we have done the same at my workplace (usually a 5GB partition with a custom image.wim with our default image/software).

You can also create 52 other partitions as well of various sizes, and fill them with various random things if you want. One for each week of the year. What this thread is about is the one hundred megabytes (100 MB) large partition that Windows creates by itself to host the boot loader, nothing else.

The 100MB partition is created for the Windows 7 Bitlocker feature.

Info

"As a result, Windows 7 automatically creates the necessary disk partitions during installation to greatly simplify BitLocker deployments."

I think it's only created by Ultimate and Business, and only when you install on a bare unpartitioned drive.

Incorrect, I have it on Professional x64 (Windows 7).

It I do believe contains boot files and system files, which should be left alone and not deleted ever.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Meta announces a major leadership change at WhatsApp by Pradeep Viswanathan Meta has announced a major leadership change at WhatsApp, with Will Cathcart stepping down after seven years of leading the world's largest messaging platform. CRED CEO and founder Kunal Shah will take over as the next global head of WhatsApp. CRED is an Indian fintech company focused on creditworthy consumers. As part of the transition, Meta is also making a minority investment in CRED through its Series H funding round. Meta CEO Mark Zuckerberg said Will Cathcart will remain at Meta and move into a new role focused on building new products from the ground up. Cathcart led WhatsApp during a major growth phase, helping the app reach more than 3 billion users worldwide. He also played a key role in expanding WhatsApp’s business offerings while keeping privacy and end-to-end encryption central to the product. Meta’s Chief Product Officer, Chris Cox, said Kunal Shah was selected after a search for a leader who understands WhatsApp’s global scale and future potential. In a leaked internal memo, Cox described Shah as a “serial founder” and one of India’s most respected entrepreneurs, adding that he brings “entrepreneurial energy” and a strong product mindset to the role. As part of the Series H funding round, CRED is raising ₹8,550 crore, or about $900 million, in a round led by Meta. The funding values CRED at ₹43,239 crore, or about $4.5 billion, on a post-money basis. It is important to note that this investment will not give Meta access to CRED customer information. Kunal posted the following on X regarding his new role at Meta: Although Kunal Shah will be stepping away from his operating role as CRED CEO, he will retain his personal shareholding in the company.
    • It wouldn't be hard for me to turn off my TV, if I had one. For one thing, I never scroll Instagram. The only reason I have an account is because Meta created one when it merged the account systems for its various services.
    • OpenAI's new GPT-5.5-Cyber tops Claude Mythos 5 in vulnerability benchmark by Pradeep Viswanathan OpenAI today announced a major expansion of Daybreak, a cybersecurity initiative designed to help defenders find, validate, and fix software vulnerabilities earlier in the development process. The availability of powerful AI models has definitely changed the cybersecurity landscape by making vulnerability discovery much faster. However, the bigger bottleneck for the industry is now patching those vulnerabilities. Impacted software teams need to validate the discovered issues, understand their impact, develop fixes, test them, and deploy patches. Back in March, OpenAI launched a preview of Codex Security, which uses agentic reasoning with automated validation to discover high-impact issues and actionable fixes specific to the codebase. Since then, it has scanned more than 30 million commits across over 30,000 codebases; more than 70,000 findings were marked as fixed by human reviewers, while over 500,000 findings were automatically determined to be fixed. Now, OpenAI is releasing an updated Codex Security plugin that can run deep scans, review recent code changes, generate security reports, trace attack paths, validate findings, and create codebase-specific patches for human review. It can also triage findings from existing scanners, advisories, bug bounty reports, and ticketing systems. OpenAI says the plugin can export results to vulnerability management systems and integrate with workflows using SARIF files, CodeQL queries, the Codex CLI, and the Codex app. Back in May, OpenAI announced the preview of GPT-5.5-Cyber, a new model built on top of the recently released GPT-5.5, designed for specialized cybersecurity work. Today, OpenAI launched the full version of GPT-5.5-Cyber through a limited release for verified defenders. On CyberGym, GPT-5.5-Cyber scored 85.6%, compared with 81.8% for GPT-5.5 and 83.8% for Claude Mythos 5. It also scored 39.5% on ExploitGym, compared with 25.95% for GPT-5.5, and 69.8% on SEC-bench Pro, compared with 63.1%. OpenAI also announced the new Daybreak Cyber Partner Program, which will allow security vendors and service providers to use GPT-5.5 with Trusted Access for Cyber in their products and services. Accenture, Akamai, Cisco, Cloudflare, CrowdStrike, IBM, Palo Alto Networks, Proofpoint, SentinelOne, Wiz, Zscaler, and others were listed as initial partners for this program. OpenAI is also launching Patch the Planet with Trail of Bits, HackerOne, Calif, researchers, and maintainers. More than 30 open-source projects have committed to participate, including cURL, Go, Python, Sigstore, and pyca/cryptography.
    • AMD confirms 26.6.2 FSR driver breaks on many Windows PCs by Sayan Sen Earlier today AMD released a major graphics driver update as it brings support for FSR 4.1 to Radeon RX 7000 series GPUs. The new update, version 26.6.2, also brings support for Assassin's Creed Black Flag Resynced and more. And while the driver technically supports Windows 10 version 21H2 and newer, the tech giant has confirmed that there is a major issue with the new driver on non-Windows 11 PCs as it fails to launch properly on such systems. The error message says, "The version of AMD Software that you have launched is not compatible with your currently installed AMD graphics driver." Therefore on the surface it looks like a compatibility problem. AMD has also confirmed that the device manager will display the yellow bang or yellow exclamation sign alongside your GPU under the Display adapters dropdown. Here is what the Radeon team's official advisory recommends to affected users: "Users Running Windows 10 and AMD Software: Adrenalin Edition 26.6.2 May Encounter Yellow Bang in Device Manager Affecting AMD Radeon RX Series Graphics ... Our Engineers are currently investigating this issue and will provide a fix once it is available. Affected users may revert to AMD Software: Adrenalin Edition 26.6.1 as a temporary workaround." As such you should revert back to the previous 26.6.1 driver which was released earlier this month. In case you were looking to play Assassin's Creed Black Flag Resynced and DOOM: The Dark Ages | Revelations you will probably have to wait a while if you want the driver to support those games officially. You can find the support article here on Microsoft's website.
  • Recent Achievements

    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      208
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Michael Scrip
      89
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!