Hi,
I don't think it's filtered down here yet, but there is a potential issue with some EOBD / OBDII / ELM327 interfaces. A recent Windows update can disable the interface. Most of these interfaces that have a USB connection use a serial to USB "bridge" chip. The most common series of chip is made by FTDI. These chips have been cloned by other companies. The cloned chips are used in a lot (if not all) of the cheap chinese OBDII / EODB / ELM327 interfaces. FTDI issed a new driver earlier this year (Windows driver version 2.12.0.0). This driver detects cloned chips and disables them "bricking" the interface and stopping it working. More recently this driver was rolled up in a windows update that installed the USB driver without asking
. Apparently this automatic installation has now been stopped.
If you are using one of the cheap interfaces DON'T INSTALL ANY FTDI DRIVER UPDATES! For more information see http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/ or google FTDI brick.
Robert.
I don't think it's filtered down here yet, but there is a potential issue with some EOBD / OBDII / ELM327 interfaces. A recent Windows update can disable the interface. Most of these interfaces that have a USB connection use a serial to USB "bridge" chip. The most common series of chip is made by FTDI. These chips have been cloned by other companies. The cloned chips are used in a lot (if not all) of the cheap chinese OBDII / EODB / ELM327 interfaces. FTDI issed a new driver earlier this year (Windows driver version 2.12.0.0). This driver detects cloned chips and disables them "bricking" the interface and stopping it working. More recently this driver was rolled up in a windows update that installed the USB driver without asking

If you are using one of the cheap interfaces DON'T INSTALL ANY FTDI DRIVER UPDATES! For more information see http://www.zdnet.com/article/ftdi-admits-to-bricking-innocent-users-chips-in-silent-update/ or google FTDI brick.
Robert.