Vista x64 on Intel references amd64 architecture, some installers hang

What led me to notice that my computer seems to think that it's amd64 was an installer hang that referenced amd64.  

My first question, is it normal for Vista x64 on an Intel Core 2 Duo to say that it's amd64?
(For instance, when I look in C:\Windows\winsxs\ I see a large number of folders leading off with amd64_...)

Second, this is the installer error that led me to the problem:

Log Name:      Application
Source:        MsiInstaller
Date:          6/10/2008 6:54:59 PM
Event ID:      11935
Task Category: None
Level:         Error
Keywords:      Classic
Description:
Product: Microsoft Visual C++ 2005 Redistributable (x64) -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'. Please refer to Help and Support for more information. HRESULT: 0x800736FD. assembly interface: IAssemblyCacheItem, function: Commit, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}


I haven't found much in the MS KB nor anywhere else I've looked.  Other people are having similar issues, but I haven't found any tried and true suggestions that have worked for me.

Any input is appreciated.
LVL 1
callitAsked:
Who is Participating?
 
andyms56Connect With a Mentor Commented:
hi m8 have a close read of this it may help the last page is very interesting and may be the answer
http://www.vistax64.com/vista-general/83464-problem-installing-microsoft-visual-c-2005-a-3.html
andy
0
 
andyms56Commented:
hi m8 can you open device manager and see what you cpu is listed as all so the C:\Windows\winsxs
folder is the new i386 folder in vista thats wher it holds all the instalation files even if thay are not neaded and a lot of software dll files are put ther as well
0
 
callitAuthor Commented:
To verify, my processor is listed as Intel Core 2 Duo in device manager.  The redistributable however does still reference amd64 in the error though.  I'm not sure if that's related to what's causing the error now though.

I wasn't aware that winsxs is the new i386 folder though, so thanks for that info.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
callitAuthor Commented:
Wow.  I was really hoping to avoid a total system rebuild, but if it has to be done to make my system work as expected, I may have no other choice.  I'm gonna wait a bit and see if anyone else comes through with a suggestion.  If not, I'll have to give that a shot.
0
 
callitAuthor Commented:
I'm in the process of getting some faulty RAM replaced.  It should be here shortly.  I'll report back with my findings.  I still have a feeling a system rebuild going to be needed.
0
 
andyms56Commented:
ok m8 let me now how you get on the ram may be the fulit all so when you next run the setup right click it and select run as admin
andy
0
 
callitAuthor Commented:
I've tried running it as admin too, same problems.  RAM is on its way.
0
 
callitAuthor Commented:
RAM arrived this week.  Will post more once I've had a chance to try windows reinstallation
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.