virtualbox.org

Hello,

following situation:

Host System: Windows 10 64bit
Guest System: Windows 7 64bit
Virtual Box Version: 5.1.6
Guest additions: installed


When I log into the guest system with a username "test", guest additions are working.
When I log into the guest system with a username "test ö", guest additions are not working.

The problem is not the space character, it works with "test a". It is the german umlaut. If this character is part of the username (not the full name), then the additions won't start and furthermore all the functions like seamless integration and so on are not working.

Maybe somebody else can try to reproduce this, if you have the same error and if yes maybe somebody else can fix it

Regards

saber

Are the GAs installed for all users?

GAs are installed for all users (C:\Windows\System32\VBoxTray.exe). They run at login for all users (HiveKeyLocalMachine \ Software \ Microsoft \ Windows \ CurrentVersion \ Run) and there is a service running in the background (C:\Windows\System32\VBoxService.exe) under the system account.

I tested with WinXP-32, Win7-64, Win7-32, Win10-64, Win10-32, and I can replicate the problem. VBoxTray.exe does not want to launch even if launched manually, if the username is "test ö". If the username is "test o" there is no problem. I think VBoxTray does not like Unicode.

Linux based systems do not even allow you to create a username with an umlaut or spaces, so they do not exhibit the problem.

You should head to the bugtracker and either search for an appropriate bug, or open a new bug report. It would also help if you can post the bug report number here so other can see the progress, add information, or see the final resolution.

Hi,

didn't find any similar in the bugtracker, so created a new entry:
Ticket-No.: 15982

Regards

saber

P.S. Cannot post a link because I created my account yesterday.

Now there is the same problem. Tell me, could this be due to the fact that the client uses a proxy (advanced.name/ru if matters) to access the server?

We implemented a fix and uploaded a test build. Could you install the most recent 5.1 Guest Additions (revision >= 111520) from here and verify that the problem is fixed? Thank you!

I can confirm that GA builds >= rev. 11520 address the issue. Guests tested: WinXP, Win7-32, Win10-64.

@Gansel
I highly doubt that the proxy is responsible for this, but if it is the same problem, then installing the test GAs (build >= 111520) should fix it. If not, you have another problem.

Hi,

I just testet the 5.1.9.r.111520
The problem that the guest additions won't load if there is a german umlaut ("äöü")in the user name is still there.

The client is a default windows 7 installation. The client is not inside an active directory environment, there are just local users available.


I don't understand the post by Gansel: What kind of proxy are you talking about?


Regards

saber

First of all, ignore the post from Gansel, it has nothing to do with this.

Now, since I have the luxury of snapshots (temporary ones) I could repeat the experiments again. I thought of trying the Win7-64 which I didn't include in my previous post. We start with this (from an admin account):

• C:\Program Files\Oracle\VirtualBox Guest Additions>VBoxControl --version
  5.1.7r110711

Then I added two standard users, "test o" and "test ö". Logged in separately on each one. "test o" works, "test ö" fails.
Logged in as admin, updated GAs. Rebooted. Logged in as my two standard users, separately again. "test o" works, "test ö" works, and here's the proof; shared clipboard working (note that the username "test ö" is not "right" according to CMD):

• C:\Program Files\Oracle>echo %username%
  test ?
  C:\Program Files\Oracle>VBoxControl --version
  5.1.9r111520

I can't understand why yours is not working. Did you try re-installing the GAs? Are they the correct version? Can you double-check?

Hi Socrates,

Yes, it is working. It was my fault. I thought installing the latest test build of virtualbox includes the guest additions. I have downloaded the guest additions seperatly, installed them and now it is working.


Regards

saber

OK, nice. Could you also post an update in the ticket so that it can be closed?
https://www.virtualbox.org/ticket/15982