Opened 11 years ago
Closed 9 years ago
#12892 closed defect (obsolete)
Wrong target path in start menu entries on Windows 7 64-bit
Reported by: | GuidoK | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 4.3.10 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
On Windows 7 64-bit virtualbox is installed to "c:\Program Files\Oracle\VirtualBox"
Start menu entries are generated in "c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle VM VirtualBox"
If I check the properties of the LNK file in the start menu folder the target of the start menu entry points to "c:\Program Files (x86)\Oracle\VirtualBox"
This occurs if I use a 32 bit application to show the LNK properties, e.g. total commander. This application opens the common file properties dialog, but it seems that the contents depends on the calling application.
Example: Show properties of file "c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle VM VirtualBox\Oracle VM VirtualBox.lnk"
The target points to "c:\Program Files (x86)\Oracle\VirtualBox\VirtualBox.exe"
The working directory points to "C:\Program Files\Oracle\VirtualBox\"
This is quite strange, because I didn't see any "(x86)" in the lnk file when I check it with an editor.
Furthermore if I show the properties of the start menu entry using the start menu > All programs > Oracle VM Virtual Box > Oracle VM VirtualBox, right-click > properties I see the correct entries, thus no (x86).
The different targets result a problem if I use a tool that reads the properties of the lnk file, e.g. an application launcher.
I tested the behaviour on Windows 7 Professional, last updates installed, german localization. No changes regarding UAC since installation of Windows 7.
It seems that is caused by the different handling of the targets depending of the environment (32 vs. 64 bit).
Is it possible to set fixed paths during installation and generation of the LNK files?
Please reopen if still relevant with a recent VirtualBox release.