Guest Addition not working with Windows NT 4.0 Guest

[Sbf93]

Steps to reproduce the issue:

Install VirtualBox 6.1.4

Install Extension_Pack-6.1.4.vbox-extpack

Create a VM and install Win NT 4.0 on the guest. I used a german OEM iso from here: ​https://archive.org/download/WinNTWKS40DEU/NTWKS40D.iso

Install Service Pack 6a on the guest.

Install Guest Additions on guest. The installation completes without any errors. After installing it requests a reboot.

Now, whenever I boot the VM and login a user, the system freezes for around a minute and then displays an error message. Translated to english: "The start of at least one service failed, which should be started at system boot. Check the Event Viewer."

There are no information in the Event Viewer. But when I look at the services, the only service with automatic start, which is not running is "VirtualBox Guest Additions Service". When I manually try to start this service, the following error appears (free translation to english): "The VirtualBox Guest Additions Service on HOSTNAME could not be started. Error 2186: The service does not respond to the control function."

Some functions of the guest additions are working fine, like higher resolutions and True Color mode. But Shared folders or mouse integration are not working at all. When I try the exact same procedure with VirtualBox 5.2.38, I do not get any errors.

[Sbf93]

Error after boot

[Sbf93]

error after manual service start

[pentagonik]

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:\Temp\VBoxService.log"

Make sure that the directory "C:\Temp" exists.

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

[Sbf93]

I followed the steps to activate the logging on the guest, but no log-file was generated after I restarted the guest and triggered the error.

[Sbf93]

Bug is still present in VirtualBox 6.1.6. I tried version 6.0.20 too and got the same error.

[bird]

I found a problem with VBoxService on NT4 that affects 6.1.x and 6.0.x, but not 5.2.x. It would typically cause VBoxService to crash and could therefore be responsible for that failed service message. Will try upload a test build of the guest additions ISO before long, anything tagged r137519 or higher includes the fix.

[Sbf93]

Im sorry to say, that this issue is not fixed in r137519.

[Doublltime]

VBoxService.zip contains the VBoxService.log file with the discovery that the network adapter was causing a fatal error in guest additions

[Doublltime]

I am glad to say that the issue seems to be related to not configuring the network adapter. I was experiencing this problem. I produced a logfile after the registry edit listed above, and the last error was listed as.

"22:49:54.871946 vminfo Error: VMInfo/Network: Failed to get adapter info: Error 50"

Changing my network adapter configuration to Host-only Adapter worked for me. I still have some service that is failing to start when I begin the guest session and reach the login, but I suspect that is something to do with the guest and not the virtualbox host.

Hope this helps someone else. Cheers

[pentagonik]

Does this still occur to you using the latest 6.1.32 Guest Additions? Please note that a guest reboot is necessary after updating the Guest Additions.

[Booboo]

I have this same issue with "The VBoxGuest Support Driver service failed to start due to the following error: The specified network resource or device is no longer accessible. in Event Viewer after start-up. A manual and boot-time start of the service fails also.

A few details: MacOS host, Windows NT 4 SP6 guest on Virtual Box 6.1.32.

I am using an internal network and when I try and start the service manually, I receive a "Could not start the VBoxGuest Support Driver Service on VMNAME. Error 00555: The specified network resource or device is no longer available.