Understanding the Storage Controller Dependency
The Lenovo IdeaPad 515ITL05 utilizes modern storage interfaces that differ significantly from older SATA-based systems. In many configurations, the system BIOS sets the storage mode to RAID or Intel RST (Rapid Storage Technology) rather than AHCI. When WinPE boots without the specific driver for this controller, it cannot see any attached block devices. Consequently, tools like DISM or diskpart will report that no valid drives are available, even though the physical hardware is functioning correctly. This issue is distinct from general network connectivity problems or file system corruption. It is a fundamental driver absence at the kernel level of the pre-boot environment. Without the correct INF files and accompanying binaries, the operating system setup or deployment agent remains blind to the target volume. This is a common scenario when using generic Microsoft WinPE images that only contain basic mass storage drivers.Preparing the Driver Files
Before modifying your WinPE image, you need to obtain the correct storage drivers for your specific hardware model. You should download these drivers from the official Lenovo Support website for the IdeaPad 515ITL05. Look for the "Storage" or "Chipset" category within the driver list. The relevant driver is often labeled as Intel Rapid Storage Technology Driver or a similar NVMe controller driver compatible with your processor generation. Extract the downloaded driver package to a local folder on your development machine. Inside the extracted directory, locate the .inf file associated with the storage controller. You may also find .sys files and catalog files (.cat) in subdirectories. Keep track of the path to this folder, as you will need to reference it during the driver injection process. Ensure that the driver version matches the architecture of your WinPE image, which is typically 64-bit (amd64).Injecting Drivers into WinPE
To add the storage driver to your WinPE image, use the Deployment Image Servicing and Management tool, commonly known as DISM. Open an elevated command prompt and navigate to the directory containing your WinPE ISO or the mounted WIM file. First, identify the index number of the WinPE image if your WIM contains multiple entries, usually by runningdism /Get-WimInfo /WimFile:winpe.wim.
Then, execute the following command to add the driver to the offline image:
dism /Image:C:\WinPE_amd64\mount /Add-Driver:"C:\Path\To\Driver\driver.inf"/Cleanup-Image and /Unmount flags to ensure all modifications are saved to the final ISO file.
Creating the Bootable Media
Once the drivers are successfully injected, you can create the bootable USB drive using the MakeWinPEMedia script provided with the Windows ADK. Run the command:MakeWinPEMedia /ISO C:\WinPE_amd64 C:\WinPE_amd64\winpe.isoVerifying Drive Accessibility
After booting into the modified WinPE, open a command prompt and rundiskpart. Type list disk to verify that your internal NVM drive appears in the list. If it does, type select disk X (where X is the disk number) followed by detail disk to confirm the capacity and model match your expectations. You can then exit diskpart and use other tools to interact with the drive.
If the drive still does not appear, double-check that the driver was added to the correct image index. You can verify the installed drivers by running dism /Image:C:\WinPE_amd64\mount /Get-Drivers after remounting the image. This will list all third-party drivers present in the offline environment, confirming whether your storage driver is included.
For users who frequently manage multiple deployment environments, combining different WinPE tools can streamline workflows. You might find it useful to integrate partition management utilities directly into your custom image. For more information on managing multiple pre-OS tools, see Combine Multiple WinPE Pre-OS Bootable USBs with EaseUS Partition Manager.
Frequently Asked Questions
Why does my WinPE see the drive but not the partitions?
This usually indicates a file system driver issue rather than a storage controller problem. Ensure that the NTFS or exFAT drivers are present in your WinPE image, as some minimal builds exclude them. You may need to inject the necessary file system filters using DISM.
Can I use AHCI mode instead of RAID to fix this?
Changing the BIOS storage mode from RAID to AHCI can make the drive visible without extra drivers, but this alters the configuration for the installed Windows OS. If you switch modes, the existing Windows installation may fail to boot due to missing AHCI drivers. It is safer to inject drivers into WinPE than to change BIOS settings permanently.
What if the driver injection fails with an error code?
Error codes often indicate that the driver is incompatible with the current Windows version or architecture. Verify that the driver is built for Windows 10 or 11 amd64 architecture. Additionally, check if the driver requires a specific catalog file (.cat) to be placed in the same directory as the .inf file.
Is there a way to automate driver injection for multiple laptops?
Yes, you can create a script that loops through a directory of drivers and adds them to the WinPE image sequentially. Use a batch file or PowerShell script to iterate through each .inf file and call DISM for each one, ensuring consistent driver coverage across different hardware models.
Does this solution work for non-Lenovo devices?
The principle applies to most modern laptops with NVMe or RAID-configured SSDs. However, the specific driver files will vary depending on the manufacturer and chipset. Always source drivers from the official vendor support page for the exact model you are servicing.