Opened 8 years ago
Closed 8 years ago
#16416 closed defect (worksforme)
Unable to rename VM names with non-ASCII characters (umlauts)
Reported by: | Bernd Selig | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.12 |
Keywords: | non-ASCII characters, umlauts | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description (last modified by )
Unable to rename a VB with non-ASCII characters (umlauts) within VirtualBox or with VBoxManage.
With VBoxManage:
VBoxManage.exe: error: Could not find a registered machine named 'D:\VirtualBox Images\Win10 B³ro\Win10 B³ro.vbox' VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown VBoxManage.exe: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 500 of file VBoxManageModifyVM.cpp
The following error message occurs:
Die Einstellungen der virtuellen Maschine Win10 Buero konnten nicht nach D:\VirtualBox Images\Win10 Büro\Win10 Büro.vbox abgespeichert werden. Could not rename the directory 'D:\VirtualBox Images\Win10 B�ro' to 'D:\VirtualBox Images\Win10 Buero' to save the settings file (VERR_ACCESS_DENIED). Fehlercode:E_FAIL (0x80004005) Komponente:SessionMachine Interface:IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Change History (4)
comment:1 by , 8 years ago
Description: | modified (diff) |
---|---|
Summary: | Unable to rename VB with non-ASCII characters (umlauts) → Unable to rename VM names with non-ASCII characters (umlauts) |
comment:2 by , 8 years ago
comment:3 by , 8 years ago
After your answer I did some more tests.
- I try it again with VBoxManage on the windows console with my batch script and it still didn´t work, because the encoding of the batch file to the console went wrong. On the console the umlaut >ü< was translated to a special character and therefore the VM wasn´t found. That´s no error of the VirtualBox.
- Another problem was the way I used the command line tool: My call contained in the parameter --name "VM-name" the complete path of the VM with the destination name, e.g. --name "C:\Users\MyUser\VirtualBox VMs\Windows Büro\..." like the VM source parameter. After I removed the path of the last parameter and type the command directly into a windows console it also worked.
- And I try it again with the GUI on the same computer with the same user and then it worked as expected. I don´t know why.
Sorry for the ticket and the circumstances. I hope my ticket will help another user during trouble shooting ;-).
comment:4 by , 8 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Thanks for the information.
Note:
See TracTickets
for help on using tickets.
Works here. Tested on Windows and Linux. I tried this both with VBoxManage (VBoxManage modifyvm OLD_VM_NAME --name NEW_VM_NAME) as well as with the GUI.
Actually VERR_ACCESS_DENIED looks much more like a permission problem. Are you sure that \dokumente und einstellungen\USER\VirtualBox VMs\* is writable for the current user?