Different IGuestSession::processCreate behavior in v7 from v6 => fixed in 7.0.x x>14

[ReseT]

In version 6 if call IGuestSession::processCreate with ProcessCreateFlag_Profile flag, new process created and its UI showed at virtual machine desktop. In version 7 if do the same call, the new process will be created as background process(no UI is displayed). Is it defect or an expected behavior? If expected behavior, please tell me how to create process with UI in version 7.

[ReseT]

Version 7 process settings

[ReseT]

Version 6 process settings

[ReseT]

Version 7 impersonates created process with specified credentials but process is executed in 0 session. (version 6 executes it in 1 session) see screenshots

[Rami Abughazaleh]

I also ran into this issue and posted the unexpected behavior in the forum here: ​https://forums.virtualbox.org/viewtopic.php?f=34&t=108881

[Rami Abughazaleh]

I believe the "Guest type" field of this issue should be set to "Windows", and I'm thinking the "Host type" should be set to "all". I'm thinking the "Component" should be "guest additions".

I'm not sure if these are used to help prioritize issues. Are regression issues also given a higher priority?

I'm thinking this is also still an issue in VirtualBox 7.0.8.

[Rami Abughazaleh]

From ​https://forums.virtualbox.org/viewtopic.php?t=109351

We've identified and (hopefully) fixed the issue; the reason was that the service on the guest did not start guest processes in session >= 1 anymore.

The issue should be fixed with the latest 7.0 test build for the Guest Additions (build >= 161506), which can be found here:

https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_7.0.15-161506.iso

After the installation the guest needs to be rebooted.

Please let us know if this fixed the issue for you. Thanks!

[Rami Abughazaleh]

I verified the issue is resolved in VirtualBox 7.0.18 and VirtualBox 7.0.18 Guest Additions, using a Windows 10 Host and Windows 10 Guest.

I was expecting to see this mentioned in the change log, referencing this ticket.

Thank you.

[paulson]

Thanks for the feedback. This was resolved in VirtualBox 7.0.16 but the Changelog update was overlooked. Our apologies for the oversight.