Issue with formatting a secondary drive in Windows 8


Recommended Posts

Hi all,

i'm having a small issue with formatting a secondary drive in Windows 8.

I have been experiencing sluggish performance with this drive which was being used as a software backup, I backed up all the data on the drive a proceeded to format the drive in computer management, but the drive in question is listed as a system partition and won't let me format it for obvious reasons.

I no idea why a secondary drive has been selected as the system partition, what I would like to know is there a way to move the system partition or do I have to reinstall Windows 8.

As you can see from the screenshot, the F drive is shown as System (Active) this is the drive I cannot format

post-149938-0-15539900-1357756091.png

If that drive is set as 1st disk (Disk 0 ) in the BIOS / SATA port, then no matter which drive you install windows on, it will always use disk 0 for the MBR

No, My primary drive is on the 1st SATA port and always has been, there is no way to configure the drive in the bios other than choosing which device boots first which was my Blu-Ray drive then my primary HDD.

No, My primary drive is on the 1st SATA port and always has been, there is no way to configure the drive in the bios other than choosing which device boots first which was my Blu-Ray drive then my primary HDD.

I would physically unplug it from the board and see if you can boot

If you can. just use disk management to delete the partition and format the drive

I would physically unplug it from the board and see if you can boot

If you can. just use disk management to delete the partition and format the drive

I can't use disk management to format the drive, when I attempt to do this it says "Windows cannot format the system partition on this disk"

You can use Diskpart to do it.

1. Type "diskpart" on the Start screen, then right-click it in the results and run it as an administrator.

2. Type "list disk" to get a list of the drives on your system, then find the one you want to erase. (Double-check this!)

3. Type "select disk X" where X is the drive number from the previous command output.

4. Double-check TWICE that you selected the right drive as Diskpart will not ask for confirmations.

5. Type "list partition" and verify again it's the right drive.

6. Repeat step 4. :)

7. Type "clean"

This will wipe all the partition information from the drive and you should be able to partition and format it in Disk Management.

You might want to switch to the proper disk before step 5 and use the "active" command to mark it so.

With your primary system partition showing as F it is possible you may find your system in an unbootable state so make sure you have a way to recover if necessary.

"You have to delete the partition before formatting"

what?? You format a partition, you can not format a non partitioned disk.

Now he may will delete the partition, and then just create a new one and then format that. But your wording is odd if that was what you meant to say.

Follow greywolf instructions and you should be good.

"You have to delete the partition before formatting"

what?? You format a partition, you can not format a non partitioned disk.

Now he may will delete the partition, and then just create a new one and then format that. But your wording is odd if that was what you meant to say.

Follow greywolf instructions and you should be good.

Yea, well he is saying he can't format the system partition, so he would have to delete it first if it won't let him format it, and yea then make a new one

Yea I see what you are saying, if he deleted it he would have no need to format it after creating a new one - should have excluded the formatting thing and just left "You need to delete the partition"

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

    • No registered users viewing this page.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!