Opened 6 years ago
Last modified 6 years ago
#17793 new defect
Change in VM settings not taken into account with snapshots
| Reported by: | Michael Tremblay | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.12 |
| Keywords: | EFI UEFI Windows 10 Settings Configurations Boot Order Snapshot | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
On a UEFI Windows 10 x64 virtual machine with multiple snapshot, change in the configuration are not taken into account when booting, even if the virtual machine file show that these change are saved.
For example, I tried to change the boot order to Network on that virtual machine, but it still tries to boot to DVD and then Hard Drive (if I press F12 and go to Boot Manager, Network is not even there and the order doesn't correspond to the one saved.
Virtual Box version 5.2.12 r122591 running on Windows 10 Pro x64 v1709
Attachments (1)
Change History (5)
by , 6 years ago
| Attachment: | Windows 10 x64.vbox added |
|---|
comment:1 by , 6 years ago
I tried to remove every snapshot (after backing up everything), and even if the vm file specificly say that it is supposed to boot from network only, it don't even try and go directly to DVD.
comment:2 by , 6 years ago
Just saw that network boot is not possible in EFI mode, is it still true?
comment:4 by , 6 years ago
I don't think so, I'm still able to boot in EFI without problem (I don't think it's a NVRAM problem like #14279).
The EFI just doesn't see or want to boot to network (PXE).
My virtual machine file, with snapshot settings and my modified settings not taken into account