Virtual Boxの環境設定で保存できない

###DHCPサーバーの有効化ができない
バージョン情報
Windows10
virtual box 5.1.30
vagrant 1.8.6

事象：
上記環境にてVirtual boxの環境設定＞ネットワーク＞ホストオンリーアダプタータブ＞アダプタ右クリック＞ネットワークの編集＞ DHCPサーバータブ＞有効化にチェック
をして[OK]を押したところ、設定を保存できませんでしたというエラーが出てしまい、保存ができません。
どのようにすれば保存できるようになるか教えていただきたいです。

背景：
上記環境にて、vagrant upをすると[auth method: private key]にてタイムアウトとなってしまいます。VM?は立ち上がっていて、Virtual boxからログインは可能ですがsshはつながりません。原因を探るべく自宅にあるもう一台のPC(Windows7)にて、同じバージョンのvirtual box,vagrantを導入し、vagrant upしてみたところ、こちらは正常にvagrant upができ、sshもできました。
両者のvirtual box設定の違いを探ってみたところ、Windows10の方でホストオンリーネットワークのDHCPサーバーの有効化のところにチェックが入っておらず、これが原因ではないかと考えました。

###発生している問題・エラーメッセージ

###Vagrantfile

Ruby
1# -*- mode: ruby -*-
2# vi: set ft=ruby :
3
4# All Vagrant configuration is done below. The "2" in Vagrant.configure
5# configures the configuration version (we support older styles for
6# backwards compatibility). Please don't change it unless you know what
7# you're doing.
8Vagrant.configure("2") do |config|
9  # The most common configuration options are documented and commented below.
10  # For a complete reference, please see the online documentation at
11  # https://docs.vagrantup.com.
12
13  # Every Vagrant development environment requires a box. You can search for
14  # boxes at https://atlas.hashicorp.com/search.
15  config.vm.box = "puphpet/centos65-x64"
16
17  # Disable automatic box update checking. If you disable this, then
18  # boxes will only be checked for updates when the user runs
19  # `vagrant box outdated`. This is not recommended.
20  # config.vm.box_check_update = false
21
22  # Create a forwarded port mapping which allows access to a specific port
23  # within the machine from a port on the host machine. In the example below,
24  # accessing "localhost:8080" will access port 80 on the guest machine.
25  config.vm.network "forwarded_port", guest: 80, host: 8080
26
27  # Create a private network, which allows host-only access to the machine
28  # using a specific IP.
29  config.vm.network "private_network", ip: "192.168.60.10"
30
31  # Create a public network, which generally matched to bridged network.
32  # Bridged networks make the machine appear as another physical device on
33  # your network.
34  # config.vm.network "public_network"
35
36  # Share an additional folder to the guest VM. The first argument is
37  # the path on the host to the actual folder. The second argument is
38  # the path on the guest to mount the folder. And the optional third
39  # argument is a set of non-required options.
40  # config.vm.synced_folder "../data", "/vagrant_data"
41
42  # Provider-specific configuration so you can fine-tune various
43  # backing providers for Vagrant. These expose provider-specific options.
44  # Example for VirtualBox:
45  #
46  # config.vm.provider "virtualbox" do |vb|
47  #   # Display the VirtualBox GUI when booting the machine
48  #   vb.gui = true
49  #
50  #   # Customize the amount of memory on the VM:
51  #   vb.memory = "1024"
52  # end
53  #
54  # View the documentation for the provider you are using for more
55  # information on available options.
56
57  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
58  # such as FTP and Heroku are also available. See the documentation at
59  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
60  # config.push.define "atlas" do |push|
61  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
62  # end
63
64  # Enable provisioning with a shell script. Additional provisioners such as
65  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
66  # documentation for more information about their specific syntax and use.
67  # config.vm.provision "shell", inline: <<-SHELL
68  #   apt-get update
69  #   apt-get install -y apache2
70  # SHELL
71end
72