• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

[SOLVED] Installed apps show incorrect program files shortcut

L

Lefteris

Contributor
Joined
Feb 11, 2017
Posts
46
Hi

I use Windows 7 x64 and when I install a 64 bit program, the Start menu shortcuts, always point to (x86) program files, which should be "Program Files" not "Program Files (x86)".
The applications and their files though are installed correctly in "Program Files"
Capture.JPG
Also 32 bit apps when I start to install them, instead of showing the correct C:\Program Files (x86) folder, it shows the C:\Program Files in the installer.

My registry seems ok
Capture1.JPG
Any help?:huh:
 
Hi Lefteris. :wave:

Try this command from a command prompt (normal or elevated):
dir "%programfiles%" /a-d && dir "%programfiles(x86)%" /a-d
Click to expand...
I get:
Volume in drive C is Packard Bell
Volume Serial Number is E292-2F1C

Directory of C:\Program Files

18/03/2017 23.01 174 desktop.ini
1 File(s) 174 bytes
0 Dir(s) 47.611.183.104 bytes free
Volume in drive C is Packard Bell
Volume Serial Number is E292-2F1C

Directory of C:\Program Files (x86)

18/03/2017 23.01 174 desktop.ini
1 File(s) 174 bytes
0 Dir(s) 47.611.183.104 bytes free
Click to expand...
 
Hi xilolee thanks for replying :s4:

I get
Volume in drive C is SYSTEM
Volume Serial Number is 548D-C8B8

Directory of C:\Program Files

19/02/2017 09:18 μμ 174 desktop.ini
1 File(s) 174 bytes
0 Dir(s) 40.860.749.824 bytes free
Volume in drive C is SYSTEM
Volume Serial Number is 548D-C8B8

Directory of C:\Program Files (x86)

19/02/2017 09:18 μμ 174 desktop.ini
10/01/2015 10:00 μμ 1.680 Global.sw
25/01/2016 06:14 μμ 707.397 is-6CMBL.tm
28/01/2016 07:58 μμ 312.451 unins000.da
28/01/2016 07:58 μμ 722.680 unins000.ex
28/01/2016 12:26 πμ 231.918 unins001.da
28/01/2016 12:24 πμ 707.397 unins001.ex
14/10/2013 11:13 μμ 53.288 unins002.da
14/10/2013 11:12 μμ 707.299 unins002.ex
16/07/2015 11:51 πμ 248.035 unins003.da
16/07/2015 11:49 πμ 722.711 unins003.ex
11 File(s) 4.415.030 bytes
0 Dir(s) 40.860.749.824 bytes free
Click to expand...

Also when I run "set" in cmd I get

ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
Click to expand...
 
Try this:
dir c:\pro* /a
Click to expand...
I get:
Code: 
 Volume in drive C is Packard Bell
 Volume Serial Number is E292-2F1C

 Directory of c:\

30/06/2017  22.03    <DIR>          Program Files
05/08/2017  21.51    <DIR>          Program Files (x86)
30/07/2017  10.19    <DIR>          ProgramData
10/03/2013  21.06    <JUNCTION>     Programmi [C:\Program Files]
               0 File(s)              0 bytes
               4 Dir(s)  47.711.305.728 bytes free
 
Volume in drive C is SYSTEM
Volume Serial Number is 548D-C8B8

Directory of c:\

27/08/2017 12:53 μμ <DIR> Program Files
27/08/2017 12:58 μμ <DIR> Program Files (x86)
23/08/2017 08:14 μμ <DIR> ProgramData
0 File(s) 0 bytes
3 Dir(s) 40.888.172.544 bytes free
Click to expand...
 
This problem is not solved! Who changed the topic? Did I say it's all ok? :omg:
Can a real technician please help me?
 
  • Open notepad.
  • Paste the following lines in it.
    Read More:
  • Save the file on your desktop as export.bat (or the name you prefer).
  • Right-click the new file and click run as administrator.
  • Then you should find the exported registry strings in 8 files on your desktop.
  • Zip them (as link.zip, or the name you prefer) and upload/attach the file here.
 
I found a correct registry and I fixed all but one problem. Individual 32 or 64 bit installers now install shortcuts correctly and show in installer the correct Program Files folder.
But when I have a mixed 32/64 bit application, which includes both 32 and 64 exes, the installer always points to Program Files (x86), which is a problem because even if I correct it manually, it will install the 32 bit part of the application, not the 64 bit which I need. Seems that windows can't see 64 application in mixed installers at all.
I tested with 3 mixed installers, FoxitReader832, ashampoo_winoptimizer_15_15.00.05_sm and Total Security 360TS_Setup_9.2.0.1164
 
I've just checked foxit reader installer: default path is C:\Program Files (x86)\Foxit Software\Foxit Reader.
I've just checked 360 total security installer: default path is C:\Program Files (x86)\360\Total Security.
I have got the giveaway version of winoptimizer 12: it's installed in D:\Program Files (x86)\Ashampoo WinOptimizer 12 (default was in c:).
I don't think they changed the default path.

Maybe you don't have the problem anymore.
Did you re-try cpuid installer?
 
Do you have windows 32bit? Because these paths are 32 bit and these installers are mixed, so they saw your os and showed these paths. Its not fixed for me because foxit for example has a 64 edition exe which is not installed when I let the installer run and its in x86 dir, but even if I edit the dir without x86 I still get 32 bit foxit.
I did retry cpuid and its working but I told you that individual installers are fine. Mixed ones have the problem. Please reread my previous post.
 
I've got Win10 x64.

Its not fixed for me because foxit for example has a 64 edition exe which is not installed when I let the installer run and its in x86 dir, but even if I edit the dir without x86 I still get 32 bit foxit.
Click to expand...
Could you post the link to it?

From foxit forums - Is FoxIt a Native 64-bit Application? (click), Lisa_lee, foxit forum administrator, said:
Currently the main program in Foxit PhantomPDF/Foxit Reader installer is still a 32-bit program, only the Foxit PDF printer part is 64-bits.
Simply speaking, it is a 32-bits application with a 64-bits virtual printer. That is the reason why it installs in the Program Files (x86) directory.
Click to expand...
 
It seems I was wrong... The link is this but it doesn't matter now http://cdn01.foxitsoftware.com/pub/.../8.3/en_us/FoxitReader832_enu_Setup_Clean.exe
I found a pc with windows 7 x64 at work and foxit installer and Total security both showed (x86). Maybe I'm losing my mind but it seems that it is fixed and I thought that foxit was a 64bit application... Perhaps the error in the registry that I had all the previous time, is the key in all this because it showed always Program Files without (x86) and it made me think that it was 64bit. Thanks for your help xilolee. :hug:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top