Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by DjLizard

  1. It's not Vista ready. Thanks for reminding me - I have put up a warning on my wiki page. You shouldn't be having to run such a tool anyway - it's Microsoft's beta program screwing up, not really a whole system-wide permissions problem. You can try to work around this by changing the permissions for the key it's complaining about, but you should definitely look into the Microsoft Communities newsgroups as there are a lot of bright and helpful folks there: Here is the main forum for WLM: http://www.microsoft.com/communities/newsg....live.messenger You will definitely want to stay within the English forums, as that's where the MVPs and MS employees who have the most knowledge about this stuff typically hang out. There may already be a post there covering your issue, or you can post about it yourself. (The error messages are translated but the error codes themselves are universal - they should be able to help you even if your errors are translated from French). Anyway, you could open regedit to this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\UIPlugins\{0776F107-F5A6-404B-9A78-7027FA6EAADD} and right-click it (Permissions) and then try to give yourself full control over the key and try installing again. This may not work (I don't use WLM myself, especially not betas) so the above newsgroup should be able to get you sorted. Good luck!
  2. This is the correct answer Thanks for your contribution! You may also need to remove all versions of .NET Framework (especially 1.1 which is the buggiest) and let it download them all from Windows Update.
  3. Please submit a log file. You can access the log pane by clicking the piece of paper icon in the bottom right. It would also be a good idea to submit a HijackThis log. I doubt Dial-a-fix will be able to help you with internet connectivity problems, except for the few items it has in its Tools dialog. You could be infected, some big firewall/security program you installed could be broken, or you could have some faulty hardware/equipment... who knows. :hello:
  4. Also, if you're affected by any policies that Dial-a-fix looks for, it will automatically open the dialog when you first start DAF.
  5. Sorry, it wouldn't be practical. (It would be 3x as much code as Dial-a-fix already is, and a ton of features just wouldn't work at all.)
  6. Use the "Flush SoftwareDistribution" button, but beware - I've never done this in Windows Server 2003.
  7. I've never gotten to test Dial-a-fix in Windows Server 2003 because I don't have a copy (apparently there's a trial I can download now), so it's officially not supported in it, but it should have worked... I agree with Eldmannen, check to see that %WINDIR% points to C:\WINDOWS... otherwise I have no idea. This version of Dial-a-fix uses the JEDI JVCL's System Info component and I haven't looked into how it checks for that folder (I would hope it asks Windows via the SHGetSpecialFolderLocation function). The next version (which I am writing now) is written in C and everything will be done The Right Way, without third-party components. I will do everything by hand to make sure there is nobody screwing me over (like the JVCL, Borland, or anyone else's software). Alternatively, you could just make c:\Dokumente und Einstellungen\Administrator\Windows\system32 and copy sc.exe into there if it really is just a DAF bug (from not being tested in 2003). I'm not sure you will want to run Dial-a-fix though, since like I said, it hasn't been tested in 2003. DAF might get the service permissions wrong (or something) due to this not being XP. What problems are you having, perhaps I can find a safer, manual way to help you fix it?
  8. While Dial-a-fix will not break anything for you any more than it already is, it most likely won't solve your issues since it performs sort of a different function. The first thing you should do is rid yourself of any spurious Internet Explorer add-ons, by checking Add/Remove programs for toolbars. AOL, Google, MSN, Yahoo, Verizon, Starware, MyWay, Earthlink, and a lot of other vendors make toolbars that can crash IE. Remove all of them. In some cases they are the problem. --- Regarding right-clicking IE.INF, are you sure it said it couldn't find "explorer.exe"? Did you mean "rundll32.exe" by any chance?
  9. Which version of Windows are you using? (XP SP2? 2000 SP4?) Check your time and date (especially the year) and make sure that they are accurate. The security certificate won't work unless the year is correct. Try clicking Flush SoftwareDistribution and then answer Yes. Restart the computer and visit again. If that doesn't work, click it again but choose No (this deletes the update history). Then visit again. If that doesn't work, you may have to post the last 30 lines of your C:\WINDOWS\WindowsUpdate.log. Make sure you post the one without the space (as you may also have a "Windows Update.log").
  10. The qmgr DLL is known, and is on the wiki: https://wiki.lunarsoft.net/wiki/Dial-a-fix It will be fully fixed in the next version of DAF. All it means is that you don't have the latest version of Windows Installer and BITS 2.0 and stuff. Get updates working again, get your updates, and you'll be OK.
  11. DjLizard


    I don't know what this is unless Microsoft has updated zipfldr to be unregisterable (which is happening with a lot of DLLs lately). It may mean that your system is fine and that Dial-a-fix does not recognize the new version. I'll look into it soon. In the meantime, don't worry about anything unless you're having problems with something.
  12. I'm not sure how this can be happening as it was already fixed. I'll look into it, though. I'm making a new version of Dial-a-fix soon. Sorry I haven't been around to answer questions.
  13. "Access is Denied" on that DLL generally means you need to run Dial-a-fix's Repair Permissions (in the Tools menu). If that doesn't work, you'll have to re-add permissions to msxml3.dll yourself. Make a System Restore point before using Repair Permissions. If you need any help, ask Tarun. I'm flooded with work :/
  14. Dial-a-fix changes service settings in several places, but it only changes them to the proper defaults (i.e., what Microsoft wants them to be set to and what they should be set to).
  15. You will need to identify the package that is appearing (using MSICUU) and remove it. (Then, of course, you'd have to reinstall whatever that package belongs to.) You can download MSICUU here: http://support.microsoft.com/kb/290301 MSICUU will remove this program from the registry completely (as if it is uninstalled) but the files that belong to this package will remain (i.e., somewhere in Program Files). I can tell you from experience that it is extremely likely that the MSI package in question belongs to HP AiO printer/scanner/fax software.
  16. Ah, it's IE7 doing it again.
  17. Aw crap. Microsoft changed registration behavior again. What this means to you: you can safely ignore that error. Dial-a-fix needs an exception for build 3020 of that DLL. I'll make a new build of Dial-a-fix soon.
  18. Open the Tools dialog in Dial-a-fix, and double click on Repair Permissions. Then try the Explorer/IE/OE/shell/WMP checkmark again.
  19. I get the feeling that you may have a more serious underlying problem (such as hard drive failure, or something to that effect). Flush SoftwareDistribution's code hasn't changed in the past 5 point releases of Dial-a-fix, and all it does is execute rmdir /s /q on C:\Windows\SoftwareDistribution, which is only used by Windows Update (nothing regarding your "pc's settings"). Without being able to work on the system prior to the System Restore myself, there is no way for me to tell you what happened or how to proceed. You will probably want to backup any important user data (documents, pictures, emails/addresses, etc) and prepare to reinstall Windows from scratch. You also may need to test your hard drive, too, as it may contain bad sectors (which would cause completely unpredictable and random problems). I would consult a local PC technician and have the hard drive tested, or head over to the other Lunarsoft support forums to ask questions about how to use one or more Drive Fitness Test programs.
  20. DjLizard


    Please post the log, or at least the error code.
  21. Well, I doubt Dial-a-fix will change any of that.
  22. https://wiki.lunarsoft.net/wiki/Dial-a-fix That should work. >_<
  23. Yeah. It's decent! https://wiki.lunarsoft.net/wiki/Dial-a-fix vv edit: ok I fixed the manifest bug vv
  24. IE7 no longer seems to faze DAF as of the latest DAF betas. This is because when IE7 is detected, DAF excludes registration of several components (pngfilt, etc) that can no longer be registered. Edit: okay, it doesn't like browseui and shdocvw. I'm fixing this and a new release (of v0.60) will come out soon. Edit 2: okay, it's fixed (get v0.60.0.24 or higher and it's good to go)
  • Create New...