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

OK Vineet Garg,


here we go.



So, I made many many many tests and below I will tell you all the situation wich is, and sorry but when I wrote you my latest post I didn't go thoroughly to your post because I was thinking to don't find the actual problems/ situation where i wrote you in my latest post, but, after when I finished to wrote you my latest post I went immediately to check any news about the BIOS problems and your advices/infos was really usefull; thanks a lot.


After studing your posts and many phisical testing (even in tricky ways) the resaults are:


1) As per your infos, yes my BIOS should be the 3rd Generations of the newest EFI BIOSes as another member from "My Digital Life" explained on it, and probabily Windows 7 as the problem with the GOP (as per his explanation). But for luck at lesat this MSI laptop as the UEFI CSM mode where not all the laptops as have this functionality. Anyway, Windows 7 with CSM mode it's working and allows me to install him inside. Anyway, NO, I don't think about that this problem of fully UEFI installation could be caused by the NVidia drivers missing, to me doesn't make sense at all it, but I just tried because some one wrote this somewhere from internet....forget about .


2) Do you remember the Installation problems as I wrote you at beginning, and after those 2 problems the installation process stopping the Windows 7 installation by him self and I have to use Lazesoft to reanimate the MSR booting partition and so on... These 2 problems, comes out not for the NVMe/ or some controller drivers that it is missing inside the USB installation (because they are injected there) because probabily I have to take out all the NVMe and HDD to just keep one, because I remember these problem at the beginning I don't have when I didn't install any OSes and make a clean installation of just Windows 7 installation.

So, because I cannot take out the NVMe and HDD phisically for warranty purpose, and any software to reanimate the Boot Partition because of the GPT FAT32 it's more unusual system for these software where they goes to looking for the MSR Partitions Booting. Anyway, to remedy the GPT problems and Windows 7 Installation; by Aoemi Partition Assistant manually I take out the cloned BOOT FAT32 Partition where the installation at the beginnign create me, otherwise doesn't let me to continue to install Windows 7. After cancelled the "UEFI" Partition, I re-adjust all the Partitions; and after that I put manually all the booting files inside the FAT32 UEFI partition becaus the NTFS OS Partition it's slave of the new cloned Partition but with not enough files to let it boot; for this reason before I have used the softwares like Lazesoft to help me to riconstruct the MSR boot partition problems.


3) After adjusted (in tricky way) all of these problems and start Windows with the minimum drivers requirements, I went through to install all the Chipset drivers and so on.


4) The unique driver that doesn't want to install it is "Intel Management Engine Driver" but the extracted drivers for Windows 7 I have them I included inside the Windows 7 USB Installation by NTLite.


5) I have an amazing news, the "Intel Managment Engine Driver installation" even if doesn't install in Desktop environment (because can be only installed in Windows 10 Desktop environment), I believe that the Intel Managment Engine it is replaced by the new USB 3.1 A36D. Because when I installed the drivers for this USB 3.1 A36D, they are really fantastic drivers that can unlock the Steel Series Keyboards lights, Bluetooth, and all usb as the purpose of these drivers. So, it seems that these drivers are not for just the USB controller section but for the entire controller Intel family, and it's really amazing.



6) So, now, everithing are working nicely except the Wifi Killer 1550 (if not, is not big deal for me), and or but the Bluetooth is true that it's working but in the half way; which it means that time to times the Bluetooth get some problems and doesn't work, followed with the "Triangle signal" in the hardware list. I tried to install the own Bluetooth drivers as well but it seems it's missing something to let him work propely.


From you: I have always to switch this functionally from the BIOS, because I'm using more than one OS
Do you mean to say that UEFI+CSM blocking UEFI + GPT Win 10 ? No No No!
CRIS: No, absolutely, was just a stupid "Fancy" request from my side, because in Fully UEFI the Logo of the Laptop (at the beginning of Laptop turning on) it's in fully 4K but in CSM mode it's in 1080p and the logo appears less defined. No worry, was really a stupid thing from my side....



To me it's really a big result anyway Vineet Garg, but I would like to at least adjust the Bluetooth problem, do you think you can help me on that?


PS: Once I installed everything, even the Windwos 7 upgrades, I tried to install the Bluetooth and Wifi drivers from the new Snappy version where now with this new version there is the new forced drivers, but for the WiFi in the end he still cannot install, and for the bluetooth he can install but with no different resaults.


