Drivers laptop Killer Wireless-AC 1550 & USB 3 - Windows 7 64Bit Helps

Vineet Garg · 22 Feb 2019

Cris,
Thanks for all the information & stuff.
1) DevManView is only good to access a lot of information in few clicks. Its not a real alternative to the traditional Device Manger. Look into the Device Manager for any abnormalities & report.
2) I would mention a little later : how to look into Offline OS Devices/Drivers from within Host/Online OS.
3) I am not telling to make any install from Snappy. But Snappy tells us where to concentrate : The Entries : Driver not installed yet , Not Signed, Device requires driver but not found in DriverPacks & Updated driver available which is also more optimal
4) Install the NET 4.7.2 Frame Work downloaded with Windows Updates Downloader.

Let me know.

Thanks & Regards. ...

EDIT : To avoid any confusion : The DevManView report is very helpful. I always wanted/needed that information. I am going through it & it may take time to suggest further. Till then verify abnormalities in DevManView with the traditional Device Manager. That is all.

Cris85 · 22 Feb 2019

Hi Vineet Garg,

I installed NET 4.7.2 Frame Work and restarted the system. After, I went to Device Manger from Windows 7 and I take for you the screenshot. Here after, you will find attached the picture report.

Thank you soooo much for your help.

Cris

Cris85 · 22 Feb 2019

Good Morning Vineet Garg,

I was thinking if for the Killer Wireless-AC 1550 Wireless Network Adapter (9260NGW) drivers , could we try the own Intel 9260NGW drivers (as it's also "coded" by DevManView software which lists the hardware ID in brackets)? Since, the Rivet Networks company that produces Killer Lan / Wireless has been acquired by intel long time ago, and Intel continues to keep this company in order not to lose the gamers clients and cover the Intel hardware under another name like Killer Wireless/ Lan, but in fact, the Killer (R) Wireless-AC 1550 hardware card is an Intel 9260NGW.

Example Rivet Networks and Intel, are like Dell and Alienware or Acer and Predator

Just a rebranding!!!

What do you think about?

I have this doubt, because when I extractd the wireless drivers from the original Killer Wireless packaging file exe, there are the drivers for Windows 7 but not in all the subfolders, I don't remember which one exactly but I remember for sure that in two of these subfolders the Windows 7 drivers was missing, and inside was only for windows 10 (so, I didn't find in these two subfolders the drivers for both OS Windows 7 and 10 as it was for the rest of the Subfolders; but in these two subfolders I have found only for windows 10).

I attached here the PDF hardware specs of the Intel 9260NGW (Killer Wireless-AC 1550).

Cris

Vineet Garg · 23 Feb 2019

Hi Cris,
Greets,
Great! I am getting jealous of you

Honestly, I did not think in that direction & I was thinking about how to mod the wireless driver. I am surprised why others did not think in that direction but i know one can make all the difference!
Today, I had very little time & would go thoroughly tomorrow but it sounds interesting!
If you want to use any driver, please share with me & i would be able to tell you whether it supports your Device & OS.

Thanks & Regards. ...

((( Just to mention :
a) You shared two USB drivers with me & the Win-RAID driver supports your device which we added to the ISO.
b) All the three NVMe disks use exactly same driver so only one driver would support all the three.
c) If an ISO is more than 4gb of size, Rufus still support UEFI+GPT for it. It uses NTFS to write that ISO on the pen drive. Don't confuse NTFS because it is only for the pen drive & not the installation. I mean to say there will be no problems at all.
d) I think you missed the tip to go into the Device Manager & From the Menu bar, click VIEW & choose Devices by connection. You would find your SATA Harddisk on SATA AHCI Controller. You would also be able to make general difference between SATA & NVMe.
e) If you are interested, I can help you know reading driver files to know about the supported Devices & OS. I see a lot of possibilities in you. )))

Cris85 · 25 Feb 2019

Hi Vineet Garg,

are you kidding, if you become too jealous of me it means that you are taking me too seriously

.
I like always to learn; therefore, I play a lot with computers, hardwares and softwares because I like it, but I have never deepened the drivers world for the hardwares.

