(Sorry, translated by ...)
I have questions about which I am not find anything on the Internet.
I have with examples and advice from the web a virtual com port for STM32LXX MD and HD devices created.
This works in your own applications under XP, Win7, Win 8, Win 8.1 as x32 and x86 machines with no problems. Send and receive, hot-plug, data rates up to 400 kB, there are no problems.
Windows side, I have the STM drivers 1.3.1 or 1.4.0 can use as trouble-free.
My Windows programs use GetDefaultCommConfig, CreateFile, SetCommState, GetCommState, WaitForSingleObject ... ... to manage the ComPorts. Other virtual com ports (eg CP210 devices) I can speak without problems with my software under Windows 10.
Under Windows 10 but does my created virtual Com port no longer!
The STM drivers can be good and error-free installation, the status code is OK = 0x0. Connected devices are immediately recognized and duly incorporated as a COM device COMXX. Everything looks good.
I can sign by the PC to send and receive them on the microcontroller via USB.
But, mark returned but do not come to the PC. No character comes back. Windows 10 only.
Has anyone had similar experiences of you?
Have any of you STM CDC Examples under Windows 10 brought to work?
Is a modified Windows 10 functionality to blame? (A note would be that eg FTDI on 28/07/2015 new drivers brought out.)
If STM implement new drivers for Windows 10?
Could my PC (and other virtual machines) be guilty despite an OK from the driver?
If other STM-CDC examples run under Windows 10, where I would have to begin to repair?
Thanks for any information I can get.