Endpoint Protection

 View Only
  • 1.  SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 02:20 PM

    Anyone else run into this problem?

    After installing the new 64-bit SEP 12.1 RU2 on a test Windows 8 computer, I went looking for files and found them under Program Files(x86). I thought maybe I could have exported the x86 setup from SEPM, but Bin64 was there. I uninstalled SEP and deleted all the Symantec folders. Then I exported another package making sure I had the 64bit version selected, and sure enough, it installed into Program Files(x86) again.

    I'm going to give it one more try. I'm going to export a full install rather than the single exe to see if that makes a difference.

    I did do an upgrade on three different computers - XP 32bit, and 2-64bit Windows 7. Their files all landed in the correct folders. This was the first install on Windows 8 from scratch. Wierd. Will update once I get the Windows 8 computer uninstalled/installed - again.



  • 2.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 02:30 PM

    Meant to include a picture, but was too fast with the submit button...



  • 3.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 02:34 PM

    This is normal behaviour. SEP is compatible for 64bit architecture but not all pieces are 64bit.

    See this thread on it:

    https://www-secure.symantec.com/connect/forums/why-64bit-sep-installed-none-64bit-folder



  • 4.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 02:36 PM

    its a native 32 bit application , thats why you will few bits installed in 86 folder.

    SEP is a NATIVE 32 bit application, but on a 64 bit hardware on top of a emulation of 32 bit OS called WOW64. That is the reason SEP client puts its files into C:\Program Files (x86) and not the C:\Program Files.

    When we run a 32-bit program on a 64-bit version , the program runs in a 32-bit emulation mode, using software to simulate a 32-bit version of OS. This allows 32-bit programs to run smoothly on the 64-bit operating system.

     

    https://www-secure.symantec.com/connect/forums/why-64bit-sep-installed-none-64bit-folder#comment-7313341



  • 5.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 03:02 PM

    Yes, I know a few bits should be in Program Files(x86). The majority should be under Program Files for a 64bit OS. That's the way it works on Windows 7. However, that isn't the problem here.

    All of the bits went into Program Files(x86) on my 64bit Windows 8 computer, with one exception. That was a file called sevinst64x86.exe. 

    Installing SEP using a full install also put all of the bits into Program Files(x86) on 64bit Windows 8.

    I spent a lot of time training my desktop support and help desk to look for 32bit apps under Program Files(x86) and 64bit apps under Program Files. I don't want to have to tell them that now 64bit SEP will be under Program Files(x86) for Windows 8 and under Program Files for Windows 7...



  • 6.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 03:11 PM

    Looks like this may be why it messed up on Windows 8...

    There is one issue with file redirection that users and developers should be aware of.

    Many 64 bit applications still use 32 bit installation routines. To ensure that an application is installed correctly, i.e. to C:\Program Files, the installation routine should make an operating system call to temporarily suspend the WOW64 file redirector. After installation another operating system call needs to be made to re-enable the redirector. If this approach isn't followed then the application will be installed to C:\Program Files (x86).

    My guess is that it installed properly on my Windows 7 computers because those were upgrades and it put the bits where they were originally located for RU1 MP1...



  • 7.  RE: SEP 12.1 RU2 x64 Installs in Program Files(x86 ) ???

    Posted Nov 19, 2012 03:20 PM

    Sounds like the issue, this can be disabled:

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa365743(v=vs.85).aspx