- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Body:
Hi everyone,
I am completely stuck trying to recover a laptop after a Windows 11 update broke the storage driver layer. I have been trying to perform a clean Windows 11 installation from a bootable USB, but I am hitting the infamous "No drives found" screen because of the Intel VMD controller block.
Here are my exact system specs from the BIOS:
* Laptop: HP Laptop 15-dw3xxx (System Board ID: 881D)
* Processor: Intel 11th Gen (Tiger Lake)
* Storage Controller in BIOS: Intel(R) RST 18.1.2.5596 RST VMD Driver
* Physical Drive: SATA 0.0, ST1000LM035-1RK172 (931.5 GB Seagate)
The Problem:
Windows Setup requires loose driver files (.inf, .sys, .cat) to load the storage controller during the installation process. However, the official Intel download pages no longer host the old F6flpy zip packages for the 18.1.2 / 18.x VMD generation. They only offer the single SetupRST.exe installer, which the Windows installation environment cannot open or extract on its own.
I have tried extracting newer versions of SetupRST.exe using command lines on a working PC, but the setup screen still refuses to detect the drive.
My Request:
Does anyone have a direct link or a backup copy of the pre-extracted Intel RST Version 18.1.2 F6 Floppy VMD drivers (containing iaStorVD.inf) that will match this Tiger Lake motherboard architecture? Any help or alternative repository links would be greatly appreciated. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And, @Shiquan_Su , as a helpful moderator, could you be kind enough to help point the OP to the proper resource?
Doc (not an Intel employee or contractor)
[If AI is so good, why do users still visit these forums?]
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This forum is for Intel Fortran Compiler (IFX) discussion. The topic of the Intel VMD driver falls outside of the scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And, @Shiquan_Su , as a helpful moderator, could you be kind enough to help point the OP to the proper resource?
Doc (not an Intel employee or contractor)
[If AI is so good, why do users still visit these forums?]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@AlHill — to answer the question in your signature: Users visit these forums to get told they are 'out of scope' by a moderator, but they use AI to actually fix their laptops. My AI assistant got me safely to my desktop 20 minutes ago while I was waiting for a reply here. Score one for the bots!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@X5 I am generally against these bots. But, in the case of Intel "support", the bots are providing far better answers lately.
Doc (not an Intel employee or contractor)
[Success breeds complacency. Complacency breeds failure. (Andy Grove)]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One of the proper resources may start from asking AI, such as Claude: Practical takeaways for the forum reply
With the help of Claude, I come up with the following suggestions:
- The user's framing ("need pre-extracted F6 zip") is solvable —
SetupRST.exe -extractdrivers <folder>(or 7-Zip the EXE) yields theiaStorVD.infset. They said they tried this and Setup still didn't see the drive, which suggests a different root cause. - Title says "Windows BitLocked After Update" — that's the real issue. Even with the correct F6 driver loaded, a BitLocker-encrypted drive shows up but is unreadable without the recovery key (Microsoft account → aka.ms/myrecoverykey, or HP Support Assistant). No F6 driver swap fixes that.
- Cleanest path on HP 15-dw3xxx: enter BIOS (F10), disable VMD under Storage/System Configuration so the SATA controller exposes the drive in AHCI mode — Windows Setup will see it without any F6 load. Caveat: if the original install was BitLocker-on, the recovery key will still be required at first boot.
Would you please try and see if they help? Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I explicitly pointed out that my source is from AI, because that knowledge is out of my expertise, and I can not endorse those suggestions.
If you can solve your issues with those AI suggestions or other sources, please feel free to post here. I can mark that as an accepted solution.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page