Could not launch a process for the machine 'Windows7 64bit'

[DTMOC]

Perhaps this is easy for someone...

Having read other similar threads, no changes have been made to any files, locations, virtual disks etc etc.
What did occur is simply an update TO 4.3.14-95030 FROM 4.3.6-91406.

Note also, that I had already reverted BACK to 4.3.6-91406 when versions prior to 4.3.14-95030 also did not work
(same issue with not being able to start a VM).
This had solved any problems with no other changes.

After upgrading past v4.3.6-91406 the following error is produced for ALL VMs (5x in this case)
(image is attached)
-----
Failed to open a session for the virtual machine Windows7 64bit.

Could not launch a process for the machine 'Windows7 64bit' (VERR_INVALID_UTF16_ENCODING).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
-----

Simply reverting back to 4.3.6-91406 without any other changes fixed the issues last time and all the VMs run fine but I'd rather stay up-to-date.
What is causing this (note - if it was not already clear - it is NOT just most recent release of vBox (4.3.14-95030) that does this!)

Thanks!

[mpack]

Select a VM, zip up VBox.log file and the .vbox file for that VM and attach the zip here.

[DTMOC]

OK. Done.
(Wanted to include a small video that shows VBox 'reaction' in the ZIP but limit is 512MB)

[mpack]

Well I'm stumped. I see nothing wrong in the .vbox file (e.g. it is not using a UTF16 encoding, and there are no funny characters embedded anywhere), and the log file is more or less useless since it's from VBox 4.3.6 and hence doesn't show an error. In any case it doesn't show any odd paths.

The only other thing it could be complaining about would be the path and/or contents of the VirtualBox.xml file. Does your <userdoc> path have any non-Roman characters in it? Have you ever manually edited the VirtualBox.xml file?

I think you'll need to raise a BugTracker ticket for this one.

[DTMOC]

Appreciate your help.
Honestly - nothing was changed except applying the patch/upgrade, before which it was working.
In fact I had already rolled back before (from 4.3.10-93012 I think) due to same problem but figured the issue would have been resolved by now

VIRTUALBOX.XML
Have never edited the VirtualBox.xml file. In fact I had trouble finding it.
Searched in vBox Programs DIR and in VM DIR.
Then did search of entire system HDD and finally found it!

Path is C:\Users\<username>\.VirtualBox
So path should not be a problem, I presume.

There were other versions of the XML file so I carefully tried a few.
One other worked (showing fewer VMs) but gave same error on startup.
I restored the original XML file and all is back to "normal" (meaning the errors for all VMs)

USERDOC
Unsure of <userdoc> path - that was not a setting in XML file.


I may have to roll back to version that worked (4.3.6-91406) I guess.
Would have liked to have resolved this but do need to use the VMs.

[mpack]

<userdoc> == shorthand for user documents path == where you found .VirtualBox folder and hence VirtualBox.xml.

Path is C:\Users\<username>\.VirtualBox
So path should not be a problem, I presume.

... provided <username> does not contain any non-Roman characters.

If you want this issue to be resolved then someone needs to raise a BugTracker ticket for it. That's generally the only way the devs will ever notice.

[DTMOC]

Ah OK.
Wondered about that and had already checked when I looked at XML.
Paths are OK and are also fairly short.

Thx for tip re: Bug Tracker Ticket.
But for now, I am going to have to revert back to 4.3.6-91406.
Will just post again for the results/status.

[DTMOC]

updating as advised in last post.

Also tried 4.3.14 with AV and Firewall Disabled due to other compaints.
But - no change - Same issue.

So...
Deinstalled 4.3.14
Reinstalled 4.3.6

Works like a charm again for all VMs - just as before!
No changes to any files or config. Just deinstall, reinstall.

Thx for help.
Will hopefully be able to post issue as New Bug.

[socratis]

Could you please do two additional things?

• Just to make sure: Did you see if you can run your VMs with 4.3.12? You might have been bitten by the nasty Windows hardening in version 4.3.14. You mentioned that you tried it but you only have mentioned the .14 and the .6 releases.
• If you filed a bug tracker report, could you post the number so that if someone else finds this thread can follow it?

[mpack]

Well, I went ahead and added to ticket #12842.

Edit:  I don't see how this could be related to the hardening bug. The OP of the ticket first encountered the problem in VBox 4.3.8.

[DTMOC]

Thanks!
DO appreciate that!

FYI - was actually "willing" - just no immediate time!
Have spent enough time on trying to resolve - a couple of times now - and need to do some 'real' work before I pursued an escalation <grin>
Again - Thanks!

[socratis]

@mpack
The OP just mentions 4.3.6 (works) and 4.3.14 (fails). Just wanted to make sure we weren't missing something. But, thanks for posting the ticket (it refreshed my memory, right, it happened at 4.3.8 ), because it leads me to the question:

@DTMOC
Are you running a non-English version of Windows?

[DTMOC]

No - Windows in English.
"Format" and "Location" is set for USA.

[DTMOC]

I guess I can post to my own thread even though it's old. )

Still in the same spot.
Stuck at v4.3.6 with it being the only version that works without the same message already posted.
There mus be an answer to this.

I did try a newer version since last posts hoping it has been fixed - think that may have been v4.3.16 - but results were the same.
I will try the latest released (v4.3.20) and post if it is now OK.

[DTMOC]

Same issue with v4.3.20!
Cannot believe this!!
Guess I need to look to more reliable products.

Socratis was helpful.
Oracle - NOT!

It is inconceivable that v4.3.6 works with no problems and all versions after that do not.
And that going back to v4.3.6 is OK.

Recap
Host OS is capable Windows 7 Pro running on Intel Core I7 2.8Ghz processor with 16GB RAM and lots of HDD space.