I just try to give you a hand for what I can do.

a) You shared two USB drivers with me & the Win-RAID driver supports your device which we added to the ISO.

CRIS: Yes, I understood what you told me; we are in the same page.

b) All the three NVMe disks use exactly same driver so only one driver would support all the three.

CRIS: If you mean about the story of the NVMe driver that gives me the problems during the Windows 7 installation (in copy section and stuck on 0%), honestly, I do not know which driver solve me this problem, I understand that we have installed the NVMe drivers of Windows 7 but do not work with the internal NVMe MSI from Samsung. I have tried many drivers in the past and one by one (so many installation test windows 7), even those MOD from WIN-RAID and the latest Samsung original exactly for the model SAMSUNG MZVLB256, no one worked to delete that installation problem by pop-up error. From what I understand, I think it's some combination of some drivers not to give me that problem of copyng files 0% inside the NVMe, because if you remember that problem disappears only if I inject all the drivers that I have downloaded in the past. So, it's not enough the exactly driver for the NVMe model, but it should be some other driver combination for some controller chipset that together with the original Samsung driver makes the installation work without problems.

c) If an ISO is more than 4gb of size, Rufus still support UEFI+GPT for it. It uses NTFS to write that ISO on the pen drive. Don't confuse NTFS because it is only for the pen drive & not the installation. I mean to say there will be no problems at all.

CRIS: Yes, I know, but the problem is that if the USB Pen drive it is prepared in NTFS it is not possible to start the installation of Windows 7 from the USB Pen under UEFI boot, because the USB Pen drive must to be prepared only in FAT32 to run the boot/installation. But as you know, the FAT32 has the 4GB limit for an entire file (but no worries about, because anyway we don't overpass 4GB).

d) I think you missed the tip to go into the Device Manager & From the Menu bar, click VIEW & choose Devices by connection. You would find your SATA Harddisk on SATA AHCI Controller. You would also be able to make general difference between SATA & NVMe.

CRIS: Yes, I know the differences between SATA and NVMe in details, thanks anyway. Or are you asking me to get you a screenshot?

e) If you are interested, I can help you know reading driver files to know about the supported Devices & OS. I see a lot of possibilities in you. )))

CRIS: I could try, it is something that always was interesting to me to learn. Thank you very much.

* In a Russian forum, I found some people trying to unlock the famous A36D hardware for the USB 3.1, and one user replied to another one that in the latest Intel drivers he need just add the lines inside the “.inf” file (I think). Is it really that simple? Because, to me sounds very strange. I post you the translated link:
Google Translate

Thank you,
Cris

Vineet Garg · 02 Mar 2019

Hi Cris,
Greets,
Please continue same patience. I got some time today so i tried to mod/make a wireless driver:

1.The modded & unsigned driver for Killer Wireless AC 1550 for win7 SP1 x64.
Hardware ID. PCI\VEN_8086&DEV_2526&SUBSYS_15501A56
( Added Support to 'Win7 Image Updater'/ Intel Wireless Driver/Netwsw04.INF )
Killer Wireless AC 1550 Driver for Win7.zip - Google Drive

(1) Make a System Restore Point.
(2) First try with : 'DPInst64.exe' & observe for some time.
(3) If failed : make System Restore, try with : 'iprodifx.exe' & observe for some time.

2. Very less hopes about 'Intel USB 3.1 extensible Host Controller'
( PCI\VEN_8086&DEV_A36D&SUBSYS_121C1462&REV_10 )

I searched all the internet but no use!

Admin Sir from Win-RAID forum has tried to mod but failed. He says the modification of .inf file is not enough & a real driver for win7 is required from Intel. Though he has some drivers to offer for testing!

In some cases, the modded driver got installed but did not work at all.

I would try myself to make it sure. I would like to try USB 3.1 controller downgraded as USB 3.0 controller.

3. Probably, your hard ware would not be working at its best. What are the short comings ? We should try those drivers one by one. I would read the drivers & tell you the things one by one.

4. The driver listed on the site has full support for your Samsung Nvme Controllers :
PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00

