Corrupt file C:\Program Files(x86)

Question

I bought an Asus a few months ago, Recently I have been getting this message about this file, the main program affected is Windows office (2007) is not working and is acting like it was uninstalled when it starts to reinstall it has a fatal error         (8330). I have tried to uninstall windows and have it run in C:\Program files (not x86). Also Chkdsk is not running for me it states that too many programs are running and to run upon next start up, however it does not run. 

Microsoft seems to be the only thing actually affected, however with other programs I open them, and a bubble in the lower left hand corner opens stating that that file is corrupt in the (x86) file but still opens. It seems like most everything is duplicated between C:\Program files and C:\Program files (x86).

Can anyone help???

Answer 1

Often the reason for verification failure maybe a failing hard drive, or running other programs, such as your anti virus software, at the same time as the SFC.

Try SFC from a clean environment by stopping third party programs and services from running.

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP

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

How to troubleshoot a problem by performing a clean boot in Windows Vista

http://support.microsoft.com/default.aspx/kb/929135

Answer 2

To THE C.

It gets to 69% verification and then states that it could not perform requested verification.

will try linney's idea

Answer 3

Have you tried running it (ChkDsk) out of the Windows environment?  If you have an install DVD that you can boot to (or a Startup Repair option via the F8 Safe Mode screen), try launching the Command Prompt from the options provided when you go down the Startup Repair path.  Use the Command Chkdsk c:  /r  (or the drive you want)

Do not perform the Startup Repair, just look for, and go to the option for the Command Prompt (from the Choose a Recovery Tool dialog), and try running Chkdsk from within that.

Startup Repair: frequently asked questions

http://windowshelp.microsoft.com/Windows/en-US/Help/5c59f8c1-b0d1-4f1a-af55-74f3922f3f351033.mspx#EHF

How to use the Command Prompt in the Vista Windows Recovery Environment

http://www.bleepingcomputer.com/tutorials/tutorial147.html

Answer 4

Hello mrsyellowduck,

To help resolve this issue, use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps:

1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As Administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2. Type the following command, and then press ENTER: sfc /scannow (yes there is a space after sfc) The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

Hope this helps you. Let us know either way. Make it a great day!

---

"And In The End The Love You Take, Is Equal To The Love You Make" (The Beatles last song from thier last album, Abbey Road.)