Symptoms
- You have added printers to a Hyper-V (Gen 2) Virtual Machine
- After installing Agent for Windows on the VM, you have created an entire machine backup.
- You restored the created backup using the agent for Hyper-V (installed on the host where the VM is located) to a new Hyper-V VM.
- The restored VM doesn't have the connected printers from the original machine:
Cause
The issue is caused by modifications to bootability when the machine is converted from EFI to BIOS (Generation 1) during recovery into new VM on Hyper-V.
Issue will be resolved in one of the upcoming releases.
This article will be updated as soon as the issue is resolved.
Workaround
Readd the printers in Windows.