And the inconvenience of a failure is not trivial. Take weeks for me to be certain that the new driver was safe to rely on. I would typically get two or three failures per week but would often go two or three weeks without a failure. So if the specialized RealTek driver saves energy, then I want toįurther complicating my dilemma is that the failures of the old RealTek card reader driver were not simple to diagnose. On the other hand, the Microsoft Surface folks left the RealTek VersionĢ.0 card reader driver for years even though it clearly did not work in the Surfaces for any application that needed reliable access to a microSD card. I assume Microsoft would not distribute the specialized RealTek driver for the RealTek card reader unless it had some advantage over Microsoft's generic mass storage device driver. So I am faced with a difficult choice between reverting back to the known safe mass storage device driver and taking a chance on the new RealTek ver.
#Realtek 2.0 card reader driver windows 10 update
Now Windows Update has replaced the mass storage driver with a new version of the RealTek driver. I switched to mass storage driver a few months ago and can assure people with the same problem that it solves the problem. The unwanted storage drive disconnect problem was easily "solved" by replacing RealTek driver with the Windows USB Mass Storage Device driver (see forĭetails). Who were using the cards as mass storage for critical files, this was a crippling defect that could cost hours each time it occurred. Windows would spontaneously disconnect (eject, dismount, etc) a microSD card. I and many other users on this community had persistent problems with the card reader in several successive generations of Surface Pro (including my 4 and 6). Unwanted disconnects (ejects, dismounts) of a storage device. In particular I need to know if the update addressed the issue of I'm not interested in obvious generalities. Can anyone shed light on what's in the new version. Today (7/7/20), Windows updated the RealTek USB Card Reader driver from version 2.0 to 3.0.
0 kommentar(er)
