@Fernando I have one of the laptops on hand atm, here are the model numbers and info for it:
HP 15t-dw300 ProdID: 1A3Y4AV
SSD: Samsung MZVLQ256HAJD-000H1
Bios files: 15t-dw300_BIOS.zip - Google Drive
@GraphicHealer
I asked you for
a) the Intel RST driver version, which detected your NVMe SSD and
b) the BIOS file, which contains the NVMe EFI module (your attachment contains a lot of not matching files).
If you want help, you should post the requested information.
That is the only bios files I could find for that laptop.
Please give me some information about the manufacturer/model of the NVMe SSD
I responded with exactly what you asked for.
The driver version I used is the:
Generic 64bit Intel RST AHCI+RAID driver v17.11.0.1000 for Win10-11 x64 mod+signed by Fernando
When the integration last allowed me to.
I am now manually loading the official HP drivers I extracted from the EXE installer.
https://ftp.hp.com/pub/softpaq/sp139001-139500/sp139242.exe
Dude. I replied as best as I could. I gave you the model, and I gave you as pure of a bios as I could. Those are the bios files that the official HP bios installer for the 15t-dw300 will give you if you request them to be put in a folder instead of installed to the mainboard. I don’t know how BIOS’s work. I just know how to install them.
- It doesn’t make sense to integrate a modded driver into the Image of a modern Windows OS, because the OS Setup only accepts WHQL certified third party storage drivers. So I doubt, that the “Generic 64bit Intel RST AHCI+RAID driver v17.11.0.1000 for Win10-11 x64 mod+signed by Fernando” has been accepted by the Win10 or Win11 Setup and its Device Management.
- Your attached HP driverpack contains the Intel RST VMD driver v18.6.1.1016 WHQL, which doesn’t support any Intel SATA Controller running in AHCI or RAID mode.
By the way - there are newer and better WHQL certified Intel AHCI/RAID drivers availabe, which belong to the RST v17 and v18 platform. You can find them >here<.
In response to #1:
I was able at some point to integrate non-WHQL drivers into the ISO, I don’t know if it was a bug or something wrong with my PC, but a windows update fixed it, and now I no longer can integrate those drivers.
I at first thought the problem was I couldn’t integrate those non-WHQL drivers.
Now I know there is no point in doing that.
Solved that part.
The issue now is why the NVME drive doesn’t show up in the first place.
In response to #2:
Of course it’s not a SATA driver. These laptops don’t even have SATA ports. They are NVME only. The issue is windows doesn’t see the NVME drives for some odd reason. That VMD driver from the HP website is what I load in the setup screen to be able to see the drive and install windows.
Side note:
I have also looked at the included drivers on the NTLite components page, and I do not see any VMD drivers. I only se the SATA Intel RST drivers, not any NVME drivers. Could that be why it’s not showing up? Or am I just misreading that page?
@GraphicHealer
If you want or have to integrate an NVMe driver, I recommend to take the “Generic 64bit Phison NVMe driver v1.5.0.0 WHQL for Win8-10 x64”. You can find the download link within the second post of >this< thread.
I do not really understand why you have tried all the time to integrate different and partly extremely old Intel MSM and RST drivers, who mainly support only Intel’s SATA AHC and RAID Controllers, but no NVMe Controllers. Only the latest Intel RST drivers from the v16 platform are able to detect and work with NVMe Controllers, but they support only NVMe SSDs and Controllers, which were manufactured by Intel (or its successor Solidigm SK-Hynix).
Good luck!
Ahhhh ok I misunderstood the RST driver. I thought RST was NVME only. I didn’t realize it worked with older port tech. That is why I was using the older driver, as from what I read, it was the best all-round RST driver, but I guess that wasn’t talking about NVME.
friends, it doesn’t matter the version to windows iso driverpack solution online how can we save it to windows iso directory on usb
@eskeenginbey
Welcome to the Win-RAID Forum!
Since the driver integration into the ISO file is rather similar for all Windows Images from Win7 up, I have moved your request into this already existing thread.
Please read the Guide, which is within the first post. If you should have any additional question regarding this topic, post it into this thread.
Enjoy the Forum!
Dieter (alias Fernando)
Hi,
I intend to use Windows 10 Enterprise LTSC 2021 x64 for multiple scenarios not knowing what hardware I might encounter.
-
Is it really necessary to integrate mass storage drivers to boot.wim index 2 and install.wim?
-
How about (W)LAN drivers to install.wim only?
-
Do I need to integrate any other driver too?
I have no problem or inconvenient installing any other driver post-installation.
I just don’t want having issues installing Windows on any type of storage device in a PC or laptop.
Also I don’t want to have connectivity issues to the network due to a missing driver right after Windows installation.
TIA
@BetaTesta
Welcome to the Win-Raid Forum!
This is only necessary, if the Storage Controller of the target disk drive is not supported by the original OS.
The integration of a WLAN driver into the boot.wim is not required (unless you want to use the Wake-On-Lan feature from scratch).
It depends on the age and the specific BIOS and hardware configuration of the target PC/notebook
The most important input and output devices should work to be able to complete the OS installation.
1 Like
Thank you.
Then for the scenario I mentioned before, I’d need to install a pack or packs of storage drivers which cover most manufacturers, right?
Is there such a driver pack(s) here in the forum?
Then I assume is safe to add WLAN drivers to install.wim.
Is there such a driver pack(s) here to cover most scenarios at once?
TIA
No.
By the way - the more storage drivers you integrate into the ISO, the higher is the risk of getting a 0x0000007b BSOD during the OS installation. A driver, which matches a specific Storage Controller, may be completely wrong for another.
1 Like
But that’s what Windows’ setup program is able to do, isn’t it?
I mean to read a controller HwID and pick the right driver from its drivers store. No?
A 100% matching “textmode” driver is required within the very first part of the OS installation (to detect and to get access to the target disk drive). At that time the Windows Device Management is not yet fully available.
1 Like
Fine.
Then integrating a pack of ‘textmode’ storage controller drivers not found in current install.wim could solve my hypothetical scenario. No?
If the answer is no then I don’t quite understand how this setup thing works because I assume an install.wim file has a lot of textmode storage controller drivers for many different devices originally integrated by MS, and there are no BSODs.
I see no damage by integrating a few newer more…
@BetaTesta
You can do what you want. I just wanted to let you know the risks of an “All-in-One-ISO”.
By the way - the content of the install.wim is not available for the Setup before the first reboot (after having completed the installation).
1 Like
Ok, I understand. Thank you.
Yes I know. I think you are mentioning this believing I want network connection during installation. No I do not want to. I want network connection available via Ethernet or WiFi right after entering into the desktop for the first time.
Lastlyl, could you point me out where the textmode storage drivers are?
And where the textmode WLAN drivers are?
TIA
One more question.
Every threes months MS refreshes Windows isos but LTSC isos.
Do you know if those refreshed isos include new integrated drivers from for increased compatibility specially for mass storage controllers?
All “textmode” drivers are stored within the boot.wim and within the install.wim of the ISO.
Usually Microsoft updates only drivers, which were manufactured by themself or they do it on demand of the chipset manufacturer. MS doesn’t care about the date of third party drivers, which are within their ISO.
1 Like