Now we don't need to use MS Updates for NVMe (2). The Installation problem should end with these drivers. If it doesn't end here, we will add Chipset driver to the ISO.

Site : Forum - Recommended AHCI/RAID and NVMe Drivers

To avoid any confusion direct download link : http://www.smartredirect.de/redir/cl...e-Drivers.html

5. You did not tell about Bluetooth ?

Thanks & Regards. ...

6. Can you provide me .inf driver file for A36D from within Win 10 installation ? Launch DevManView from win10, select the A36D device, explore .inf file from the right click menu. You can use 'Save the file as'. I would compare the file with Win-RAID modded drivers.

((( Just to mention :

(a) In a Russian forum, I found some people trying to unlock the famous A36D hardware for the USB 3.1, and one user replied to another one that in the latest Intel drivers he need just add the lines inside the “.inf” file (I think). Is it really that simple? Because, to me sounds very strange. I post you the translated link: Google Translate
Actually, Driver modding moves around adding support in .inf files as said in the forum but as said earlier : Its not working. A Win 7 supported .sys file is also needed but tries are open!

(b) 'Reading Driver' starts with double clicking the .inf files. It will open them in a text file like look.

Don't try to install the .inf files, you have to just read them.
By default, double clicking .inf files doesn't install them & just open them in a text file look.

Avoid changing the files unknowingly in the reading process!

There we have to look for Hardware IDs to check the support for a particular device.

The second thing to look for is the supported OS :
NTamd64.6.0 refers to win7 64 without SP1. NTamd64.6.1 to Win7 SP1 64,
NTamd64.6.2 to win 8 64, NTamd64.6.3 to win 8.1 64
NTamd64.6.10 & ahead to win 10.

Sometimes only NTamd64 is listed there. It is actually supporting all of them.
)))

Vineet Garg · 06 Mar 2019

Hi,
I read all the drivers & just short listed what is exactly required now :

(a) Chipset driver from product support page is good enough. It is good to first install it with -overall command line switch after OS install.

(b) The dedicated official driver for IMEI ( Intel Management Engine Interface ) does not support your device for win7 but no worries : the Chipset driver (above) gives a driver for that also!

(c) These drivers from official product support page has full support for win7 64 ;
Realtek PCIe Card reader, SteelSeries Keyboard, Synaptics Touchpad
For Optimum use, these drivers should be installed.

(d) Samsung NVMe & USB Thunderbolt drivers : already taken from Win-RAID Forum.
It seems Thunderbolt functionality drivers are available online.
The Win 7 inbox driver seems to work well for the normal HDD.

(e) Realtek HD Audio driver in 'Win7 Image Updater' supports your device & OS. If it does not work so well, we can easily find other good driver online.
It depends upon usage. If you feel something is missing in audio functionality, we would try other drivers.

(f) Good graphic driver is available from NVIDIA itself.

(g) The really missing/challenging drivers are three now: Killer Wireless AC 1550, Killer 1550 Bluetooth driver & intel USB 3.1 xhci controller driver ( A36D )

Let me know.

Thanks & Regards. ...

Before trying any modded driver, make a system restore point at least. In case of failure, uselessness and/or problem(s), immediately restore it to nullify any bad effect(s) on the installed OS. You have got to keep on experimenting so, make sure a good OS is always there!

Cris85 · 09 Mar 2019

Hi Vineet Garg,

I'm back....

In meantime that i try the killer lan drivers, I followed your procedure to read the USB .inf file, and no were there is these words that you listed out:

NTamd64.6.0 refers to win7 64 without SP1. NTamd64.6.1 to Win7 SP1 64,
NTamd64.6.2 to win 8 64, NTamd64.6.3 to win 8.1 64
NTamd64.6.10 & ahead to win 10.

Maybe could be this the problem why cannot be installed the drivers?!

I save it as "Save the file as", you can find attacched the ZIP file below because the Forum does't allow me to attach the file in .inf extension...

Cris

Vineet Garg · 09 Mar 2019

Hi,
Nice to see you back!

Please don't get confused, Its just to mention & churn,I don't expect anything from you out of it!

