@Fernando:
I did install your driver v15.9.3.1026 and forced DEV_22A3 to Intel 300 Series because it was only standard AHCI driver. But this computer is cheap and has the worst transfer rate. I think I'll keep the SSD because it does boot a little bit faster and random access is fast too even though it only has a limit of 50MB/s instead of the SSD maximum 540MB/s.

EDIT by Fernando: Unneeded fully quoted post replaced by directly addressing (to save space)

Hi and thanks for the help so far, I sort of noticed something when installing your mod'ed drivers on windows 7 first when i right click on the device, it says its digitally signed. yet then i click on driver details and in there the 2 files are not digitally signed!
yet in windows windows 10 there is 1 file and its digitally signed?

Hello, Fernando

Can you provide a v16.5.1.1030 [mod]?
According to my previous experience (a few monthes ago, v16.3.0.1007 [mod]) the rescent 16.x Drivers (for a new target platforms) work well on older systems also (Z77, etc).
Moreover, I remember about positive feedback from some other users, which have older chipsets too.

Zitat von Fernando im Beitrag #965

---

mod+signed 64bit Intel RST AHCI+RAID drivers v16.5.1.1030 dated 06/12/2018, modified and digitally signed by me at 07/28/2018

---

Yes. Z77. ASUS P8Z77-V DELUXE

I've tried forced installation using "Have Disk..." option and receive the message about "fake or bad hash of the driver pack" (translated to English by me as I'm understand this).
Then I'm immediately revert my drivers back to 16.3 to avoid possible issues during the next boot.

Zitat

---

why is it so important for you to get the latest Intel RST driver installed, which seems not been designed by Intel for your system

---

Several reasons:
- The rescent drivers works well on old systems.
- The rescent drivers are slightly faster, according to (not wide but) existing feedback
- Theoretically, a new drivers may consist fixes for reduced speed in case of Spectre patches (my disk system expecting such issues)
- Why not?

Zitat von Fernando im Beitrag #968

---

How did you unzip the driverpack?

---

Zitat

---

I have never seen such message.

---

I'm too. But this message have appeared at the standard context, at the standard screen we can see after any driver installation (successful or not).
This was the same screen such "Driver was updated successfully" or "There is no need to update the driver" or "The installation of the driver was unsuccessful, because...", etc.

May be this message screen have been changed a bit in case of some new M$ security patches or so...

@Fernando
It's ok. But it's not good news for us. For modding, yeah?
Having a correctly prepeared sert it's not enough. We need now the right hashes also. As I can quess...

Corps pushing to make things harder, less flexible, more stupid and more buggy from the box. That's touches all proprietary IT-spheres.

@Fernando
And don't forget an always helpful quck trick for newly modded drivers.
If "Browse..." method works when updating from previous version, then pack should be OK for 99.9%.

@Fernando

Driver works (tested on Win8.1). Thank you very much!

But I'm expecting issues with "Intel RST Software"(Win8.1).
Can such issues appear in case of unneeded Visual C++ Redistributable Packages installations? I have all freshy and ready packs in my system.
Or Visual C++ Redistributable Packages are not relative to "Intel RST Software" at all?

I have to run "RST_x64.msi", right?