Jump to content

DjLizard

Sponsor
  • Content Count

    273
  • Joined

  • Last visited

Everything posted by DjLizard

  1. DjLizard

    DAF

    Open Task Manager (control+shift+escape), go to the Processes tab and click "Show processes for all users" which will elevate Task Manager to admin. Then click File > New Task (Run)... and type CMD in the box and hit OK. Close task manager. From the elevated command prompt type all of the following: net stop cryptsvc net stop bits net stop wuauserv regsvr32 cryptdlg regsvr32 cryptui regsvr32 cryptext regsvr32 dssenh regsvr32 mssign32 regsvr32 mssip32 regsvr32 scecli regsvr32 softpub regsvr32 rsaenh regsvr32 winhttp regsvr32 wintrust regsvr32 licmgr10 regsvr32 wucltux regsvr32 wuapi regsvr32 wups regsvr32 wups2 regsvr32 wuwebv rmdir /s /q %systemroot%\system32\softwaredistribution net start cryptsvc net start bits net start wuauserv Then try Windows Update again. Dial-a-fix will not be ready for Vista for several more months.
  2. Apparently the solution to this is supposed to be this KB article, which looks exactly like what we're already doing - Dial-a-fix registers those DLLs, and we tried reinstalling the XML parsers and stuff... but you should probably run through the steps in that KB just in case. Try this first, though: rename C:\WINDOWS\System32\spupdsvc.exe to spupdsvc.old and then try again. If all else fails, go here: http://support.microsoft.com/common/international.aspx and select your locale and then contact support. Support for security patches is free, and Microsoft PSS is actually pretty good (they even recommend Dial-a-fix quite frequently :cool:
  3. I've been getting the MSXML3 error a lot - it turns out that if you run Dial-a-fix again, it doesn't happen and everything is fine. I'll fix this in the next version of DAF. For the "marked for deletion" error, that just means you should restart your computer. After restarting, be sure to run the same sections in Dial-a-fix again to put everything back. Then try Windows Update again. A future version of Dial-a-fix will handle these things more gracefully.
  4. You're burning the CDs wrong, I believe. If you see caldera then you've enabled Nero's floppy drive bootable emulation stuff. Don't choose to make a bootable CD compilation at all. Open Nero, close any sub-window it opens (such as New Compilation), and click Recorder on the top pull down menu and choose Burn image...
  5. That's what I said, an inpage error That error code is not anyone's friend (but err.exe is mine). I know it doesn't guarantee that hardware is/has failed, but it's too frequently corrupted files from bad sectors or controller errors that start the issue in the first place. At least, on my bench. I get a lot of end-user computers which are mini biodome ecosystems of problems and mayhem. :cool:
  6. One of the things Dial-a-fix does is run ie4uinit.exe which changes that value Spybot is complaining about. I'll probably change this to be more prominent (as in the user decides whether Dial-a-fix runs this) in the next version. The ie4uinit repair has its merits so I left it that way and figured nobody would notice :cool:
  7. I haven't watched the video (will when I get home) but the comments to the article are quite surprising: not only are they not retarded comments (like found on YouTube and most sites) but most of them have a point (many had quite a few points, such as CBC bias). Anything you get repaired has sectors of the industry like this. A few companies suck and a few companies don't.
  8. Ah. Well Dial-a-fix neither links to or comes with a "cus.exe", and like I said, a cursory Google search seems to imply it's a virus. All I do every day is remove viruses from people's computers (I'm a bench technician) and most antiviruses fail at catching most attacks. I wish antivirus programs were more effective, but then viruses would become more effective. I'll never catch a break. Find the file cus.exe, and see if you can upload it to http://virusscan.jotti.org (which seems to be down at the moment - try again later). Get second opinions by scanning your system with avast!, Avira Antivir, Spybot Search & Destroy, and also try Malwarebytes RogueRemover just in case. (Google each of them to find them).
  9. Load what? Dial-a-fix? If this is not Dial-a-fix related, please register and post in the appropriate technical support forum (which is here: http://lunarsoft.net/forum/index.php?showforum=14). When you post there, please include as much relevant information as you can, such as your operating system version and service pack level, what antivirus/firewall software you are using, how you think the problem began, and steps you've taken to try to resolve it. If this is regarding Dial-a-fix, you can be assured that cus.exe is not part of Windows nor Dial-a-fix, and may be a virus. From a cursory google search, it does appear that cus.exe is a virus.
  10. Start > Run > eventvwr.msc Right-click on System, and choose Save Log File As..., save it as "Event Log (*.evt)" type and upload it to a file sharing site somewhere and then provide a link to it. Do the same thing for the Application event log. While you're uploading stuff, also upload C:\WINDOWS\windowsupdate.log. Be sure not to upload the one with the space in it ("windows update.log") which is not the right one.
  11. Test your memory and hard drive before doing anything else. The error code c0000006 is an "in-page" error which generally means either memory or hard drive problems. MEMORY TESTERS: http://memtest.org/ http://oca.microsoft.com/en/windiag.asp Let them run for several hours. HARD DRIVE TESTS: If you are a bit savvy, you can try my article: https://wiki.lunarsoft.net/wiki/Data_recovery 1) Download the RIPLinux live CD described under "Tools required" and burn it to a CD 2) Boot to the CD, login as root 3) fdisk -l (that's a lowercase L) 4) Find your hard drive and use smartctl and badblocks on it, as described in the article If you are not savvy or do not feel like learning all of this stuff I suppose you could use Hitachi's DFT: http://www.hitachigst.com/hdd/support/download.htm#DFT Whatever software you use to test your drive, it needs to be bootable (so that you do not affect Windows) and has to be able to do long tests (of every sector on the drive). Let us know if you need further assistance with these tools/instructions.
  12. Although I have a utility called Dial-a-fix that helps with these kinds of issues, it probably won't solve this one. I suggest starting at the Office 2003 Solution Center (which is quite good) : http://support.microsoft.com/ph/2488 Specifically, this section: http://support.microsoft.com/kb/304498 That article is a bit much, but we can walk you through any steps that you don't understand. If you have any questions or comments about your Office issue, make a NEW posting in the appropriate section of the forums (probably one of these: http://lunarsoft.net/forum/index.php?showforum=14) Good luck, and welcome to Lunarsoft.net!
  13. Try clicking "Flush SoftwareDistribution" on the main Dial-a-fix window. Answer 'no' to the secondary dialog. Try Windows Update again. It will take quite a while after using the Flush button for Windows Update to scan your system, so if it seems like it hangs/stalls, let it go for quite a while - it will eventually finish. Failing that, try installing the updates separately to see if any error messages are generated. You didn't mention which version and service pack level of Windows that you're using, so here are the landing pages: http://www.microsoft.com/technet/security/...n/MS06-006.mspx http://www.microsoft.com/technet/security/...n/MS07-047.mspx The first one has a standalone update that you can download, the second one does not (I can't find it). You can also check your event viewer for errors, or contact Microsoft support (which is usually free for Windows Update issues). There are other, more advanced methods for finding out what is wrong, but we'll get into that if none of the above helps.
  14. Are you posting about Dial-a-fix? If not, please register and post in a regular Lunarsoft Windows support forum. Before using Dial-a-fix (or any system utility for that matter, including Microsoft's own chkdsk for example) please do the following: Ensure your hard drive has no bad blocks Ensure your memory is free of errors To check for bad blocks, you can use your hard drive manufacturer's diagnostic utility (search for it), Dell's extended hard drive diagnostic (if you have a Dell, that is - and call Dell for support with this), Hitachi DFT (which works with almost any drive and is the recommended choice for most users) or a Linux live CD with the "badblocks" program on it (for experts). Please test your hard drive before posting. If you find one or more bad blocks, you should backup and consider replacing your drive. After the first bad block, it's all downhill from there. I have a complicated data recovery / testing article at my wiki here which explains quite a bit: https://wiki.lunarsoft.net/wiki/Data_recovery To check for memory problems, download and boot to a memtest86+ or Microsoft Memory Diagnostic disk/disc. memtest86+ Microsoft Memory Diagnostic Let the memory test for several hours (for at least one pass) - overnight is better if it is possible. I actually recommend a minimum of 5 complete passes. If a single error is found and you are not comfortable with memory replacement, consult a local PC repair shop. If you are comfortable with memory replacement, remove one memory module and start the test again. Rotate modules one-by-one until you find the defective one(s). If you are getting strange errors when Dial-a-fix registers DLLs, try the following things: Restart the computer and try that section in Dial-a-fix again Try to replace the file in question with a copy from the original source media Run SFC /scannow (through Start -> Run..., or through Dial-a-fix's Tools dialog) If you are having "Access denied" type errors, try Repair permissions in the Tools dialog (the hammer button) If a service has been marked for deletion, restart the computer and run that section of Dial-a-fix again. If you like Lunarsoft, please donate to Lunarsoft. Do not ask for support in THIS thread; make your own. If you think a common solution should be added to the above list, post in this thread.
  15. You're going to need to be more specific than that. Can you post a Dial-a-fix log or at least some context to that error message?
  16. The repair permissions tool probably wouldn't fix this anyway - you're going to have to fix the permissions yourself.
  17. Yep - I don't recommend it myself (well there's not really a point since it can't prevent, it can only set things back to defaults). It can find problems you didn't know about, though... the best section for that is section 5 (Registration center). So that PC World issue he promised to write is out? Aha! http://www.pcworld.com/article/id,137083/article.html
  18. I fully misunderstood this to mean that 9999 million people turn it off. Never mind. :cool:
  19. Care to cite your sources on this or do you just always work from a fully-engaged shotgun of hyperbole? Correct. I'm not expecting users to do anything with them except send them. The memory dumps that CCleaner cleans are crash dump logs from blue screens of death, not AOL Instant Messenger or some such. Blue screens of death, like kernel panics, need to be fixed immediately or data/computer loss occurs. If you don't send the reports and/or just delete them, your problem never gets solved. Since end-users don't know what "memory dumps" are and probably won't even notice that CCleaner is cleaning them away, there is nothing for a technician to work from once they finally take their computer into a shop (which of course will be after it's too late anyway). Sometimes OCA will directly tell you that your memory is bad/failing or that your hard drive is failing. Are you telling me you'd rather not know about that kind of information? Would you rather not help others find out that their hardware is faulty through Microsoft by way of your sent dumps? OCA aggregates information to better serve those who send them. Yeah, I guess not; they're just taking up mere kilobytes of space that could be better served by something more useful, like tracking cookies. Why? Cleaning it a year from now is the same as cleaning it right now. The prefetch data is deleted and new ones are put in place whenever new or updated applications are launched. It rotates all the time and has an upper limit set. It's pointless to clean it, period. It's placebo bullshit. Then turn off the prefetcher through its registry setting. That should be an enjoyable experience!
  20. There isn't any "source" so to speak, as Dial-a-fix simply passes execution over to secedit.exe. The commands are: secedit.exe /analyze /db %systemroot%\sectest.db /cfg %systemroot%\inf\defltwk.inf /log %systemroot%\security\logs\secanalyze.log secedit.exe /configure /db %systemroot%\sectest.db /cfg %systemroot%\inf\defltwk.inf /log %systemroot%\security\logs\secrepair.log (Ugh why do code boxes text wrap on here? Code boxes should always use scrollbars. The above commands are two long lines each.)
  21. It's not (directly) a bug in DAF (except for possible negligence on my part), but rather a side effect of secedit.exe and the template it uses to restore permissions. I tried to fix this before and the fix worked and hasn't come back until very recently (your report is one of a small handful that I am just now hearing about). I haven't yet figured out why this is happening again, exactly, but I'll go ahead and take responsibility for the bug anyway since I triggered it. I've gotten a lot of reports that other peoples' limited accounts have stayed put with the current version of Dial-a-fix (from users who were affected by the previous thing that I thought I had "fixed"), and I have been unable to reproduce the problem myself as of yet. In the next version of Dial-a-fix (which is being worked on right now) I will ensure that the Users group retains its members. I'll also try to narrow down the exact conditions under which this occurs, since it doesn't seem to be very consistent. I sincerely apologize for any inconvenience this may have caused you! I also hope you were able to resolve your ZoneAlarm issue. Let me know if I can be of any assistance.
  22. I had the "invalid value for registry" error a few times and all I had to do was run Dial-a-fix again. If all else fails, register the file yourself with regsvr32.
  23. If you email Microsoft Windows Update Product Support Services (MS WU PSS) they'll typically tell you to use Dial-a-fix. Weird, eh? Tons of MS MVPs and PSS agents/MS employees are using it to help their customers. The thing that makes my program different from all of their solutions is that I packed all of their solutions into one place. Their scattered MSKBs regard very specific issues and most people are not able to find the right one for their particular problem. With Dial-a-fix, it doesn't care; it just does them all. I'd love to work at Microsoft. I want to talk with my idol Mark Russinovich! Before this year is over a new version of Dial-a-fix will be out that scans for a lot of stuff. Stuff that could be causing problems you don't even notice, or impending failures. Keep checking back for updates. Cheers and thanks for the praise!
  24. I have not written any terms and conditions (therefore you are free to do what you want) but I would prefer that you didn't host downloads of Dial-a-fix yourself, and simply linked to my wiki and/or linked to my download links.
  25. It's not Dial-a-fix; Dial-a-fix doesn't create any files or registry entries for itself.
×
×
  • Create New...