S/N: HGeBPLIY3H240909843
Purchased at OZON.RU @ December 6, 2024
After updating to Windows 24H2, the network card disappeared from the system and a CD-ROM appeared. I studied the topic, this is the behavior of USB network cards, if they do not see a suitable driver in the system, then they switch to the disk drive mode, which, in theory, should have an installation package of drivers. In our case, it is not.
The device finds itself as VID_0BDA&PID_8151, and the problem is that drivers for VID_0BDA&PID_8153 are available on the network. At the moment, VID_0BDA&PID_8151 is a Bluetooth device (the newest drivers)
Why the identifier was changed, I do not know, but for Windows, a driver is needed for a network card with the specified ID, otherwise it will remain in CD-ROM mode.
Please, can you provide the correct drivers for VID_0BDA&PID_8151, I promise to never update the system to version 24H2 again, which causes such troubles.
Answering myself. It was necessary to turn off the laptop (not reboot) and disconnect the power from the socket. This causes the effect of resetting the network controller so that it can switch to network card mode.
Classic Windows move, huh? If VID_0BDA&PID_8151 went Bluetooth, Realtek should have the right drivers for you. Maybe try manually downloading them, or give Device Manager a shot to roll things back. Don’t let 24H2 win!
Rolling back does not change anything, it still remains in CD-ROM mode and yes, in this mode it has the identifier PID_8151.
What helped me personally:
It is really necessary to roll back (reinstall) no matter what version 23H2. Even after this, the CD with the ID PID_8151 hangs in the new system.
Next, you need to turn off the computer (start - shutdown) and disconnect the power supply from the laptop for a few seconds.
After that, turn on the power and turn on the laptop, after which the network card appears (hurray) with the ID PID_8152.
And once again - Never update to 24H2, at least for now.
Thanks alot
If VID_0BDA&PID_8151 went Bluetooth, Realtek should have the right drivers for you. Maybe try manually downloading them, or give Device Manager a shot to roll things back. Don’t let 24H2 win! 
