The migration package
migration-4.6.0.21.517580.msu does not migrate the internal DHCP server configuration properly when a non-default internal network is used for sandbox VM. Because the configuration is not migrated, the internal DHCP server fails after the completion of migration.
The VM creation process monitors network activity from the sandbox VM that is being created. If there is no network activity from newly created VM, the VM creation process considers the VM has failed to start and treats the entire VM creation as a failure.
The sandbox VM must obtain basic network information, such as its IP address, from the internal DHCP server. But, because the DHCP service fails to start, the sandbox VM being created fails to retrieve a basic network configuration. So, the VM creation process does not see network activity from the VM being created, and the entire VM creation process fails.