I bricked an faux-FTDI last year before I swapped out the XP development notebook (now Linux) to a Windows 8.1 notebook. Fixing the issue last year on XP was easy ... seems that I am a user in the Admin group, so I could do anything I needed. When crap hit yesterday and I plugged in a new Chinese FTDI USB-serial device, the FTDI drivers bricked the device by writing PID_0000 to the adapter... kiss of death! Now, I had taken great pains on NOT doing any driver updates to the 8.1 notebook, so obviously something I installed did the FTDI update ... blast 'em.
I went to edit the two necessary files in C:\Windows\System32\DriverStore\FileRepository
according to this article. I then found out that Microsoft had protected the DriverStore\FileRepository and even with Administrator rights, I could not edit and save the necessary changes to ftdi.port.xxx and ftdi.bus.xxx.
I attempted to take add myself into the rights group (remember I am an Administrator) but the system would not permit. I attempted to take ownership and the system would not permit. I am moving to Linux, so far 4 machines in the lab, but the coding/development box is the last that I had planned on doing. After yesterday, I may change the priorities!
So, what is one to do? Boot from a Linux preview DVD or course! That solves the lesser god issue. After editing the necessary files and adding the lines (abbreviated here for brevity. File ftdiport.inf shown below, similar edits must be accomplished to ftdibus.inf
Code: Select all
[Version] ; Changed version from 04/10/2012 to 04/10/2022 in effort to avoid newer versions automatically overwriting ... no guarantees with Microsoft! DriverVer=04/10/2022,2.08.24 <...> [FtdiHw] %VID_0403&PID_0000.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_0000 %VID_0403&PID_6001.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_6001 <...> [FtdiHw.NTamd64] %VID_0403&PID_0000.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_0000 %VID_0403&PID_6001.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6001 <...> [Strings] VID_0403&PID_0000.DeviceDesc="USB Serial Port 0000" VID_0403&PID_6001.DeviceDesc="USB Serial Port"
And a good reboot.
The "real" and unbricked USB devices will plug & play. The bricked devices must be restored to working by manually associating the driver. Shown via pictures in the next post.