{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "slug": "dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it", "url": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/" }, "title": "Identify a new disk conclusively before initializing it", "summary": "What evidence should establish that a disk is safe to initialize?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:16:52+00:00", "modified_at": "2026-09-08T18:17:13+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 224, "potentially_affected": "Use this review when preparing a genuinely new storage device.", "dse_recommendation": "Compare the physical inventory with the disk shown by the management tool, including capacity and the available identifying information.", "primary_source": { "name": "Initialize New Disks", "url": "https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft explains that a newly added disk must be initialized before it is prepared for file storage in Windows; formatting and any required drive-letter assignment follow. Its procedure warns that initializing an in-use disk erases its data and calls for backing up existing files first. The procedure is intended for a new disk without existing data; some USB devices support formatting rather than initialization. Microsoft documentation.

\n

Applicability

\n

Use this review when preparing a genuinely new storage device. Treat an unexpectedly missing or uninitialized existing disk as a separate troubleshooting case. Establish the device identity and data ownership before selecting an operation.

\n

DSE recommendation

\n

Compare the physical inventory with the disk shown by the management tool, including capacity and the available identifying information. Have a second administrator confirm the selected target and the owner’s statement about existing data. Record the intended partitioning and destination workload. If the device identity or data history is uncertain, return the decision to the storage owner before proceeding.

\n

Verification

\n

After an approved initialization, record the selected disk and resulting state. Verify the intended volume and access path before allowing application writes. Retain the prechange identity evidence alongside the completed configuration. If the observed capacity or device association differs from the approved plan, pause allocation and investigate the discrepancy.

\n

Official references

\n

Microsoft Learn: Initialize New Disks. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft explains that a newly added disk must be initialized before it is prepared for file storage in Windows; formatting and any required drive-letter assignment follow. Its procedure warns that initializing an in-use disk erases its data and calls for backing up existing files first. The procedure is intended for a new disk without existing data; some USB devices support formatting rather than initialization. Microsoft documentation.\nApplicability\nUse this review when preparing a genuinely new storage device. Treat an unexpectedly missing or uninitialized existing disk as a separate troubleshooting case. Establish the device identity and data ownership before selecting an operation.\nDSE recommendation\nCompare the physical inventory with the disk shown by the management tool, including capacity and the available identifying information. Have a second administrator confirm the selected target and the owner’s statement about existing data. Record the intended partitioning and destination workload. If the device identity or data history is uncertain, return the decision to the storage owner before proceeding.\nVerification\nAfter an approved initialization, record the selected disk and resulting state. Verify the intended volume and access path before allowing application writes. Retain the prechange identity evidence alongside the completed configuration. If the observed capacity or device association differs from the approved plan, pause allocation and investigate the discrepancy.\nOfficial references\nMicrosoft Learn: Initialize New Disks. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft explains that a newly added disk must be initialized before it is prepared for file storage in Windows; formatting and any required drive-letter assignment follow. Its procedure warns that initializing an in-use disk erases its data and calls for backing up existing files first. The procedure is intended for a new disk without existing data; some USB devices support formatting rather than initialization. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks).\n\n## Applicability\n\nUse this review when preparing a genuinely new storage device. Treat an unexpectedly missing or uninitialized existing disk as a separate troubleshooting case. Establish the device identity and data ownership before selecting an operation.\n\n## DSE recommendation\n\nCompare the physical inventory with the disk shown by the management tool, including capacity and the available identifying information. Have a second administrator confirm the selected target and the owner’s statement about existing data. Record the intended partitioning and destination workload. If the device identity or data history is uncertain, return the decision to the storage owner before proceeding.\n\n## Verification\n\nAfter an approved initialization, record the selected disk and resulting state. Verify the intended volume and access path before allowing application writes. Retain the prechange identity evidence alongside the completed configuration. If the observed capacity or device association differs from the approved plan, pause allocation and investigate the discrepancy.\n\n## Official references\n\n[Microsoft Learn: Initialize New Disks](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "url": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Identify a new disk conclusively before initializing it", "item": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "url": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/", "headline": "Identify a new disk conclusively before initializing it", "description": "What evidence should establish that a disk is safe to initialize?", "abstract": "What evidence should establish that a disk is safe to initialize?", "articleBody": "Source facts\nMicrosoft explains that a newly added disk must be initialized before it is prepared for file storage in Windows; formatting and any required drive-letter assignment follow. Its procedure warns that initializing an in-use disk erases its data and calls for backing up existing files first. The procedure is intended for a new disk without existing data; some USB devices support formatting rather than initialization. Microsoft documentation.\nApplicability\nUse this review when preparing a genuinely new storage device. Treat an unexpectedly missing or uninitialized existing disk as a separate troubleshooting case. Establish the device identity and data ownership before selecting an operation.\nDSE recommendation\nCompare the physical inventory with the disk shown by the management tool, including capacity and the available identifying information. Have a second administrator confirm the selected target and the owner’s statement about existing data. Record the intended partitioning and destination workload. If the device identity or data history is uncertain, return the decision to the storage owner before proceeding.\nVerification\nAfter an approved initialization, record the selected disk and resulting state. Verify the intended volume and access path before allowing application writes. Retain the prechange identity evidence alongside the completed configuration. If the observed capacity or device association differs from the approved plan, pause allocation and investigate the discrepancy.\nOfficial references\nMicrosoft Learn: Initialize New Disks. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:52+00:00", "dateModified": "2026-09-08T18:17:13+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-019-identify-a-new-disk-conclusively-before-initializing-it/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Identify a new disk conclusively before initializing it" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 224, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Initialize New Disks", "url": "https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks" } } ] } }