a) Till i engaged with your issue, I thought .inf is all for drivers but that's not the truth. The other files .sys, .cat , .inf, etc. are also quite important. If one double click & read an .inf file, he would be able to know all the other important driver files.

NTLite works with DISM in the background but is easier to use. As soon as it picks a .inf file, it tells what that driver file is for! All the other needed files are internally pulled from the extracted driver folder but not told!

b) To avoid any problems, I decided to go with minimum drivers & installing the rest drivers only after a successful install.

c) When we talk about the driver mod, it mostly suggests .inf modification.
Seniors said that mod is not working with A36D, 8086. They said that win 7 needs a supported .sys file for the device but why ? I am not satisfied so, i am still hopeful!

d) When I asked Win-RAID Admin Sir to extract & share the driver from Win 10, he shared :

win10 inbox.rar

e) NTamd64 is there in the USB .inf file!
( Its just the beginning my friend!
While trying to find/replace/change/edit something in a large .inf file, the Notepad's Edit tab from the top menu comes handy.
DevManView also mentions the .inf section of the .inf file. It hints what is the section which is being used from the large .inf file for the particular device under that OS.)

What about the modded Killer LAN driver ?

Let me know.

Thanks & Regards. ...

Cris85 · 10 Mar 2019

Hi Vineet Garg,

I'm back, and I got the tests resoults on your drivers for Killer Wireless AC 1550.

Before I replay to all your posts, I would like to tell you the results first, so, the drivers was installed successfully and before reboot the system I went inside "Control Panel---Network and Internet---Network Connections", and the Killer Wireless Lan 1550 appeared!!!

But, unfortunately, the system go in crash after few seconds.... I tried to reboot the system, and doesn't boot anymore and it stuck/loop on the Windows 7 logo without to enter in the next step to the Desktop environment.

Then, I restored the system, and tried again, but at this time I reboot immediately the system and I got the same symptoms stuck/loop on the Windows 7 logo without to enter in the next step to the Desktop.
So, I tried the 3th way, I reinstalled the OS with the minimum drivers required as last time we did (USB, Windows updates + NVME Samsung) I injected the Killer Wireless AC 1550 Drivers and the Laptop show me the same situation of stuck/loop on the Windows 7 logo without to enter in the next step to the Desktop environment.
Now, I restored everything again and I'm ready for other tests. So, I confirm that , with the Killer Wireless AC 1550 Drivers Modded in this way, we have some problems.

Now, I go through to all your 3 posts:

Post #86

Vineet Garg:

2. I would try myself to make it sure. I would like to try USB 3.1 controller downgraded as USB 3.0 controller.
Cris:
No worries about,because It's ok even the Downgrade for me, I hope really you can my friend...

Vineet Garg:
4. Now we don't need to use MS Updates for NVMe (2). The Installation problem should end with these drivers. If itdoesn't end here, we will add Chipset driver to the ISO.
Cris:
In meantime, I tested also this situation, and it doesn't end this problem even to add the NVMe drivers from Samsung. As I said, I believe it's some combination drivers (maybe, Chipset as well) to take out this problem in the beginning of the OS installation.

Vineet Garg:
5. You did not tell about Bluetooth ?
Cris:
Sorry if I always I forget about, but yes doesn't work the Bluetooth as well. Because, for me the Bluetooth is combine with the problem of the Killer Wireless AC 1550, and always I forget to mentioned to you.

All the rest of the points in Post #86, are well noted.

Post #87

Vineet Garg:
(g) The really missing/challenging drivers are three now: Killer Wireless AC 1550, Killer 1550 Bluetooth driver &intel USB 3.1 xhci controller driver ( A36D ).
Cris:
Yes, right, the missing/challenging drivers are these three.

All the rest of the points in Post #87, are well noted.

Post #89

Congratulation, you have been very analytical to read this situation Vineet Garg, really proud to follow you in this fullish experiments, anyway I'm here. Your thoughts in logic way make me sense to read this entire story about my case, thank you so much to teach me something else. Please, keep going on that because I'm here; we will success together on it.

Thank you so much.

Cris