[Solved] Boot Win 8.1 takes 5 min after install virtualbox

[Bartvl]

Using windows 8.1 64 bit, virtualbox 4.3.18. Boot takes 5 min. When i uninstall virtualbox it only takes seconds. No additions installed. Also occurs in older versions. Can i provide more info?

[loukingjr]

See Minimum information needed for assistance.

[Bartvl]

I have no guest installed or running. virtualbox 4.3.18r96516, extension pack is the same version.

Code: Select all

C:\Program Files\Oracle\VirtualBox>VBoxManage list hostinfo
Host Information:

Host time: 2014-11-09T17:31:07.845000000Z
Processor online count: 4
Processor count: 4
Processor online core count: 4
Processor core count: 4
Processor#0 speed: unknown
Processor#0 description: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Processor#1 speed: unknown
Processor#1 description: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Processor#2 speed: unknown
Processor#2 description: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Processor#3 speed: unknown
Processor#3 description: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Memory size: 16056 MByte
Memory available: 11123 MByte
Operating system: Windows 8.1
Operating system version: 6.3.9600

VBoxManage list --long systemproperties :

Code: Select all

C:\Program Files\Oracle\VirtualBox>VBoxManage list --long systemproperties
API version:                     4_3
Minimum guest RAM size:          4 Megabytes
Maximum guest RAM size:          2097152 Megabytes
Minimum video RAM size:          1 Megabytes
Maximum video RAM size:          256 Megabytes
Maximum guest monitor count:     64
Minimum guest CPU count:         1
Maximum guest CPU count:         32
Virtual disk limit (info):       2199022206976 Bytes
Maximum Serial Port count:       2
Maximum Parallel Port count:     2
Maximum Boot Position:           4
Maximum PIIX3 Network Adapter count:   8
Maximum ICH9 Network Adapter count:   36
Maximum PIIX3 IDE Controllers:   1
Maximum ICH9 IDE Controllers:    1
Maximum IDE Port count:          2
Maximum Devices per IDE Port:    2
Maximum PIIX3 SATA Controllers:  1
Maximum ICH9 SATA Controllers:   8
Maximum SATA Port count:         30
Maximum Devices per SATA Port:   1
Maximum PIIX3 SCSI Controllers:  1
Maximum ICH9 SCSI Controllers:   8
Maximum SCSI Port count:         16
Maximum Devices per SCSI Port:   1
Maximum SAS PIIX3 Controllers:   1
Maximum SAS ICH9 Controllers:    8
Maximum SAS Port count:          8
Maximum Devices per SAS Port:    1
Maximum PIIX3 Floppy Controllers:1
Maximum ICH9 Floppy Controllers: 1
Maximum Floppy Port count:       1
Maximum Devices per Floppy Port: 2
Default machine folder:          C:\Users\Bart\VirtualBox VMs
Exclusive HW virtualization use: off
Default hard disk format:        VDI
VRDE auth library:               VBoxAuth
Webservice auth. library:        VBoxAuth
Remote desktop ExtPack:
Log history count:               3
Default frontend:
Autostart database path:
Default Guest Additions ISO:     C:\Program Files\Oracle\VirtualBox/VBoxGuestA
itions.iso

[loukingjr]

I don't know why it is increasing your boot time but I can tell you you have to disable Hyper-V in order to run guests in VirtualBox and I forget how it's worded since you've edited your post but I believe Data Execution Protection bit has to be disabled in the BIOS. Someone who knows Windows better than I may have more info.

[Bartvl]

I don't know why it is increasing your boot time but I can tell you you have to disable Hyper-V in order to run guests in VirtualBox and I forget how it's worded since you've edited your post but I believe Data Execution Protection bit has to be disabled in the BIOS. Someone who knows Windows better than I may have more info.

Thank you. Hyper-v is not installed. Guests are working fine. I will check my bios...

[loukingjr]

You're welcome. I did a search for long boot times for Windows 8.1 and found MANY links. Perhaps one will help. Long Boot Times Windows 8.1.

[mpack]

Are you saying the host takes longer to boot?

In that case it has to be a driver issue. My guess would be that Win8 is upset by the appearance of an unknown network connection it can't probe - the VBox Host Only adapter. You can probably configure it to leave that interface alone.

[Bartvl]

Are you saying the host takes longer to boot?

In that case it has to be a driver issue. My guess would be that Win8 is upset by the appearance of an unknown network connection it can't probe - the VBox Host Only adapter. You can probably configure it to leave that interface alone.

Indeed, the host. How can i disable the vbox host only adapter? It doesnt show in network connections in windows configuration.

[mpack]

Look in Device Manager, network adapters. If you disable it then you won't be able to create a host only network between the host and the VMs. It would be better IMHO to configure Win8 properly.

[Bartvl]

Look in Device Manager, network adapters. If you disable it then you won't be able to create a host only network between the host and the VMs. It would be better IMHO to configure Win8 properly.

Thank you. However, i uninstalled virtualbox. Installed again and disabled host only adapter in setup. Problem still consists.

• - hyper-v is not installed

• - host only adapter is not installed

• - anti virus windows defender is disabled

• - No extension pack or guest vm is installed or running

• - When i uninstall virtualbox, the system boots in seconds!

[loukingjr]

Can you try something? Try rolling back to VirtualBox 4.3.12 and see if your boot time improves. https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

[mpack]

I can't really see why anything introduced since 4.3.12 would affect the host when VBox isn't running.

[loukingjr]

I can't really see why anything introduced since 4.3.12 would affect the host when VBox isn't running.

Neither can I but I figured it can't hurt.

[Bartvl]

Just tried 4.3.12. I did even an checksum on the setup file. However the same problem...

[mpack]

There can be no magic involved here.

1. VirtualBox cannot affect the host when VirtualBox isn't running.
2. The only parts of VirtualBox which run all the time are drivers. And in fact, AFAIK only the Host-Only driver is active all the time.
3. Therefore, if you remove or disable the Host-Only driver and still get the problem, then VirtualBox isn't causing it.