DjLizard

yes

To make CCleaner execute automatically/silently, do CCleaner.exe /AUTO. To run it every time you log in, throw a shortcut in your Startup folder. To make it work on every person's login, throw it in the common startup folder (\Documents and Settings\All Users\Start Menu\Programs\Startup) and for a desktop icon for all users, throw the shortcut on the common desktop (\Documents and Settings\All Users\Desktop)

Symantec usually uses the Microsoft Installer system. There is nothing wrong with any of the aformentioned installer systems, except when people write shoddy scripts, such as Symantec has. Norton-products have file and registry permissions problems, shared DLL problems, WMI problems, and since it uses the IE core it then can have ActiveX problems, WSH problems, Zone problems, etc... there's an unlimited number of ways to ruin a Norton installation/uninstallation.

Ok that's just plain absurd.

zaphirer: you have another issue... Firefox doesn't just do that. Check your extensions. Run firefox by typing "firefox -safe-mode" in the Run... box (or click the Firefox (Safe Mode) icon in the start menu)

And Not Every Word Needs To Be Capitalized

Now how come I didn't even remember to hit the report button?

You finally made it. (Hey, I hope you cleaned up that dark guy's junk posts.) Took you long enough to notice this is a junk thread

MrG said it is fixed in the upcoming release.

My XP machine at home has been on (and under heavy use) for 3 weeks and 4 days without a reboot.

I concur

I concur

Awesome, MrG!

We're sorry we didn't get to your message sooner (it seems I missed it completely). You get this error consistently how? What's common on all your OSes that aren't on mine, for instance? I use CCleaner on 20+ machines per week, and haven't seen this one yet. I'd have to assume that there is either a corrupt registry entry, or an illegal character is in an entry that CCleaner can't handle (some nulls, some low ascii, and whatnot), or maybe it's not that simple. ejohnson and Syphus, please describe exactly the procedure to reproduce this error. Include any relevant details about your operating system, internet explorer, firefox (if applicable), the registry keys and/or values in question, etc.

Please read: http://www.safer-networking.org/en/faq/6.html

R.I.P. These threads are dead DRVTACH, if you'd read them you'd have noticed we've posted the solution several times throughout this page. (You attacked me in another thread for supposedly not *reading*, yet here you are, not reading). Sun Java is not Javascript is not a GIF is not a Flash animation

speak for yourself

Yeh, I guess "hackers" could get in if I didn't keep Windows up to date. I don't use a firewall (except the Windows internal one) and I leave myself on the DMZ of my router (I hate restricted access).

Thought this was XP... ?

?_?

In the other thread where this was asked, I ruled quite the contrary. Over the course of 10 years, I've determined [by observation and trial/error] that leaving my computer(s) on 24/7/365 has proven more beneficial than to those [my customers] who have not. My customers have purchased nearly identical class hardware, and reside in a nearly identical class of temperature, humidity, pollutants, and other environmental factors as I do. I have discovered that while that article is very factual in nature, it is not as cut and dry as listed above. Ways to beat the odds: 1) Have a UPS system. You should get a UPS system. I don't have a UPS system [yet]. I get hit by power spikes/sags/outages. My power supply is above-grade [$150 Antec NeoPower), it doesn't die. It is not a Powmax ($2 ) power supply. 2) Have an air ionizer. I don't have an ionizer. I smoked. Doral lights. One day, (after 730 days of continuous computing/smoking), I decided to shut down and clean out my case (using a nice 90 psi air compressor), but to my amazement, there was nothing to clean. I don't understand... I quit smoking recently, just after I bought the parts for my new computer. This computer attracts loads of dust... 3) Keep it off the carpet. Keep it off the floor. Luckily, mine is precariously perched atop a rickety end-table that weighs less than half of what my PC weighs. 4) Keep it cool. You shouldn't buy a crappy case. You should buy a nice cool Antec case, and load it up with Antec brand 120mm case fans Your CPU should have a full on copper block with a hefty high speed fan that should not be throttled to lower speeds according to the temperature of your system. These parts were designed with a heat yield, and were designed to always be running. 5) Remember the "lightbulb principle". A lightbulb runs for several hours, then you finally turn it off. You do this day in and day out. One day, right when you turn it on, it pops. How come it never pops when it's already on? Thermal expansion. They last longer when they just stay on all the time. They are low wattage. Your computer is not! Do the math. 6) Hard drives don't like power-offs (they have to park, and why isn't there ever any place to park! lots of handicap spaces though), and are also heat yield-certified. They are designed to run a certain RPM, a certain temperature all the time, for a certain amount of hours. Cool them off and they run even longer. Stop defragmenting every week and maybe they wouldn't wear out so much. The PC I had before this one had the following things happen over the course of its life (btw, it hasn't died yet) : A) 7 capacitors total on the board had blown, and were leaking spent electrolyte, over the course of 5 years -- still works to this date I accidentally "missed" when I later connected a floppy drive power plug... 5v to ground = toasty to the power supply -- still works C) Video card fan's ball-bearing warped/seized (GeForce 3 (not a Ti)) - it was one of those paper-thin ones from back in the day. I noticed it about 2.5 years after I built it -- not sure how long it'd been dead -- so I zip-tied a northbridge chipset fan to it (because I broke off the video card's pegs, heh) D) I had three hard drives stacked on top of each other with no fans on them, because, well: E) I had no case fans. It still works, but I wanted a motherboard with SATA, dual-channel 400MHz RAM support, etc, so I built the one I'm on now. I retired the old beast's carcass into the closet. I think I was just lucky in all that (and it was a cheap computer) but the computer I have now is going to last a long while (it has many fans and a lot better things going for it - DjLizard, also CompTIA A+ certified. Missed 1 question between the two tests. Probably SCSI-related. PS: My current uptime: 3wks 4hrs 43mins Usual reboot reasons are: fiancee, "you must restart your computer" because I installed some hax0r driver, windows updates, blah blah etc.

Ok, I have a better idea. (I missed the 'system32' on step 1') 1) Start, Run... CMD 2) %systemdrive% 3) cd \ 4) cd %systemroot%\system32\drivers\etc 5) attrib -r -h -s hosts 6) del hosts

Steve: That last part you have to type as you see it. Click start, click on Run..., and type CMD, and hit enter. When the Command Prompt window appears, you type each line and hit enter: CD %systemroot%\drivers\etc ATTRIB -R -H -S -A HOSTS DEL HOSTS ---- The name servers (202.188.0.133 | 202.188.1.5) are OK. They resolve addresses to IPs and vice versa. You can use the command NSLOOKUP in Windows XP to access the nameserver. Each time you connect to, say, 'www.google.com', your nameserver looks it up -- here's what my output looks like from CMD: Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.C:\Documents and Settings\DjLizard>nslookupDefault Server: tampfldns08-amp.tampabay.rr.comAddress: 65.32.2.147> www.google.comServer: tampfldns08-amp.tampabay.rr.comAddress: 65.32.2.147Non-authoritative answer:Name: www.l.google.com[b]Addresses: 64.233.161.147, 64.233.161.99, 64.233.161.104[/]bAliases: www.google.com At any rate, yeah, you wouldn't technically be able to access the internet, except by IP address, so don't remove the nameserver entries (when I give Windows custom nameservers, hijackthis says they're removable as well -- it's normal). Tarun must have been sleepy, because you shouldn't remove that Tarun - I also doubled up on the 'safe to remove' text in your program, sorry, haha (I'm sure you can fix it now). (Domain hijack, safe to remove. Safe to remove:) Change the wording to 'Custom nameserver, not recommended to remove' or something.

Nope, and I DON'T recommend turning the thing you just mentioned off (it's not related - the system log = event viewer\system). If you really don't want dumprep, disable error reporting (on the same page as Startup and Recovery Settings) - I DO NOT RECOMMEND DISABLING ERROR REPORTING. Error reporting has given me perfect solutions to problems I've had in the past (both on my own machines and my customer machines). It also helps Microsoft collect aggregate crash data, to see how many people are affected by a given problem (the more error reporting everyone does for a given crash, the more priority it will get, and it will get fixed faster - so report those errors!) -u means usermode and -k means kernel mode a driver blows up, you get a -k Iexplore blows up, you get a -u if error reporting failed, sometimes it gets stuck as a startup entry (it's supposed to say Windows has recovered from a serious error, etc)

O4 - HKLM\..\Run: [userFaultCheck] %systemroot%\system32\dumprep 0 -u ^^ This item is safe to remove using HJT, and usually won't come back, unless you get another 'serious error' from Windows to report. O4 - HKCU\..\Run: [MsnMsgr] "C:\Program Files\MSN Messenger\MsnMsgr.Exe" /background ^^ This one usually comes back, unless you do what Tarun said, which is "using the GUI", which actually means to use the appropriate interface for disabling MSNM startup, which is: With MSNM running, go to Tools, Options, Preferences (or in MSN 7, "General"), and uncheck "Automatically run messenger when I log on to Windows" You should simply delete your hosts file and start it over. 1) Start, Run... CMD 2) CD %systemroot%\drivers\etc 2) ATTRIB -R -H -S -A HOSTS 3) DEL HOSTS Then run spybot s&d, go to advanced mode, then Tools, then checkmark Hosts file, then click the button to "add spybot s&d's hosts file"