Realtek card reader driver not used despite install (Windows 10 x64)

[S_Rawat]

So, I'm having a hard time determining why exactly my Realtek card reader driver is getting installed successfully but still my OS (Windows 10 x64 LTSB) picks up outdated microsoft drivers no matter what I do. I'm an advanced user and have tried a fair bit of driver installation workarounds myself but to no avail. 

Issue simulation:

In reference to screenshots:

1. The card reader in my HP 245 G5 notebook is a realtek one (judged by the device instance path details which is - USBSTOR\DISK&VEN_REALSIL&PROD_RTSUERLUN0&REV_1.00\0000). The current driver in the system is Jun-06 driver by MS. 

2. HP Support Assistant notified me of a driver update available for the card reader.

3. I initiate the installation which is shown as successful. So I reboot the system.

4. Even after the reboot the driver version remains the same as before. In short the realtek driver isn't picked up.

Other things I've tried.

1. Tried to manually update the driver by pointing windows to search in drvbin64 folder in C:\swsetup\<HP update exe version>\. The method fails as windows isn't able to find any appropriate matching driver for the device.

2. Manually selected the RtsUerX.inf file in the drvbin64 folder but windows still won't find the matching driver.

3. Turned off driver signature enforcement in Windows 10 permanently and in the instance using advance startup options. Still no go.

4. Installed the RtsUserX.inf still the driver won't get picked up.

5. Tried uninstalling the existing MS driver altogether but still upon reboot system would pick up by itself the dated MS driver.

I'm at my wits end here as to why this behaviour? Any help is deeply appreciated.Before installation the driver version and detailsHPSA update shownSuccessful installationDriver remains the same after reboot.

[S_Rawat]

Here is what logs in Windows event logs throw  up (numbered in increasing sequence as they occur in system logs)

1. Driver Management has concluded the process to add Service RTSUER for Device Instance ID USB\VID_0BDA&PID_0177\20121112761000000 with the following status: 0.

2. Driver Management concluded the process to install driver rtsuerx.inf_amd64_fc7903fa9d7efb23\rtsuerx.inf for Device Instance ID USB\VID_0BDA&PID_0177\20121112761000000 with the following status: 0x0.

3. A driver package which uses user-mode driver framework version 2.19.0 is being installed on device SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_REALSIL&PROD_RTSUERLUN0&REV_1.00#0000#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}.

4. The UMDF service WpdFs (CLSID {112de495-ac4c-46f8-b663-6a4266c53313}) was upgraded.  It requires framework version 2.19.0 or higher.

5. The driver package installation has succeeded.

6. Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_REALSIL&PROD_RTSUERLUN0&REV_1.00#0000#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.

7. Drivers were successfully installed for device WPD Device.

8. Media player and imaging program compatibility layers were successfully registered for device %1. Layer bits %2 were requested, layer bits %3 were registered.

9. Autoplay registration was skipped for device %1.

10. Driver Management concluded the process to install driver wpdfs.inf_amd64_4b4cfcfa114bdc22\wpdfs.inf for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_REALSIL&PROD_RTSUERLUN0&REV_1.00#0000#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0x0.

11. 

[S_Rawat]

:: bump ::