Thanks you a lot,
Cris

Hi Cris,
Brilliant Stuff,
Sorry for the delay!

1. So, Are you able to boot into Win 10 with CSM enabled ? As i understand, your BIOS give options to choose a CSM or Pure UEFI for every OS individually, isn't it ?

2. The Installation problem is coming from other OS/Disk boot partitions. There are some workarounds you can try in future.
For eg.
(a) If your BIOS allow, You can disable boot support for other internal hard disks & then only proceed with the win 7 installation. Once you have completed the win 7 installation, you can again enable boot support for/from other hard disks.
(b) As i remember you have 2 NVMe drives & one HDD. If you plan to install Win 7 on HDD, Don't integrate NVMe drivers & they / their boot partitions won't come into play.

3. OK, Good!

4.
(a) Forgotten ? We found that the IMEI driver listed on the product support page, doesn't have win 7 section for your device ID. I think we can easily add win 7 support for that device in the driver but I think we should look @ WinRAID forum's section for IMEI drivers.
(b) Do you remember there was a driver for your IMEI in the chipset drivers 'NULL HECI' Driver?
NEWS : That's a fake driver to just remove the yellow exclamation mark, no functionality!
(c) So, now you should explore a little whether you want / use IMEI ? Its specific functionality! (If yes we would look at WinRAID forum )
(d) As said in (b), now different sites may start advising such NULL Drivers & without even telling! Sadly, its an give up policy to accept that some advanced features will not work under Win 7 but there are some people who don't think like that.
One will only be able to make that difference by experimenting / using those drivers against their functionalities.

5. I believe that the Intel Managment Engine it is replaced by the new USB 3.1 A36D. Because when I installed the drivers for this USB 3.1 A36D, they are really fantastic drivers that can unlock the Steel Series Keyboards lights, Bluetooth, and all usb as the purpose of these drivers. So, it seems that these drivers are not for just the USB controller section but for the entire controller Intel family, and it's really amazing
It's an illusion! They are just that better with Intel USB 3 controllers / devices & not others. Just think practically, A USB 3 driver working for IMEI & other controllers! Better you use / install that driver for that particular devices from Device Manager only. If they replace other type of proper drivers, it may be a big trouble. They are stuffed with such generic information for eg Hardware IDs that they seem to support / install other Intel devices as well. Check for those/their functionalities. Please report without any biased.

6.
(a) New Device Manager View : Unknown Devices
(b) Did Bluetooth ever work partially / for little time ? Please explain.
(c) There is a button, probably with a small LED, which switches all wireless functionalities on/off for the laptop. You can make out that from within Win 10 installation, Device Manager, etc. It needs a driver for win 7 probably & such drivers are available!

7. I can try modding Wifi drivers but i am very afraid of what happened the last time. Honestly, If it is my laptop, i would always avoid that trouble times!
You are an advanced user why don't you think about running & experimenting win 7 in virtual environment there we can open up our arms.

Let me know how i can help you!

Thanks & Regards. ...

Ok Vineet Garg,

I am ready with a lot of news, because in the meantime I have gone ahead with other experiments, so as to fully understand all the problems where they come from. This time I searched all the drivers via NTLite list and I prepared everything well, in the USB/ISO Windows 7 there are all the drivers of the Notebook (I also put those of the Killer LAN 1550).
Below I will try to answer you to all of your points by this report, and to give you a well situations picture:

BIOS & INSTALLATION PROBLEMS (Solved):
Finally I found out where the problem is, once I have injected all the Windows 7 drivers and updates in the ISO / USB related to each peripheral of the Notebook (and checked with NTLite that everything was ok/founded), a new problem appears during the installation , this problem when I selected the target NVMe to start the Installation, it comes out the following message “Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk ......... "I found this YouTube video where it illustrates the same problem as I have: YouTube.
The solution that this guy gives, unfortunately does not work with my notebook, because in my BIOS the AHCI controller is already selected which should communicate easily with the NVMe and continue the installation, but what is absolutely strange it is that whether I choose the NVMe or the HDD if there is not installed any operating system inside the free HDD/NVMe target Windows 7 cannot be installed because in the BIOS Boot Section they disappear (I attached few pics about). Yes, on this important BIOS Boot Section (that allows me to boot able or disable any HDD-SSD-NVMe), when there is NOT installed any OS onside of each NVMe; the own NVMe it will disappears from the boot selections, likes that doesn’t exist. It is like that the BIOS it will auto-disable, maybe for a cause of a bug of the BIOS, because to me it’s strange that by himself it will disable the hardware because inside the NVME or HDD target cannot find any FAT32 BOOT System (where in such situation in the PC Desktop side, in the BIOS section will never happen such thing and allows you to choose the priority of the HDD/NVMe/SSD wherever if inside the disk there is or there isn’t installed the OS). This create me the problems, with Windows 7 installation. Good example it is, that you cannot see the HDD HGST of 1TB in this Boot list in below pictures, but they are listed in GREY on the Motherboard hardware information.

