FTDI is at fault for this as they were the ones who passed on the driver to Microsoft to be included in the update. Microsoft are doing as they have always done and take the word of the manufacturers that what they are going to be including into their update will not be malicious to preexisting devices.
Yes it's a pain that this situation has come about and yes it's a pain that some peoples devices are being affected by this, but it is not the customers fault that devices are being bricked, intentionally or not. The fact of the matter is that this situation has happened. The only foreseeable way out of this is for FTDI to change their code to support correcting this issue in affected devices, which they will not want to do or foot the bill for as it's not their product in the device which is now broken.
Such as the situation is bad, this has highlighted sellers of this chip so people who have bought fake chips know where they bought them from and those places should be listed as not to further the problem. Microsoft should reverse the update so that it doesn't affect any further devices and those with affected devices will have to foot the bill and pass that back on to the manufacturing and sellers of the fake devices which were purchased.
In the long run, it's a terrible thing that has happened but but it can be reversed on most devices and once Microsoft pulls the update those devices will be able to work again, albeit that FTDI won't want to be changing their source... they should think about doing so as a customer relations exercise.
Home
Help
Search
Login
Register
