-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Wireless and Networking
- HP Probook 450 G2 wireless driver installation does not work...

Create an account on the HP Community to personalize your profile and ask a question
08-10-2021 04:06 AM
Win 10 Pro 64-bit
Intel(R) Dual Band Wireless-AC 7260
Driver: 18.33.14.3, Date: 03/09/2018
I want to install driver Ver: 17.15.0.5, Date: 22/02/2015 and then lock it with a policy. However, there is no change to the driver after running sp82801.exe
The connection is very unstable and breaks regularly. I have to run the MS Trouble-shooter several times a day.
About a year ago I installed driver 17.15.0.5 Date: 22/02/2015 which seemed to be more reliable but then MS Update restored ver: 18.33.14.3
Today I found the "Prevent installation of devices that match any of these device IDs" but I need to install the older driver before trying this policy.
Solved! Go to Solution.
Accepted Solutions
08-18-2021 03:53 AM - edited 08-24-2021 02:05 PM
Update 23Aug21
So far Wi-Fi has been completely stable without any network failures, while using this driver; and the Windows 10 policy "Prevent installation of devices that match any of these device IDs" seems to be preventing it from being updated.
====================================
It never ceases to amaze me how Microsoft manages to create so many traps in their operating systems such that even us old warhorses fall into them...
I have an answer to my post, but it creates even more issues with the MS view of the defaults for messages.
I tried installing the older driver by running sp82801.exe with the newest driver in place. It made no difference. The newest driver remained in place. What I am not really sure about is whether the old driver was installed and then Win10 updated to the new driver immediately afterwards. I suspect this may have happened, so this raises the issue of the "Found new device balloon", which I don't think I have ever seen on this laptop with Win10. I deal with this further down the post.
Anyway, I tried another procedure today which worked -:
- Download the driver but don't install.
- Device Manger: Delete the device.
- Group Policy Editor (GPE): Enable "Prevent installation of devices that match any of these device IDs"
- First I tried to install the driver from safe mode +network but the Wi-Fi adapter did not appear.
- Restart and check for the adapter - nothing.
- After a minute or two though the network appeared and on checking the 2015 driver was active. Result! But will the driver update to the latest at the next update?? (I don't want this to happen!)
- Ran "Check for Updates"(may as well bite the bullet...). It displayed "downloading and installing latest Realtek drivers" - heart sank! - then error message displayed: "There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0248)"
Researched this and in the following post the author found that the error code means something slightly but significantly different. It just says that a system policy has prevented the update which of course makes sense because I enabled a policy to achieve that.
Why exactly is the Realtek driver still in Windows Update?
0x800F0248
SPAPI_E_DEVICE_INSTALL_BLOCKED
The installation of this device is forbidden by system policy. Contact your system administrator.
Actually, I don't want to see this message. And this in my opinion is at odds with the non-appearance of the Found New Device (FND) balloon which I think should appear by default and have to be suppressed by a group policy, not the other way round. We need to know if something is happening to our computers! Even the most uninterested computer used needs to know if new hardware is detected. But then if we tell Windows not to install updates do we want an error message to appear? In this case I would say not and only to display a message if a group policy is in place for that purpose. But then on reading through the FND balloon policy notes, it appears that the device driver author can suppress the balloon. So it's anyone's guess whether HP has supressed the balloon which would be a nuisance if I want to see it. Does anyone in HP know? If they have, then it should be listed in the spec for the driver. In my opinion the balloon should not be suppressed; I think this deserves another post to ask the question...
HTH
08-18-2021 03:53 AM - edited 08-24-2021 02:05 PM
Update 23Aug21
So far Wi-Fi has been completely stable without any network failures, while using this driver; and the Windows 10 policy "Prevent installation of devices that match any of these device IDs" seems to be preventing it from being updated.
====================================
It never ceases to amaze me how Microsoft manages to create so many traps in their operating systems such that even us old warhorses fall into them...
I have an answer to my post, but it creates even more issues with the MS view of the defaults for messages.
I tried installing the older driver by running sp82801.exe with the newest driver in place. It made no difference. The newest driver remained in place. What I am not really sure about is whether the old driver was installed and then Win10 updated to the new driver immediately afterwards. I suspect this may have happened, so this raises the issue of the "Found new device balloon", which I don't think I have ever seen on this laptop with Win10. I deal with this further down the post.
Anyway, I tried another procedure today which worked -:
- Download the driver but don't install.
- Device Manger: Delete the device.
- Group Policy Editor (GPE): Enable "Prevent installation of devices that match any of these device IDs"
- First I tried to install the driver from safe mode +network but the Wi-Fi adapter did not appear.
- Restart and check for the adapter - nothing.
- After a minute or two though the network appeared and on checking the 2015 driver was active. Result! But will the driver update to the latest at the next update?? (I don't want this to happen!)
- Ran "Check for Updates"(may as well bite the bullet...). It displayed "downloading and installing latest Realtek drivers" - heart sank! - then error message displayed: "There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0248)"
Researched this and in the following post the author found that the error code means something slightly but significantly different. It just says that a system policy has prevented the update which of course makes sense because I enabled a policy to achieve that.
Why exactly is the Realtek driver still in Windows Update?
0x800F0248
SPAPI_E_DEVICE_INSTALL_BLOCKED
The installation of this device is forbidden by system policy. Contact your system administrator.
Actually, I don't want to see this message. And this in my opinion is at odds with the non-appearance of the Found New Device (FND) balloon which I think should appear by default and have to be suppressed by a group policy, not the other way round. We need to know if something is happening to our computers! Even the most uninterested computer used needs to know if new hardware is detected. But then if we tell Windows not to install updates do we want an error message to appear? In this case I would say not and only to display a message if a group policy is in place for that purpose. But then on reading through the FND balloon policy notes, it appears that the device driver author can suppress the balloon. So it's anyone's guess whether HP has supressed the balloon which would be a nuisance if I want to see it. Does anyone in HP know? If they have, then it should be listed in the spec for the driver. In my opinion the balloon should not be suppressed; I think this deserves another post to ask the question...
HTH