locked
Shortcut to IE9 32-bit points to homedrive instead of c:\program files (x86) on Win7 x64?? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Strange problem here. We are deploying Win7 SP1 x64 using SCCM OSD. In the base image i've included the IE9 installation. When deploying this image and logging on for the first time the shortcut to the 32-bit IE9 points to H:\Program Files\Internet Explorer\iexplore.exe instead of to C:\Program Files (x86)\Internet Explorer\iexplore.exe

    I've observed the following:

     

    • The driveletter of this users homedrive is H:
    • When logging on with a local user account (administrator) the shortcut is fine!
    • the folder on H: does not exist
    • x64 IE shortcut works fine

    What could be causing this issue?

     

    Thursday, March 17, 2011 7:37 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

     

    I experienced this same issue. I resolved it by extracting the cab files from IE9 installation exes and applying them using dism

     

    For 32bit

    Create a program with command: dism.exe /online /add-package /PackagePath:"<pathto32bitcab>\IE9-Win7.CAB" /IgnoreCheck /norestart

     

    For 64bit

    Create a program with command: C:\Windows\sysnative\dism.exe /online /add-package /PackagePath:"<pathto64bitcab>\IE9-Win7.CAB" /IgnoreCheck /norestart

    Or use "Disable 64-bit file system redirection" if ran from Run command Line so that 64bit dism.exe is used from real C:\Windows\system32 rather than the one in C:\Windows\SySWoW64

     

    This is a workaround and it works. No idea why this happens... I was pretty amazed by this myself.

     

    TJ

    • Proposed as answer by Miya Yao Friday, March 25, 2011 8:18 AM
    • Marked as answer by Nicholas Li Thursday, March 31, 2011 6:42 AM
    Friday, March 18, 2011 1:39 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

     

    I experienced this same issue. I resolved it by extracting the cab files from IE9 installation exes and applying them using dism

     

    For 32bit

    Create a program with command: dism.exe /online /add-package /PackagePath:"<pathto32bitcab>\IE9-Win7.CAB" /IgnoreCheck /norestart

     

    For 64bit

    Create a program with command: C:\Windows\sysnative\dism.exe /online /add-package /PackagePath:"<pathto64bitcab>\IE9-Win7.CAB" /IgnoreCheck /norestart

    Or use "Disable 64-bit file system redirection" if ran from Run command Line so that 64bit dism.exe is used from real C:\Windows\system32 rather than the one in C:\Windows\SySWoW64

     

    This is a workaround and it works. No idea why this happens... I was pretty amazed by this myself.

     

    TJ

    • Proposed as answer by Miya Yao Friday, March 25, 2011 8:18 AM
    • Marked as answer by Nicholas Li Thursday, March 31, 2011 6:42 AM
    Friday, March 18, 2011 1:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Would any of you know how to install ie9 into a different directory?
    Friday, March 25, 2011 5:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I've got exactly the same problem, followed your instructions above which complete sucessfully, but I still have the problem with the shortcut pointing at the home drive, even after a restart.

    Is there anything else I should be doing?

    Cheers

    Adam.

    Monday, August 29, 2011 8:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We have this exact same problem when deploying IE9 via WSUS to Win7 x64 mahines.  It is picking up the homedrive path for some reason and changing the shortcut.  Better yet when we logon as a different user on that machine we only see "Internet Explorer" in the Start Menu and the path points to the 64-bit version.  We need to create a new shortcut pointing to the x86 path.  This is a huge problem for deploying IE9 in a WSUS environment.
    Rob Pettigrew
    Wednesday, September 7, 2011 8:48 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We have the same problem deploying IE9 via WSUS on Windows 7 X64 SP1.  IE x32 shortcuts points to homedrive.

    We had found the following solution that worked in our environment.

    We created computer group policy preferences to delete the following registry values if exist.   It fixed IE9 x32 icon.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components]
    "NoIE4StubProcessing"

    and

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce]
    "NoIE4StubProcessing

    http://support.microsoft.com/kb/2642824


    • Proposed as answer by Marina Velent Wednesday, July 18, 2012 10:16 PM
    • Unproposed as answer by Marina Velent Wednesday, July 18, 2012 10:17 PM
    • Edited by Marina Velent Wednesday, July 18, 2012 10:43 PM
    • Proposed as answer by Marina Velent Wednesday, July 18, 2012 10:43 PM
    Tuesday, July 17, 2012 2:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I recently learned that some of our users were having this same problem.  Since I deleted all the SP1 backup files, uninstalling IE9 wasn't an option.  The work-around I found is to run the "show" icons command on login.  

    In <default user hive>\Software\Microsoft\Windows\CurrentVersion\RunOnce

    REG_SZ "ieicons"

    value "C:\windows\system32\ie4uinit.exe -show"

    I still don't know why (or from where) the incorrect icon is being created.  I can delete all the icons from my default profile start menu and from the all users start menu, but the icon pointing to the user's home drive is still created on the first login.  Running "ie4uinit.exe -show" seems to 'fix' it every time.  I didn't have any of the NoIE4StubProcessing registry keys, and no other obvious run/runonce/run at startup processes to create the icon.  Must be buried deep in the Microsoft pixie dust that makes everything "just work"


    • Edited by indyogb Wednesday, August 15, 2012 4:45 PM
    Wednesday, August 15, 2012 4:11 PM