So I tried to work around this problem, thinking it was a communication problem between AHCI, the NVMe and Windows 7 installation, I opted to create a 40GB space in my 1TB HDD being sure that between AHCI and SATA there shouldn’t be problems, but even here I had the same problem. The only way to get around of this problem is to select the NVMe and then select "New Volume" whereby on the same screen Windows Installation will create the 100 MB BOOT as FAT32, the 128 MB for Recovery and the remaining GB space for Volume C: . But as you well know about, I can't continue with the installation because the Volumes are created and Windows does not pass to the next start of copying the Windows 7 files in the NVMe because the Volumes he will create automatically on the next step. The only way is to leave the FAT32 volume and the 128MB (where the FAT32 will turn on the BIOS and Windows 7 communication) , and the C volume: to delete, after to re-select the deleted ex-Volume C: and press NEXT and the installation will start to coping the Kernel files and so on (but he will create a second FAT32 where C: will be slave of), to then give a second error at the end of the copy files and restart. And then you know all the procedure with Lazesoft and so on…..
To avoid being able to get all these errors out, I have to select from the BIOS “Intel RST Premium With Intel Optane System Acceleration” (instead of AHCI, and it doesn't make me sense at all), start the Windows 7 Installation, select the only active HDD Hardware Disk in the list, because all the NVMe will magically disappear (because there is no active AHCI controller and the NVMe is not recognized even if there are injected drivers inide the Win 7 installation), continue the installation with the only actived SATA HDD, to then install Windows in the 40 GB partition Free. Wait for everything to be installed (finally with NO errors) when will be finished the installation and Windows will restart the PC, on restart select Windows 10 OS, and copy the 3 volumes created to the HDD in the NVMe (FAT32 100mb, 128 mb Recovery, and Volume C:) via AOEMI Backupper (or similar software). After, once copied the Volumes extend the Volume C: with the rest of the empty space from the NVMe and reboot the PC, to allow Windows 7 installation to continue with the installation process and hardware components and so on......

Example, with Windows 10 (of course) or Linux there are not these problems in the Installation Process, but I believe that with this BIOS third Generation and Windows 7, in Windows 7 there is something missing to be able to recognize the NVMe even if the BIOS deletes them because they could be empty, example in the normal PC Desktop the BIOS never makes NVMe or SATA disappear (even if there is nothing installed in it) it will never behaves in this way. So, I was thinking either it is a BIOS Bug that with Windows 7 has this special problem or it is some controller in between that prevents correct operation with Windows 7 and fails to communicate well with the NVMe – HDD and BIOS by AHCI. Whatever the problem it is, finally I managed to get around on it. But I would like to know your thoughts on that…..

Rebus between fully UEFI & UEFI with CSM (Solved):
Good news, Windows 7 can start under the fully UEFI (so, no CSM)!!!!
The procedure it is to install Windows 7 under UEFI CSM mode (because the installation will not work under fully UEFI mode), and once everything will be installed (even all the upgrades) in the BIOS you can switch to fully UEFI. The important it is that the Secure Boot will remain Disable (Fast Boot can keep able). Another important thing, it’s to modify the system text DPI after you switched to fully EFI mode, because for somehow if modify the DPI test in Windows 7 under CSM and then you Switch to fully UEFI from the BIOS, as I said for some how will create a mess with the “zoom DPI text” in different sections of the OS (like in the right click mouse menu will be more smaller than the rest of the DPI zoom of the OS and so on).

Bluetooth News (Partly Solved):
Here I went mad about, but finally I discovered the actual situation.
The Bluetooth time to times doesn’t work, I tried many others compatible Bluetooth drivers (signet and not signet) only from Station-Drivers as these ones: https://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=4072&lang=en .
So, after getting mad, I found the WHY some times the Bluetooth working and sometime not:
1) First every time that I tried to install some not working driver, I went always to uninstall the driver from Device Manager, and after few seconds Windows will install (always) automatically the basic drivers from the Kernel. And these drivers were sometimes working till the restart of the PC and then need to reinstall them again and again and again. Now, when I noticed that this procedure doesn’t work at all (even after reboot the system) and gives me back the 43 message; for just occasionally I discovered that the installation problem of the basic Drivers Bluetooth from Windows was caused by my USB Bluetooth Mouse receiver because in Windows 10 I don’t need the receiver because the mouse can work by the build-in Bluetooth Antenna (and I will explain you another thing below about this). So, now, if I want that my Bluetooth will work every time I will reboot the system, first I have to disconnect my Bluetooth USB mouse receiver before turn off the PC or reboot the System, because for some how go in conflict with the Windows basic drivers for Intel Bluetooth hardware and turn off the “Bluetooth Enumerator driver” and keeps the “Generic Bluetooth Adapter Driver” on, but with 43 error and the yellow triangle.
2) If I want to unlock this problem, it’s not enough to reinstall the basic drivers, so because the hardware it’s totally blocked by the Windows 7 OS the unique way to unlock the Bluetooth it’s to reboot the PC go to Windows 10 let the Bluetooth to work properly, reboot - go to Windows 7 OS (with the USB Bluetooth mouse receiver disconnected) and re-install the basic drivers, aaaand Magically the Bluetooth works AGAIN!!!!
3) I need to correct my self about the “half way Bluetooth working” as I mentioned in my latest post. The Bluetooth work well can receive the files and connect to some like PC Joypad and so on….the unique problem (and I discovered yesterday) when I went to my Logitech site to check my mouse drivers for Windows 7, I discovered that my mouse can work under Bluetooth mode only from Windows 8 to Windows 10. For Windows 7, cannot work under Bluetooth mode cause of the Windows 7 limitation functionality. So, I went to source to get inform tecnically why, and I discovered that Windows 7 doesn’t has the Bluetooth Low Energy API, did you know that? Here there is some quick chat explanation about https://stackoverflow.com/questions/14401435/bluetooth-low-energy-api-for-windows-7-0 .
4) So, now I totally understand why some BLA future from my phone cannot be installed in Windows 7 and the mouse cannot be listed out when I press the Bluetooth paring from the mouse………
5) I didn’t know that, because I have one mini USB Bluetooth receiver from my PC Desktop but was a software from the USB brand that helps me to find my mouse, and maybe they have inside the Software some API driver for the Bluetooth Low Energy /BLA devices because Windows 7 doesn’t has by default…
Have you some idea how can I get these API? I saw someone that builds some software to emulate these API to let communicate the BLA Bluetooth Devices……
About the Mouse specs, where the Logitech write this, please watch the latest picture attached.



