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

    • Exactly. They won't go 100 because current gen consoles are simply too old for any groundbreaking graphics or gaming experience otherwise. They will go with standard (console) price 70 or go with 80 if they really want to go premium. Of course they will have more expensive options too with some useless cosmetics as always.
    • Doesn’t surprise me at all. God is light & He gave us life so it sounds almost logical that we would therefore emit a certain amount of light.
    • This is what I want. Hey Gemini, how do I remove you from all my google products permanently?
    • I would never install install this build before rtm process. only 3 months to go. never install on your daily devices. just wait 3 months.
    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      75
  • Tell a friend

    Love Neowin? Tell a friend!