Not up to date with the latest Simplix pack, I used a pack months ago though. So I think it's safe to say it's kinda updated. Code: MRP - Query Tool v124.0 [Compiled: 09/29/2022 {UTC}] -- Date/Time Ran: 10/21/2023 {UTC} -- 08:52am [SF] ===========================================[ Basic Information For This Computer ]=========================================== ==================================================[ Operating System Info ]================================================== Installation Type : Client {Non Server} Media Installation Method : Clean Version {Full Name} : Microsoft Windows 7 Professional Version {Product Name} : Windows 7 Professional - Service Pack 1 Version {SKU} : Professional {48} Edition {Registry} : Professional Architecture : 32 Bit {via AR:4} Internal Build Number : 7601 Full Build Information : 7601.26465.x86fre.win7sp1_ldr_escrow.230329-1823 Short Reference Version : 6.1.7600.16385 OS Upgrade Status : Denied/Disabled {1} Licenses allocated : 1 WSH Availability Status : Enabled WSH 'DisplayLogo' Value : Enabled {1} [All Users] Part of a Domain : False Device Role : Standalone Workstation {Ref: 0} VL/KMS Capable/Permitted : Yes General Language Name/Code : en-US / 1033 {0x409} General Language Locale : English - United States General Language Value : ENU Localized Language Name : en-US {UserSID} Localized Country Location : United States {UserSID} Multiple OS Language Names : en-US GeoID Nation ISO Location : United States [244] GeoID Nation CUR Location : Mexico [166] Time Zone Data {Registry} : Central Standard Time (Mexico) Time Zone Data {TzUtil} : Central Standard Time {Mexico} Using Daylight Saving Mode : No Daylight Adjust Clock Mode : Enabled/Checked Original Install Date/Time : 07/18/2021 8:13:01 PM {Localized} Last Boot Up Date/Time : 10/21/2023 8:42:28 AM {Localized} Total Up Time {hh:mm:ss} : 00:09:51 Dirty/Crash Shutdown Count : N/A SHA2 Code Signing Support : Enabled {0x1} SHA2 Core Code Signing : Enabled {0x1} Data Execution Prevention : OptIn/Default {Ref: 2} DEP Available : Yes DEP 32Bit Applications : Yes DEP Drivers : Yes DEP Support Policy : Enabled for OS Kernel, essential binaries and all Windows-based Services. Current Power Policy Used : Home/Office Desk {0} {UserSID} Power Plans Available : Balanced, High Performance, Power Saver Current Active Power Plan : Balanced {Ref: L} WMIC.exe Command : Present
That would be a nonsense from Microsoft. All drivers for the adapter and speaker are installed. The speaker PBS-8028 is added in Devices. This speaker installation is somehow truncated. It's just one more step for the PBS-8028 to show up in Playback devices. I don't get it.
Bluetooth Radios Hardware Ids Code: Generic Bluetooth Radio USB\VID_0A12&PID_0001&REV_8891 Microsoft Bluetooth Enumerator BTH\MS_BTHBRB
The third screenshot (i.e. the PC HelpSoft Driver Updater Pro one). I wasn't aware of the hardware ID then, so I deduced that the program might be able to correctly detect the chipset. But after you posted the IDs, it's pretty much clear that the detection was faulty, cause the hardware is indeed a Cambridge Silicon Radio (CSR)-made legacy one. Unless you're mixing things up, or the vendor duped you with a fake BT 5.0 module, of course you can't use those Realtek drivers on this hardware. As suggested by @egalerst, opt for the CSR Harmony stack, which should be enough the unleash the true potential of the hardware.
On a different note, what's wrong with the built-in Bluetooth module of the laptop? If it uses the half-mini PCIe interface (we need the model number of the target laptop to determine), then you can easily upgrade to a much better internal card that will bring compatibility to newer-gen Wi-Fi standards as well.