Can't install FF7 on windows 7 64 bit

[Strini]

I've been hunting around for a fix to this, and I'm at a loss. I'm installing via ISO mounting and every guide and FAQ etc seems to jump right past my problem (which isn't an uncommon one from what I've seen) but I just flat out can't get the install to work. I mount the install disc, run the setup file (which opens with no issue) then I click Install, and the setup window closes, my mouse shows the working symbol for a few seconds then stops. That's it, nothing else happens, it never installs, no error. I go into task manager and it shows a setup.exe as running, and the description says 32 bit setup. I'm assuming this is my problem? Is there any way to make a 32 bit setup run on a 64 bit windows 7 system? I'm sort of new to this so I'm not sure if I did something wrong but I can't seem to find a fix for it.

Also if I end the task it usually pops up saying the program probably didn't install correctly.

[FeliX Leonhart]

Restart your PC, and run the setup just after windows is loaded.

[Strini]

Restart your PC, and run the setup just after windows is loaded.

sigh.... thanks haha

[xWHEATiiZ]

haha same problem but all i had to do was close crome 

[sky_wingace]

I am having the same problem I already tried restarting my computer and then installing, I made sure that all other programs were closed and still I have the same problem.

[Covarr]

The problem, as far as I can tell, is related to Google Chrome. The latest version will probably exacerbate it, since it now starts with Windows and runs in the background. Check your system tray by the clock, and see if Chrome is running in there.

Alternatively, just install the thing in safe mode. It works fine there.

[antd]

I just suffered from this issue. However, I did not install Chrome.
Instead the issue was caused by Visual Studio Ultimate.

[Walter253]

What the point with Chrome? It can actually break some .exe ?
signed: a Chrome-User a little worried : x

[insidious611]

At the risk of being too technical, I'd imagine because of issues with far-flung pointers we've had with FF7 in the past, it's something where the installer is trying to read memory addresses it shouldn't be trying to read, the same memory addresses Chrome is coincidentally using. Which, Chrome, being heavily multithreaded, has a tendency to put itself all over your RAM. So no, it's not really "chrome messing things up" per se.