VirtualBox

Opened 4 years ago

#20015 new defect

VBox commands via MS openssh on a windows 10 host system fail CO_E_RUNAS_LOGON_FAILURE

Reported by: mih Owned by:
Component: VM control Version: VirtualBox 6.1.16
Keywords: Cc:
Guest type: all Host type: Windows

Description

Trying to run "VBoxManage list vms" on a Windows 10 host, when connected to the host via Microsoft OpenSSH server fails:

VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: Completely failed to instantiate CLSID_VirtualBox: CO_E_RUNAS_LOGON_FAILURE VBoxManage.exe: error: Details: code CO_E_RUNAS_LOGON_FAILURE (0x8000401a), component VirtualBoxClientWrap, interface IVirtualBoxClient

This works as soon as any user (it does not need to be the one who tries to run the command) connects via rdp to the system. If a user B is connected to the system and a VBox is started from user A, the VBoxHeadless process is running as user B...

Is it possible to avoid this behaviour and run VBoxManage commands and even start headless VMs connected via openssh? What is the reason for this behaviour?

Change History (0)

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy