To resolve the issue consistently, you can manually delete the hidden STM32 BOOTLOADER entry, uninstalling the device (no need to delete the driver, just uninstall the device). Then reboot your board in DFU mode and it should connect as expected every time. Unfortunately I need to do this process every time I want to program, but that's far better than the inconsistent/intermittent failures before.
With the board that I have, the PC fings the unprogrammed chip, but after programming the RAM the Cypress application examples don't find it anymore. The PC, though, does find the device sometimes. Sometimes saying "working", sometimes "error 10", sometimes just as unknown device even without any possibility to manually install a driver.
Only if I use the Bulkloop example from the Cypress Suite USB 3.4.7 (not from the DVK), I can program (RAM) and run the Bulkloop example, but the Streamer Example does not work there either. If I try with the Streamer application the chip may go completely unrecogniceable (eventually it comes up again as NO EEPROM Device after some time off and some juggling with manual driver installation).
I have a big problem with my pc, whenever I use my pc the USB unplug and plug sound appears constantly, (with this I mean the sound the pc makes when you plug and unplug something haha) and I thought it was some kind of damaged device, but I've disconnected almost every usb cable I have on my pc and the problem doesn't seem to be fixed. It's kind of annoying because the sound just appears almost all of the time. I've looked up in device manager and windows says it's an unknown device that's causing this, and this makes it even more difficult to solve because I don't know which one it is. I've tried uninstalling the device driver, unplugging almost all of my usb ports and using troubleshooter to fix this, but it just doesn't work. I'll write down the device properties if this helps, the text is in spanish, but I'll use google translate.
Well I tried it for the first time today, and I get USB connectivity problems. The Win10 PC does not recognise the device (I have shorted the BOOT0 and VDD pads). In the device driver I see the VID of 0x0000 and PID of 0x0002 just like the original poster.
df19127ead