PDA

View Full Version : AdAware Problem



SurferJoe46
17-03-2007, 05:54 PM
Getting this error code (http://www.imagef1.net.nz/files/adaware.jpg) for the installation of Ad-Aware..any ideas? :badpc:

dolby digital
17-03-2007, 06:09 PM
Getting this error code (http://www.imagef1.net.nz/files/adaware.jpg) for the installation of Ad-Aware..any ideas? :badpc:

Sorry, are we your Support Personell (or your package provider) :eek:

Maybe the download corrupted itself.

SurferJoe46
17-03-2007, 06:28 PM
Well..yes! actually!

I keep on getting this when I try to re-install what used to be existing on my desktop..and I have several other friends with the same error message too...just thought it might've been a resolved problem there...guess not.

Speedy Gonzales
17-03-2007, 06:54 PM
Try reinstalling Windows Installer.

If you're using XP (http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en)

If you're using 2000 SP2 and under (http://www.microsoft.com/downloads/details.aspx?familyid=4B6140F9-2D36-4977-8FA1-6F8A0F5DCA8F&displaylang=en")

Or 2000 SP3 + (http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en)

SurferJoe46
18-03-2007, 03:45 AM
Well...I found out it's a WGA snafu..and it has triggered a fault in the Windows Installer Service (WIS)..to which M$ has issued the following instructions for XP, where they say this:

You may receive Error 1721 when you try to remove programs by using Add or Remove Programs in Windows XP

The instructions for repairing it require a little Command activity, and here's the list of destructions:

How To Reregister the Windows Installer service

1. Start your computer in Safe mode. To do this, follow these steps:

a. Restart the computer.
b. After the BIOS information is displayed, press F8.
c. Use the DOWN ARROW key to select Safe Mode, and then press ENTER.
d. Use the UP ARROW key and the DOWN ARROW key to select your computer, and then press ENTER.
2. Log on to the computer as local administrator.
3. Click Start, click Run, type cmd.exe, and then click OK.
4. At the command prompt, type msiexec /unregister , and then press ENTER.
5. At the command prompt, type msiexec /regserver, and then press ENTER.
6. At the command prompt, type exit, and then press ENTER to close the command prompt.
7. Remove the software program from Add or Remove Programs.
ME HERE: I am not sure WHAT software they refer to here..the one we just installed in the C-prompt or the offending software that bollixed up the computer in the first place..oh, well!

Then, Run The System File Checker


The System File Checker (Sfc.exe) utility is used for scanning protected operating system files to verify their version and integrity. If System File Checker detects any operating system file with the incorrect file version, it replaces the corrupted file with a file that has the correct version from the Windows installation source files.

To use System File Checker, follow these steps:
1. Click Start, click Run, type cmd.exe, and then click OK.
2. At the command prompt, type sfc /purgecache, and then press ENTER.


Note You may be prompted to provide Windows installation source files (your Windows Installation Disc) when you run the sfc /purgecache command.

If the command is completed successfully, you will receive the following message:


Windows File Protection successfully made the requested change.

3. At the command prompt, type sfc /scannow, and then press ENTER.


Note This command may take several minutes to finish. You may also be prompted to provide Windows installation source files (your Windows Installation Disc) when you run the sfc /scannow command

4. At the command prompt, type exit, and then press ENTER to close the command prompt.
5. Remove the software program from Add or Remove Programs. AGAIN: I am not clear on WHAT software program they mean here..if someone knows for sure, let me know too. How would we know what program did the damage?

It seems as though a file gets left open when WGA looks at it, and then when you shut down and reboot, that file is corrupted. The end-run program cannot pick up on the open file and just forgets to close it when you shut down....so there.

I had hoped it was a little simpler than this..but thanks Sir Speedy for the goad to get it fixed.