To reply you in some points where the rest are already replied by this report above:

Vineet Garg:
4.
(a) Forgotten ? We found that the IMEI driver listed on the product support page, doesn't have win 7 section for your device ID. I think we can easily add win 7 support for that device in the driver but I think we should look @ WinRAID forum's section for IMEI drivers.
CRIS: Thanks for this, I already injected them from the USB installation, it's the same?

(b) Do you remember there was a driver for your IMEI in the chipset drivers 'NULL HECI' Driver?
NEWS : That's a fake driver to just remove the yellow exclamation mark, no functionality!
CRIS: Perfect, but for somehow I succesfully installed from the USB Installation and it's listed out in Device Manager, it's this one: Intel(R) HECI #1 - A360?
(c) So, now you should explore a little whether you want / use IMEI ? Its specific functionality! (If yes we would look at WinRAID forum )
As said in (b), now different sites may start advising such NULL Drivers & without even telling! Sadly, its an give up policy to accept that some advanced features will not work under Win 7 but there are some people who don't think like that.
One will only be able to make that difference by experimenting / using those drivers against their functionalities.


CRIS: Really thanks for this sourcing but I don't think it's important for me now, especially for Windows 7 in the laptop where less I touch and better it is....Thank you anyway Vineet Garg

Vineet Garg :
5. I believe that the Intel Managment Engine it is replaced by the new USB 3.1 A36D. Because when I installed the drivers for this USB 3.1 A36D, they are really fantastic drivers that can unlock the Steel Series Keyboards lights, Bluetooth, and all usb as the purpose of these drivers. So, it seems that these drivers are not for just the USB controller section but for the entire controller Intel family, and it's really amazing
It's an illusion! They are just that better with Intel USB 3 controllers / devices & not others. Just think practically, A USB 3 driver working for IMEI & other controllers! Better you use / install that driver for that particular devices from Device Manager only. If they replace other type of proper drivers, it may be a big trouble. They are stuffed with such generic information for eg Hardware IDs that they seem to support / install other Intel devices as well. Check for those/their functionalities. Please report without any biased.

