I'm sorry for late reply. Thank you for advice. It was just me being 'not smart', tried to use it on win7 without vcp driver from ST (ST-link was reconized as vcp and i decided that i already got one). Apart from that, everything works correct, but still i had to add function HAL_PWREx_EnableUSBVoltageDetector(), because it didn't have any reaction at all without it (with vbus sensing turned on). And with aforementioned functions (MX_USB_OTG_HS_PCD_Init() / MX_USB_OTG_FS_PCD_Init()) everything is also ok, when i turned VCP on FS USB it's wasn't otg anymore (instead new function MX_USB_DEVICE_Init(); appears in main). I had configured both usb HS / FS as otg at first and then configured USB FS as vcp, so i got a function in main for USB HS OTG initialization MX_USB_OTG_HS_PCD_Init() and other function MX_USB_DEVICE_Init(); for vcp config (and vice versa if configured HS as vcp, then FS was OTG, and of course i mixed it all up and misunderstood). I don't know if explained it all clearly, just tried to say that there are no problems if everything configured as needed.
It also worked for me on win10 with standard windows drivers. (Actually in description on vcp drivers download page it is said that it is even better to use standard driver for vcp, because their drivers have some problems in win 10). But i saw some posts in the internet where people installing ST drivers for win10, why? And is there any way to use STM32 vcp with standard vcp driver on windows 7? As far as i understand there is usbser.sys for that purpose on win7, but you still need to write your own inf file to load it. Need to do more research on that topic.
P.S. Thread isn't very useful or informative, maybe it is better to delete it? Or leave it and mark as answered?
