[SOLVED] Windows Server 2019 boot environment and virtIO


Mar 18, 2021
I just had a Windows Server 2019 reboot into "automatic startup repair", which it couldn't perform because it wasn't able to find the drive(s).
I then changed the disk type to scsi and repaired the disk manually—CLI, chkdsk /f C:—which did work. Changed the disk back to virtIO and Windows was back up within a minute.

I've been using virtIO for quite some time, but it seems that I never found myself in that situation before. Is that something you would expect?
Last edited:
expect what ?
something changed - it just can be that way
if windows was already running and suddenly get the error "no drives" than i guess you changed the scsi to virtio and windows didnt know the driver. if i install windows 2022 i need to enter the driver for virtio, otherwise it cant find a drive.
Within Windows the virtual disk worked without issues (using virtIO), but once the machine rebooted into "automatic startup repair" it didn't see the disks until I changed them to SATA.


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!