Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
The disk not appearing in the BIOS at all and not appearing in the Windows installation are different issues. Physical connection, M.2 SATA/NVMe compatibility, shared ports, RAID/AHCI/VMD mode, storage driver, and disk health should be checked separately.
Turkey (Turkish)
Germany (German)
Worldwide (English)
No storage device detected
NVMe Configuration: Not Present
We couldn't find any drives
Load driver to show hardwareThe disk not appearing in the BIOS at all and not appearing in the Windows installation are different issues. Physical connection, M.2 SATA/NVMe compatibility, shared ports, RAID/AHCI/VMD mode, storage driver, and disk health should be checked separately.
Do not follow the general internet recipe without recording the brand, exact model, motherboard revision and BIOS version.
Store Boot Mode, disk controller, Secure Boot, TPM, XMP and virtualization status with photos or reports.
Don't do risky firmware without a BitLocker key, Windows recovery USB, stable power and a fallback plan.
Do not change more than one BIOS setting at the same time; Verify Windows and hardware status after each step.
Do not initialize, clean, or format a disk that contains data.
Meaning: Firmware is not recognizing any storage device.
Possible cause: Physical connection, controller or disk failure.
Meaning: M.2 NVMe disk not detected in the slot.
Possible cause: Incorrect slot, connection, BIOS, or disk issue.
Meaning: BIOS sees the disk but installation does not.
Possible cause: Intel RST/VMD/RAID driver missing.
Meaning: The slot may only support NVMe or SATA alone.
Possible cause: M.2 protocol incompatibility.
Meaning: M.2 usage shares a specific SATA port.
Possible cause: Motherboard lane sharing
Meaning: The Windows controller driver is not ready for the new mode.
Possible cause: BIOS disk mode changed.
Meaning: Empty disk does not contain a bootable operating system.
Possible cause: Normal behavior.
Meaning: Connection, temperature, power, or disk failure may occur.
Possible cause: Loose cable/slot or firmware.
No records matching this expression were found.
Get-Disk | Format-Table Number,FriendlyName,SerialNumber,BusType,PartitionStyle,OperationalStatus,HealthStatus,Size -AutoSizeDisks seen by Windows are shown.
Get-PhysicalDisk | Format-Table FriendlyName,SerialNumber,MediaType,BusType,HealthStatus,OperationalStatus,Size -AutoSizeDisplays physical disk health and connection type.
Get-PnpDevice -Class DiskDrive,SCSIAdapter,HDC | Format-Table Status,Class,FriendlyName,InstanceId -AutoSizeLists disk and storage controller devices.
Get-CimInstance Win32_SCSIController | Format-Table Name,Manufacturer,Status,DeviceID -AutoSizeDisplays RST/VMD/RAID included storage controllers.
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2,3} -MaxEvents 300 | Where-Object {$_.ProviderName -match 'disk|stor|nvme|iaStor'} | Select-Object TimeCreated,ProviderName,Id,Message | Format-ListShows recent errors related to disk and storage.
Get-CimInstance Win32_BaseBoard | Format-List Manufacturer,Product,Version; Get-CimInstance Win32_BIOS | Format-List SMBIOSBIOSVersion,ReleaseDateDisplays the model information for slot compatibility and BIOS research.
Check the cable, power, M.2 protocol, and shared SATA ports.
On modern Intel laptops, the installation screen may not see the disk without the VMD driver.
BIOS/UEFI diagnostic disk test separates hardware from software issues beforehand.
The Salt BIOS setting usually does not delete files; however, the boot mode, disk controller, TPM Clear or incorrect installation procedures may affect Windows access and encryption keys.
Secure Boot, TPM, BIOS updates, and some firmware changes can change the security measurement and Windows may request a recovery key at startup.
Manufacturers may offer the same feature under different menu names and locations. The exact step must be verified based on the device's full model and BIOS version.
Normal firmware menu usage usually does not void the warranty; opening the case, physical CMOS intervention, or unauthorized firmware operation may affect the manufacturer's conditions.
No. It is more correct to not add unnecessary risk to a working system unless there is a security, hardware compatibility, or manufacturer's stated issue.
Universal password or bypass should not be used. Manufacturer support or the company's IT manager should be used with device ownership proof.
No. Firmware recovery, physical CMOS, disk failure, and data recovery operations require model guide and, if necessary, authorized service.
We safely examine Windows 10/11, Secure Boot, TPM, SSD detection, USB boot and firmware recovery problems according to device model.