Windows 2000 Server guest reports 'The VirtualBox Guest Additions Service service terminated unexpectedly'

[Mark Cranness]

Windows 2000 Server guest reports Guest Additions Service errors during boot after upgrading to 4.2.4 (from 4.1.x).

Boot is slower than usual, and Windows displays message:

"At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details."

Event Viewer shows: "The VirtualBox Guest Additions Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action."

VBoxService.exe is running, however Services displays "Starting" in the Status column.

Changing the host time causes the guest time to also be changed, so that service is still working. Changing the service definition to system32\VBoxService.exe -v -v -v, and NO guest service messages are logged to the VirtualBox log file (I think they should be?), including NO messages about the host time change and sync.

If the service startup is set to Manual, and the service manually started, Windows displays: "Could not start the VirtualBox Guest Additions Service service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

Running the service manually with: vboxservice -v -v -v -f ... shows no likely error messages.

[Mark Cranness]

VirtualBox log (note: VM still running; no messages added after 00:00:46.962828 by guest service)

[Mark Cranness]

Manually running vboxservice.exe -v -v -v -f to look for errors

[pentagonik]

Please try the following:

To enable logging for VBoxService on the Windows guest a registry value needs to be modified.

In the guest, open regedit.exe as Administrator and add/edit the following key: HKLM\SYSTEM\CurrentControlSet\Services\VBoxService\ImagePath

from "system32\VBoxService.exe" to "system32\VBoxService.exe -vvvv --logfile c:\VBoxService.log"

After the registry modifications were made the guest needs to be restarted. Then, after the issue re-appeared, provide 1) the VBoxService.log file(s) (will be written to C:\ on the guest) and 2) the appropriate VBox.log file from the host in a zipped archive then. Thanks!

[Mark Cranness]

Re-defining service to use: --disable-control --disable-timesync --disable-vminfo --disable-memballoon --disable-vmstats --disable-pagesharing ... command line parameters (and confirming that time servive no longer updates the time), and : "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details." message still appears.

[Mark Cranness]

Logs as requested

[pentagonik]

Thanks for the logs. This will be fixed in the next upcoming release.

Please re-open the ticket if the issue still appears in the upcoming version.