CRIS: You are totally right on that, and I can see especially with this Bluetooth case....

Vineet Garg:
6.
(a) New Device Manager View : Unknown Devices
(b) Did Bluetooth ever work partially / for little time ? Please explain.
(c) There is a button, probably with a small LED, which switches all wireless functionalities on/off for the laptop. You can make out that from within Win 10 installation, Device Manager, etc. It needs a driver for win 7 probably & such drivers are available!

CRIS: The SCM software from MSI, working well but cannot turn of and Turn on the WIFI and Bluetooth. Because as per my understanding this it's controlled by SCM where a driver that controller it, it calls "ENE Radio Switch" it's the unique driver that exist only for Windows 10 and not for Windows 7. Windows 7 can only managment it (turn on or turn off) by the internal basic Windows 7 Software/Fuctionality. To me not big deal this, really not important....


Vineet Garg :

7. I can try modding Wifi drivers but i am very afraid of what happened the last time. Honestly, If it is my laptop, i would always avoid that trouble times!
You are an advanced user why don't you think about running & experimenting win 7 in virtual environment there we can open up our arms.

CRIS: Honestly, I tried many of them (I mean drivers) and everyone even from Snappy (because in the end I can install them) they have the problems with the Driver Controller, maybe the drivers are fine but the Controller cannot start, it's the same case as for the USB.... I don't know if it needs someone that really mod and it construct this Controller Tree Driver.... Your thoughts?

So, for now I can see only the latest challenge it is with the Killer Lan 1550, because with the rest we are on track
Thank you,
Cris

Hi Cris,
Greets,
1. Your brilliant reporting helps my causes. I will go through it & let you know.
2. Right now i am focusing on Wifi drivers. As you said you are happy with experimenting, I am analyzing some old drivers & would be out with a driver in a couple of days.

Thanks & Regards. ...

Hi Cris,
Greets,
It seems I am making good progress but I need some more time.

In the meantime :

1) Give me full Hardware IDs & Compatible IDs for Killer Wireless from Device Manager.

2) I have extracted the very basic driver components for Intel Wireless Cards :

Intel Wifi Drivers.rar - Google Drive

All the modding will be around that driver only.

( The original driver extracted is here : Intel PROSet/Wireless Driver (IT Administrators) 20.0.2 64-bit zip : SOFTPEDIA DOWNLOAD )

So,
1. Extract the Driver.rar to a folder
2. Replace the original NETwsw04.INF with this one : NETwsw04.INF - Google Drive
( Google Drive is dealing with it as a music file, Just download it )
3. Keep the original file to a safe place
4. Execute iprodifx.exe

Don't care for strange names but of course tell me about all those! How it is appearing everywhere ?
Observe & Check the functionality.
Let me know. ...

Take care the file name is not changed even to NETwsw04(1).INF ! Exactly same name !

What to say about you........Great!

1) Replace the file with this one : NETwsw04.INF - Google Drive
2) A Watchful Force Install from Device Manager.
3) I am interested in Appearance in Device Manager, Installation & Functionality.
4) You are not able to make & restore 'System Restore Point' ? The problem occurs due to a driver so you can boot into Safe Mode & restore System Restore Point.
( Though System Restore uninstalls the program & registry, but leaves files & folders made by the installation but they are not a problem in most cases. )
( System Image Restore takes hardly 30 min for me with Macrium Reflect free )