Hi all, this might come as a silly question, but i'm currently trying to play with command line deployment of the proset wifi driver for a mixture of laptops with a mixture of hardware profiles - 8265 series, 9560 series, AX200 series, etc.
From Intel's own documentation, the command would be (for example):
blurb_22_80_1.exe -s -l "c:\somefolder\log file path.log"
and in general that works - but from testing i get two errors very occasionally returned. Error code 1603 and 350. 1603 appears to be driver not applicable (fine), but i can't find what error 350 might be. If i installed the package myself directly as administrator, it appears to install fine.
I have found documentation about error codes from the bluetooth installer, but not for the wifi one. Does anyone know what error 350 might mean, or know where I can find the error documentation? For example does it mean: reboot pending so didn't deploy?
Appreciate any help someone can offer!
a- Error code 350 is pending reboot, and it really does not depend on us. If in the previous installation one of the INFs requested reboot (quite common with the WiFi driver, no idea about BT) then any installation afterward will request reboot, this can also happen if there is a pending Windows update.
b- Error code 1603 is a general error, it can be anything from an exception in code to a problem with the setup.xml. It would be needed to see the log for that. (You may share the log so we can review it further to see if there are any additional details we might provide).
We recommend performing a Windows update and also we would suggest referring to your Computer Original Equipment Manufacturer (OEM) to check this further since this error could be linked to the operating system (OS).
6- When and where do you receive the Error codes 1603 and 350? Is it when trying to install the driver? Is it after installing the driver and using the computers under "regular use"? Do you have this issue with the Wireless, with Bluetooth, or with both? Could you please provide more details and screenshots if possible?
Hi AndrewG - the confirmation that error 350 is just pending restart required is all I needed. I should be able to puzzle out the 1603 error myself - as I say we have a policy that prevents installs of certain drivers which I think we just need to temporarily suspend. Any anomalies left after that will be minor (I hope). Thankyou for your time in confirming.
Since the thread has been marked as "Solved" and there are no more questions, we will proceed to close it now. If you need any additional information, please submit a new question as this thread will no longer be monitored.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
By the way, since this is an OEM laptop device, please take into consideration that our support may be limited since we are not familiar with the technology, settings, customizations, custom drivers, and features that the OEM has designed and installed for your system, nevertheless, I will do my best to assist you with your concern.
I want to attempt a cold reboot of my laptop. My battery was removable, but the case was not easy to open as it needs the help of a technician to remove screws to open the case. In this case, can I follow the steps for a Laptop cold reboot with a non-removable battery?
We have some issues as well with this wifi adapter, regardless of which driver version the users are in. We have recently changed the authentication method to EAP-TTLS and for the moment users that have this Wifi adapter have reported Wifi disconnections. The Wlan report at the time of the event show that the user has disconnected from the wifi network when the user did not. In system event we see an information level event that informs the driver is corrupt or not properly installed.
I tried the cold reboot. The only problem is when I turned on my laptop after pressing the power button for 15 seconds, the screen is black and I did shut down once more and turned on again my laptop. The cold reboot did not work as expected. Should I repeat the cold reboot again considering the black screen problem?
probably not it, I'm having the same issue (blank screen on cold boot and everything} and the only peripherals my laptop has are wired ones. it also does this regardless of whether they're plugged in or not. I hope someone finds out what the actual problem is. The generic solution given by senkuchan isn't cutting it for me, and the problem with my wifi adapter is getting worse.
Upon looking further, I think it's because of an issue with the hardware itself. I'm a bit out of practice when it comes to mucking about with a laptop's internal components, and am therefore too nervous to try this out myself, but this might work
Thanks for your reply. The wifi adapter is Wi-Fi 6 AX201 160 MHz, this is, as far as i understand the same adapter as the original poster. Regardless if realy needed by intel i can open a diferent threat.
In line with your concern that, if you should repeat the cold reboot process, yes you may perform again the cold reboot, but this time, you may need to perform the clean installation first of your OEM driver for your wi-fi adapter: ( -gaming/tuf-gaming/asus-tuf-gaming-f15/helpdesk_download?model2Name=FX506LI) and performed a Cold Reboot: ( ).
Bluetooth and other communications methods used with wireless mice and keyboards all use the same 2.4GHz transmission band that is used for standard WiFi. As well, USB 3.x transmission is done using the 2.4GHz signalling, so it too can contribute to WiFi interference if the USB cables being used are not well shielded.
Got a similar issue with my Razor Blade 15 Advanced (RZ09-0301). WiFi and Bluetooth functions are suddenly down. The Intel Wi-Fi 6 AX200 driver shows a code 10 error and keeps reinstalling itself automatically as soon as I try delete it showing the same error again and again. Tried to delete all corresponding Intel software and drivers and reinstall it. So far no solution in sight ...
Same here on my 2020 RZ-033. Tried going up and down with intel drivers, reseting network settings but to no avail. first time this happened i was also able to uninstall and reinstall the intel drivers.
I've encountered a similar issue with my Razor Blade 15 Advanced (RZ09-0301), where both WiFi and Bluetooth functions have unexpectedly stopped working. Upon investigation, I noticed that the Intel Wi-Fi 6 AX200 driver consistently displays a code 10 error. Strangely, whenever I attempt to delete the driver, it automatically reinstalls itself, presenting the same error repeatedly.
I've encountered a similar issue with my Razor Blade 15 Advanced (RZ09-0301), where both WiFi and Bluetooth functions have unexpectedly stopped working. Upon investigation, I noticed that the Intel Wi-Fi 6 AX200 driver consistently displays a code 10 error. Strangely, whenever I attempt to delete the driver, it automatically reinstalls itself, presenting the same error repeatedlyTennis Premium All Clash MOD Version.
Remember to create a backup of your important data before making significant changes to your system.Best Facebook VIP Account Bio Symbols 2024 If the issue persists, seeking assistance from technical support or a knowledgeable professional may be the next step.
Other than uninstalling and re-installing the driver, what have you tried? Is there anything connected? Dock? ethernet? No physical wifi switch I assume, what about a fn key to enable/disable the wifi?
After the last update for Windows 11 insider (Home). The driver for the wireless card stopped working. There is already a guide on the issue on Intel's boards, but it is not working either. So i think the issue is with the Windows.
I managed to bring my Killer wireless network adapter back - after wasted a whole morning. Windows updated overnight and I lost the card after that. This was the error I saw in Event Viewer:
@OussD After a lot of research, the problem is usually solved by resetting the bios to default, mainly on dell laptops. The problem is caused after doing bios update or installing windows 11.
Also don't forget to install the updated drivers.