SATA SSD Not Detected After Installation: Check Disk Management
A technician is installing a 2.5" SATA SSD in a desktop computer that already has an M.2 SATA SSD installed in the primary M.2 slot. After connecting the SATA SSD to a SATA port, the computer boots normally but the new SATA SSD is not detected in Windows. The technician verifies the SATA cable is secure and the drive has power. The motherboard manual shows that the M.2 slot shares bandwidth with SATA port 5. The technician has connected the new drive to SATA port 3. Which of the following should the technician do NEXT to resolve the issue?
Quick Answer
The answer is to check Windows Disk Management to initialize and format the new drive. This is correct because a SATA SSD not detected after installation often appears in Disk Management even if it is invisible in File Explorer, as the drive simply lacks a partition and file system. The technician has already verified physical connections and avoided the bandwidth-sharing trap—the M.2 slot only disables SATA port 5, but the new drive is on port 3, so the hardware is fine. On the CompTIA A+ Core 1 220-1101 exam, this scenario tests your ability to distinguish between hardware failure and software configuration issues; a common trap is assuming a missing drive means a dead component or BIOS setting. Remember the “three D’s” of troubleshooting: Disk Management, Driver, and Diskpart—always check Disk Management first for any unallocated space.
⚠ Common exam trap
It's easy for candidates to assume a detection issue must be a hardware conflict or faulty cable, when in fact the drive may simply need to be initialized and formatted in Windows Disk Management, a common oversight for new drives.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check Windows Disk Management to initialize and format the new drive.
The new SATA SSD is not detected in Windows, but the technician has already verified the cable is secure and the drive has power. Since the drive is connected to SATA port 3, which does not share bandwidth with the M.2 slot (only SATA port 5 does), the issue is likely that the drive is simply not initialized or formatted. The next logical step is to check Windows Disk Management (diskmgmt.msc) to see if the drive appears there and needs to be brought online, initialized, or formatted.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Move the SATA SSD to SATA port 5 to avoid potential bandwidth conflicts.
Why it's wrong here
Since the M.2 slot shares bandwidth with SATA port 5, using that port would likely cause the conflict and disable the M.2 drive or the SATA port. The technician should use a port that is not shared.
When this WOULD be correct
If the technician had connected the SATA SSD to SATA port 5 (the shared port) and the M.2 SSD was using the shared bandwidth, moving the SATA SSD to a non-shared port (e.g., port 3) would resolve the detection issue.
- ✓
Check Windows Disk Management to initialize and format the new drive.
Why this is correct
The M.2 slot shares bandwidth with SATA port 5, not port 3, so the drive is electrically connected and detected at the firmware level. A new, uninitialised disk appears in Disk Management but not File Explorer, so initialising and formatting it makes it usable.
- ✗
Disable the M.2 SSD in the BIOS to free up bandwidth for the SATA port.
Why it's wrong here
Disabling the M.2 drive would defeat the purpose of having it. The issue is not a bandwidth conflict because the M.2 is in the primary slot and the SATA drive is on a non-shared port.
When this WOULD be correct
This option would be correct if the new SATA SSD were connected to SATA port 5 (the shared port) and the M.2 SSD was causing the SATA port to be disabled. Disabling the M.2 SSD in BIOS would free up bandwidth for the SATA port.
- ✗
Replace the SATA cable with a known-good cable.
Why it's wrong here
The M.2 slot shares bandwidth with SATA port 5, not port 3, so the drive should already be detected; the cable is verified secure, making replacement pointless. It tempts because a faulty cable is a common cause of undetected drives, but the stem has already eliminated that possibility.
When this WOULD be correct
When a new SATA drive is not detected and the technician has not yet checked the cable integrity, or if the drive intermittently disconnects, replacing the SATA cable with a known-good cable would be a valid next step.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓Check Windows Disk Management to initialize and format the new drive.Correct answer▾
Why this is correct
The M.2 slot shares bandwidth with SATA port 5, not port 3, so the drive is electrically connected and detected at the firmware level. A new, uninitialised disk appears in Disk Management but not File Explorer, so initialising and formatting it makes it usable.
✗Move the SATA SSD to SATA port 5 to avoid potential bandwidth conflicts.Wrong answer — click to see why▾
Why this is wrong here
The technician connected the drive to SATA port 3, which does not share bandwidth with the M.2 slot (only port 5 does). Thus, there is no bandwidth conflict, and moving the drive to port 5 would not resolve the detection issue.
★ When this WOULD be the correct answer
If the technician had connected the SATA SSD to SATA port 5 (the shared port) and the M.2 SSD was using the shared bandwidth, moving the SATA SSD to a non-shared port (e.g., port 3) would resolve the detection issue.
Why candidates choose this
Candidates may assume that any SATA port could be affected by M.2 bandwidth sharing, or they might misread the manual and think port 3 is shared, leading them to suggest moving the drive to a different port.
✗Disable the M.2 SSD in the BIOS to free up bandwidth for the SATA port.Wrong answer — click to see why▾
Why this is wrong here
Disabling the M.2 SSD is unnecessary because the new SATA SSD is connected to port 3, which does not share bandwidth with the M.2 slot (only port 5 does). The issue is likely that the drive is not initialized in Windows, not a bandwidth conflict.
★ When this WOULD be the correct answer
This option would be correct if the new SATA SSD were connected to SATA port 5 (the shared port) and the M.2 SSD was causing the SATA port to be disabled. Disabling the M.2 SSD in BIOS would free up bandwidth for the SATA port.
Why candidates choose this
Candidates may assume any SATA port conflict exists because the manual mentions bandwidth sharing, leading them to think disabling the M.2 drive is a quick fix, without verifying the actual port used or checking Disk Management first.
✗Replace the SATA cable with a known-good cable.Wrong answer — click to see why▾
Why this is wrong here
The technician already verified the SATA cable is secure and the drive has power, and the drive is connected to a non-shared port (SATA port 3), so a faulty cable is unlikely to be the cause.
★ When this WOULD be the correct answer
When a new SATA drive is not detected and the technician has not yet checked the cable integrity, or if the drive intermittently disconnects, replacing the SATA cable with a known-good cable would be a valid next step.
Why candidates choose this
Candidates may think that a faulty cable is a common cause of drive detection issues, and they might overlook that the problem is more likely due to the drive not being initialized in Windows.
Analysis generated from the official 220-1101blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every 220-1101 question from scratch — 896 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on 220-1101
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A technician installs a new M.2 NVMe SSD into an appropriate M.2 slot on a desktop motherboard. After booting the system, the BIOS does not detect the SSD. The SSD is known to work in another computer. The technician has verified the SSD is fully inserted and secured with the mounting screw. Which of the following is the MOST likely cause?
medium- A.The M.2 slot is disabled in the BIOS settings.
- ✓ B.A SATA port that shares bandwidth with the M.2 slot has a drive connected, causing the M.2 slot to be disabled.
- C.The power supply does not provide enough wattage for the NVMe SSD.
- D.The CPU does not support NVMe drives.
Why B: The most likely cause is that a SATA port sharing bandwidth with the M.2 slot has a drive connected, which disables the M.2 slot. Many desktop motherboards share PCIe lanes between specific SATA ports and the M.2 slot; when a SATA device is connected to the shared port, the motherboard firmware automatically disables the M.2 slot to prevent resource conflicts. Since the SSD works in another computer and is properly seated, the issue is a configuration conflict rather than a hardware failure.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1101 exam.