Medical device manufacturers are for-profit entities looking to make a profit. If using Windows makes it easier to make a profit then they'll use it. If that's problematic to society, from a security perspective, then regulations should be put in place to put make security costs impact the manufacturer's bottom line.
Personally, I'd like to see pentesting as part of device certification requirements.
I think the other issue here is liability -- if the manufacturer provides a "security update" and subsequently causes an error which kills a patient, it's the manufacturer's fault. Whereas if there's malware on the device, then it's the hospital's fault for not keeping the device clean.
Plus, there's a great deal of vendor lock-in in the medical devices industry, so I wouldn't expect to see hospitals suddenly adding devices from $NEW_VENDOR which bothers to spend the extra money to write security updates and spend millions getting them recertified.
I'm not sure if that's still possible these days, considering windows server weights in disk space and memory than an usual device should ever require... Maybe someone has first-hand / more up to data information about it?
And no, we didn't offer security updates (although Microsoft did provide some infrastructure to do this). This was a hardware company, the idea of providing anything other than consumables and spare parts was quite alien.
[1] The original plan was to use Linux, but we needed to connect various hardware that only came with Windows drivers...