Windows 7: Installing MSI packages

My downloads folder is located on my drive D (non-sytem) storage drive. Everytime I download an MSI package installer, it does not want me to install it if I run that installer from drive D. But as soon as I transfer that file in drive C and run it from there, it works fine. Is this normal behavior? If so, why?

Thanks.

It doesn't "want" you to install...what do you mean by "want"?

Running the program will give me the installer screen just fine but when the installer already installs the actual files, it says "file not found" or something along those lines. It is different for every different msi package but it always give me an error. As soon as I transfer that file from my drive D to drive C, everything works fine.

Is the C drive another physical disk or partition of C?

Can you post a screenshot of the actual error?

Screenshots and Files - Upload and Post in Seven Forums

A Guy

Drive C is an SSD and drive D is a mechanical drive so yeah two separate physical disks.

I will when I go home tonight. But as i've said the errors are different for each MSI package. Is this not normal?

I'm not sure, a lot will depend on how the installer is written, and where it wants to write it's temp files. the exact error(s) may just help. A Guy

Alright. But I'm sure that when I install the physx package there was a "file cannot be found" error. What's so special in an MSI package that other normal installers don't have?

It is just a type of installer, but it uses a package approach

What Is MSI Installer? | eHow.com

Windows Installer - Wikipedia, the free encyclopedia , read the section under key paths.

A Guy

Here ya go, the screenshot. Now, I noticed something. As I've said I run that under the directory D:/Users/Kevin/Downloads because I "moved" the location of my Users directory from drive C to drive D using by changing the properties (right-click) of each Users folder. I then tried moving the MSI installer at the root directory of D:/ and it surprisingly worked. It also works at drive C. Does this mean that the problem exists only when I run it from the Users folder?