| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 77649 | 2007-03-17 04:54:00 | AdAware Problem | SurferJoe46 (51) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 533808 | 2007-03-17 04:54:00 | Getting this error code (www.imagef1.net.nz) for the installation of Ad-Aware..any ideas? :badpc: | SurferJoe46 (51) | ||
| 533809 | 2007-03-17 05:09:00 | Getting this error code (www.imagef1.net.nz) 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. |
dolby digital (5073) | ||
| 533810 | 2007-03-17 05:28:00 | 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. |
SurferJoe46 (51) | ||
| 533811 | 2007-03-17 05:54:00 | Try reinstalling Windows Installer. If you're using XP (www.microsoft.com) If you're using 2000 SP2 and under (www.microsoft.com) Or 2000 SP3 + (www.microsoft.com) |
Speedy Gonzales (78) | ||
| 533812 | 2007-03-17 15:45:00 | 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 . |
SurferJoe46 (51) | ||
| 1 | |||||