Optiplex 7060 micro Driver Issue: Realtek 8822BU Wi-Fi not discovered after upgrading to Windows 11 24H2

Hi

The above agrees with what you have already posted.

Sometimes you can have a Mobile (Smart Phone), perhaps called a cell phone in some regions, and plug in a USB lead and have it share it's internet connection with your Laptop/Desktop etc.

Negating the need for the many metres of ethernet cable.

For unsigned drivers I would try turning off Secure Boot if practicable.

Something slightly more extreme...

Hi Anne_droid,

Many thanks for your reply with the explanation of the process to use to install the driver.

However, I can’t install what I don’t have . . . first I have to find and download the compatible driver, from a trusted source, before I can install it.

Trying to get help from Realtek (the OEM) is a lost cause. Didn’t mention it before, but I have the same problem with an Asus All-in-One that also cannot “see” the identical Wi-Fi adaptor after a Win 11 upgrade to version 23H2 about a year ago. E-mailed Realtek many times, to all of their so-called service e-mail addresses, but not one of them even had the common courtesy to reply. Luckily, the PC is only 2 metres away from its router, and I was able to drill through a wall to make a cabled connection.   

This time, I contacted Dell Community because the Optiplex 7060 micro PC doesn’t come with an integrated PCI Wi-Fi adapter. Therefore, I was hoping/assuming that it can’t be the only case of a Windows upgrade to 24H2 causing a plug-in (plug-and-play) adapter to not be seen/recognized by the PC.

So, please allow me to repeat the request in my original post . . . I would be most grateful to know where I can "safely" download the latest driver compatible with the Dell PC running 24H2.

Many thanks in advance.

Hi

Try....

BUT I cannot give any personal experience of the veracity/validity of any download.

https://oemdrivers.com/network-realtek-1030-44-0727-2022

Thanks again anne_droid,

Unfortunately, again, this didn’t work.

I note that the driver available from the link you gave is dated 2022. This one (that I downloaded and tried to install very soon after encountering the problem) is dated 2025 (i.e after 24H2 was released):

. . . but Microsoft security gave this warning and quarantined it:

Would be most grateful if you, or anyone, could please advise where to download a “safe” copy of the 2025 driver and/or if it is possible to just quarantine/remove/neutralise the “unsafe” part and install the driver anyway?

Many thanks in advance

Hi

I did think about suggesting booting into SAFE MODE (F8), but perhaps I wont.

Have you installed the DriverHub, not something I recommend.

OK, so the download, realtek-8822bu-wireless-lan-80211ac-usb-nic-1981283.zip

is a zip file with 2 files inside...

driver-hub-install_28.exe

realtek-8822bu-wireless-lan-80211ac-usb-nic-1981283.zip

which seem circular to me.

So inside the zipped zip is/are.....

/home/anne/Downloads/rtwlanu.sys
/home/anne/Downloads/RTUWPWlanExt.dll
/home/anne/Downloads/RTUWPUsbSwExt.dll
/home/anne/Downloads/RTUWPSrvcMain.exe
/home/anne/Downloads/RTUWPSrvcLib.dll

So did you get this far? Maybe it is the driver-hub-install_28 that is the issue.

My link has a lot more complicated files inside it.

You are concentrating/stuck on on a safe download, rather than the extract and install part methinks.

If in doubt please ask.

Hi

I have sent a PM.

Ha

managed to add the zip file with the 5 files inside hopefully.

Hi Anne_droid,

Thanks for the help/advice. Sorry about the delay in getting back to you, but I've been very busy.

Today, I've finally had time to address this issue again and, to avoid wasting any more time on this very frustrating and annoying problem, I have been undertaking a simple process of elimination to try and identify the actual culprit (between the upgrade to 24H2, the Dell, the Adapter/Dongles or the Driver and/or any permutation/combination of all 4).

I first reverted the Dell back to 23H2 . . . the Realtek Adapter/Dongle was immediately recognised and works perfectly (as before the so-called upgrade to 24H2). The driver showing in Device Manager was the Realtek version dated the 30th of April 2025. So, one of my many attempts at installing the new driver must have worked (even though I hadn’t been able to see it as the Adapter/Dongle hadn’t been recognised). This was the first indication to me that the driver was not to blame.

I then in turn tried each of the 3 identical Wi-Fi Adapter/Dongles, that our family has, in each of 2 HP laptops that we are currently using. One is still running 23H2 and the other has already been updated to 24H2. I first temporarily disabled their integrated/internal Wi-Fi adapters:

• The HP running 23H2 immediately recognised all 3 Adapter/Dongles, installed a driver and reported them all as “working”. Astonishingly, the driver was a generic Microsoft driver dated the 29th of July 2019. To me at least, this was the final and absolute proof that the driver is not to blame and a very strong indication that the Adapter/Dongles are not to blame.
• The HP running 24H2 didn’t recognise any of the Adapter/Dongles. Thus, another major international computer manufacturer’s device is also not able to recognise any of the Adapter/Dongles when running 24H2. This is a very strong indication that the Dell is not to blame.

Conclusion: The simple aforementioned simple process of elimination leads me to conclude, as suspected, that the problem was and still is the so-called “upgrade to Windows 11 24H2”. The problem now, however, is how to solve it.  

I am truly astounded at the plethora of online complaints about Wi-Fi network failures of every computer brand possible after updating to 24H2. It appears that the only solution, which consistently appears to work, requires editing the Registry, which I am reluctant to attempt.

Therefore, certain that Microsoft will do nothing but blame everyone else except themselves, I have reluctantly decided that I’ll have to maintain the Dell on 23H2 until some wise and kind soul makes a fix with a file or command to automatically change the necessary Registry entries.

In conclusion, many thanks for your help and apologies for having wasted your valuable time trying to resolve the problem by updating the driver.

Prego.