For a clean Hyper‑V setup, Arc Loader or RR are usually the recommended starting points because of their user‑friendly interfaces and better support for virtualised hardware.

: A CPU supporting Intel VT-x or AMD-V, with virtualization enabled in the BIOS/UEFI.

Use ://synology.com to locate your new virtual NAS on the network. If you'd like to start building this today, tell me: Your current Windows version (Pro, Enterprise, or Server) The number of drives you plan to dedicate to storage

Hyper-V presents virtual disks as .vhdx files on an IDE or SCSI controller. DSM 7 prefers native SATA. You will need to configure your bootloader to treat the Hyper-V virtual SCSI controller as a standard SATA controller.

These tell DSM how many SATA controllers and disks to expect. 4. Storage Setup To store your data, you must add virtual disks to the VM. Go to Settings > IDE Controller 0 (for the loader). Go to Settings > SCSI Controller .

: Ensure the Hyper-V virtual switch uses an MTU of 1500 unless your physical infrastructure completely supports Jumbo Frames (MTU 9000). Avoid setting Jumbo Frames inside DSM if it is not mirrored precisely on the Hyper-V virtual switch layer.

: Use Hyper-V’s virtual hard disks (VHDX) for easy portability or pass physical drives directly to DSM for raw performance.

Official Synology DSM updates often patch the vulnerabilities used by the bootloader. Blindly updating DSM via the Control Panel can render the system unbootable. Always check community forums (XPEnology Community) for compatibility before updating the DSM version.

Set the disk type to to ensure boot stability.

Switch the Hyper-V network adapter to "Legacy Network Adapter".