Realtek RTL8723BE driver issue in Windows 10 .
10-12-2015 06:55 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Email to a Friend
- Flag Post
Realtek RTL8723BE network driver . after purchasing the notebook and firing it up for the first time the until upgraded itself to Windows 10; and everything appeared to be rellatively OK.
The network adaptor was using driver version: 2023.15.701.2015
However, after a recent Windows update the driver update for the adaptor has been playing havoc with the cwireless onnection . dropping it at will, and dropping it when the notebook ‘rests’.
I’ve scoured the web for a solution but nothing works, so as a final act I ‘rolled back’ the driver and all now appears OK.
Any idea when this problem with the new driver update is going to be resolved .
10-12-2015 07:25 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Email to a Friend
- Flag Post
Please uninstall the driver open the device manager uninstall the driver with delete option
please test the older driver
10-12-2015 07:26 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Email to a Friend
- Flag Post
Until Realtek fixes the issue with a new driver release.
To keep the updated driver from reinstalling, do this. hide the update.
Here is the link to the download and instructions for running the tool.
It is easy to use. Just run it and check the wireless card update you don’t want installed and that’s it.
Also, it does not temporarily hide the updates. The hide is permanent unless you run the tool again and select show hidden updates and uncheck the one(s) you want to install.
I saved the tool in a folder on my PC for future use.
10-12-2015 08:21 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Email to a Friend
- Flag Post
Thanks for that . all done so let’s hope it keeps the finger in the **bleep** for now until Realtek and/or Microsoft can get their acts together.
Should never have upgraded to Windows 10 . always promised myself I wouldn’t do it until at least 6 months down the line but the darn laptop did it automatically when it fired up for the first time. Brings back memories of OS’s gone by being in an unready state when MS released them . looks like Windows 10 isn’t going to buck that trend LOL.
The money MS is making, you’d think they could afford to pay the developers to get this sort of thing ‘right’ first time around instead of chasing their tails for ever and a day trying to fix stuff after the event.
