Intel RST Driver Dell 2 in 1 12th generation intel


Author
Message
db1
db1
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 6
I wanted to post this here as it may help others in future. I have a new Dell XPS 13 9315 2-in-1. The HDD is soldered to the motherboard and it uses a relatively new intel controller. I believe this issue will apply to many computers using 11th and 12th generation Intel chipsets. I had a lot of trouble getting it to work in the WINPE recovery mode. I tried loading the drivers when creating the bootable media via the macrium software but it didn't work.

My solution - although not so elegant was:
1. Create your recovery media via Macrium
2. Copy the intel storage driver and devcon executable to a usb drive
3. Boot the Macrium recovery media
4. Click the button near the bottom of the screen to open a command prompt window
5. Navigate to the directory with the storage driver and run pnputil -a *.inf it should say it successfully loaded the driver
6. Navigate to the directory with devcon
7. Run devcon find *
8. Get the hardware ID of the storage controller. Mine was near the bottom of the list.
9. Run devcon disable <HWID of controller>
10. Run devcon enable <HWID of controller>
Your disk drive should now be available.

To test the disk is available run
diskpart
show disk
You should see your disk listed
Run exit to exit out of diskpace
Close the command prompt window and continue your recovery.

Download the 'Intel Rapid Storage Technology Driver and Application' for your machine from the dell website. 
I used https://dl.dell.com/FOLDER08281538M/6/Intel-Rapid-Storage-Technology-Driver-and-Application_MK0Y4_WIN64_19.2.1.1006_A02_04.EXE
Or go to the Dell Support page and look for storage drivers for your machine.

Download Devcon
Download 787bee96dbd26371076b37b13c405890.cab, extract the file filbad6e2cce5ebc45a401e19c613d0a28f and rename it to devcon.exe 
Link to cab: https://download.microsoft.com/download/1/4/0/140EBDB7-F631-4191-9DC0-31C8ECB8A11F/wdk/Installers/787bee96dbd26371076b37b13c405890.cab
Source of information in case you need a different version:
https://superuser.com/questions/1002950/quick-method-to-install-devcon-exe

Download Dell WinPE drivers
https://www.dell.com/support/kbdoc/en-au/000108642/winpe-10-driver-packhttps://www.dell.com/support/kbdoc/en-au/000108642/winpe-10-driver-pack
This is a larger set of drivers in case you need a different driver for your machine.

I spent a few hours sorting this out. Hope if helps. Good luck with your recovery.
Danskeman
Danskeman
Expert
Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)Expert (743 reputation)
Group: Forum Members
Posts: 520, Visits: 4.2K
I had an issue with a particular driver not being seen in winpe mode so I could not access second hard drive in a dvd enclosure replacing dvd drive.

I too had issues getting Reflect to see it.

I injected the driver into boot.wim usimg simple dism command and it worked fine.

Try this - just google the dism commands - loads tell you how to export, and inject.

On pc in normal windows mode, export the Intel driver, and it should create a .inf file.
Then inject .inf file into boot.wim

Winpe should see the driver then.


db1
db1
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 6
I think there are two issues going on.
1. I'm unsure if Macrium injects the driver into the WIM properly
2. Apparently intel used the same hardware ID for multiple storage controllers. As such, it can get confused about which driver to load.

In any case, I just wanted to share my solution with others. I only needed to do a re-image once and don't intend to do it again any time soon.


GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search