Jump to content

DjLizard

Sponsor
  • Content Count

    273
  • Joined

  • Last visited

Posts posted by DjLizard


  1. version.dll probably crashes because dmloader is corrupted (like in the other post) and being corrupted causes garbage versioning information to be passed back to Dial-a-fix.

    Dial-a-fix 1.0 (if it ever gets off the ground) doesn't crash when passed garbage version information (already worked on that), and will probably be able to figure this out automatically.

     

    Please support Dial-a-fix 1.0!


  2. Please like on facebook!

    Please tell your techie friends to like!

    Please tell everyone to send money!

    ---

    I don't want this to die, and neither does anyone else.

    But I need financial help if I'm ever going to find time to work on this again.

    If everyone sends a few bucks, I may be able to take time off from my 17 hour workdays (6.5 days a week) to work on Dial-a-fix.  It's because of the work I have to endure just to stay in debt that takes me away from Dial-a-fix.

    Please help!

    - DjLizard

     

     


  3. Explore C:\WINDOWS\SYSTEM32 and see which of the following files exist.

    This is every single file that may or may not be present on your system that has anything to do with the Cryptography service (or is used by CryptSvc).

    You may not have a few of these files and that's OK. Just let me know a list of ones you do not have.

    ACTIVEDS.DLL

    ADSLDPC.DLL

    ADVAPI32.DLL

    ADVPACK.DLL

    APPHELP.DLL

    ATL.DLL

    AUTHZ.DLL

    BROWSEUI.DLL

    CABINET.DLL

    CDFVIEW.DLL

    CERTCLI.DLL

    CFGMGR32.DLL

    CLUSAPI.DLL

    COMCTL32.DLL

    COMDLG32.DLL

    CREDUI.DLL

    CRYPT32.DLL

    CRYPTDLG.DLL

    CRYPTEXT.DLL

    CRYPTSVC.DLL

    CRYPTUI.DLL

    CSCDLL.DLL

    DBGHELP.DLL

    DEVMGR.DLL

    DHCPCSVC.DLL

    DNSAPI.DLL

    DOT3API.DLL

    DOT3DLG.DLL

    DSSENH.DLL

    DUSER.DLL

    DWMAPI.DLL

    EAPOLQEC.DLL

    EAPPCFG.DLL

    EAPPPRXY.DLL

    EFSADU.DLL

    ESENT.DLL

    GDI32.DLL

    GDIPLUS.DLL

    GPKCSP.DLL

    HLINK.DLL

    HNETCFG.DLL

    IEFRAME.DLL

    IERTUTIL.DLL

    IEUI.DLL

    IMAGEHLP.DLL

    IMGUTIL.DLL

    IMM32.DLL

    INETCOMM.DLL

    INITPKI.DLL

    IPHLPAPI.DLL

    KERNEL32.DLL

    LICDLL.DLL

    LINKINFO.DLL

    LZ32.DLL

    MFC42U.DLL

    MLANG.DLL

    MOBSYNC.DLL

    MPR.DLL

    MPRAPI.DLL

    MPRUI.DLL

    MSASN1.DLL

    MSGINA.DLL

    MSHTML.DLL

    MSI.DLL

    MSIMG32.DLL

    MSLS31.DLL

    MSOERT2.DLL

    MSRATING.DLL

    MSSIGN32.DLL

    MSSIP32.DLL

    MSVCP60.DLL

    MSVCRT.DLL

    MSWSOCK.DLL

    NETAPI32.DLL

    NETCFGX.DLL

    NETMAN.DLL

    NETPLWIZ.DLL

    NETRAP.DLL

    NETSHELL.DLL

    NETUI0.DLL

    NETUI1.DLL

    NETUI2.DLL

    NORMALIZ.DLL

    NTDLL.DLL

    NTDSAPI.DLL

    NTLANMAN.DLL

    ODBC32.DLL

    OLE32.DLL

    OLEACC.DLL

    OLEAUT32.DLL

    OLEDLG.DLL

    OLEPRO32.DLL

    ONEX.DLL

    POWRPROF.DLL

    PRINTUI.DLL

    PSAPI.DLL

    QUERY.DLL

    QUTIL.DLL

    RASAPI32.DLL

    RASDLG.DLL

    RASMAN.DLL

    REGAPI.DLL

    REGWIZC.DLL

    RPCRT4.DLL

    RSAENH.DLL

    RTUTILS.DLL

    SAMLIB.DLL

    SCARDSSP.DLL

    SCCBASE.DLL

    SCECLI.DLL

    SECUR32.DLL

    SETUPAPI.DLL

    SHDOCVW.DLL

    SHELL32.DLL

    SHLWAPI.DLL

    SHSVCS.DLL

    SLBCSP.DLL

    SOFTPUB.DLL

    TAPI32.DLL

    URLMON.DLL

    USER32.DLL

    USERENV.DLL

    USP10.DLL

    UTILDLL.DLL

    UXTHEME.DLL

    VERSION.DLL

    W32TOPL.DLL

    WINHTTP.DLL

    WININET.DLL

    WINMM.DLL

    WINSCARD.DLL

    WINSPOOL.DRV

    WINSTA.DLL

    WINTRUST.DLL

    WLDAP32.DLL

    WMI.DLL

    WS2_32.DLL

    WS2HELP.DLL

    WSOCK32.DLL

    WTSAPI32.DLL

    WZCDLG.DLL

    WZCSAPI.DLL

    WZCSVC.DLL


  4. Dial-a-fix won't run in limited user accounts, and wouldn't really be able to fix this if it did since it has not been specifically programmed to fix this. :(

    If you run it in the Administrator account, however, it's safe to check all boxes in section 5, the registration center. You won't need the other sections.


  5. It depends on what you mean by "RPC".

    A) If you mean the actual "Remote Procedure Call" service, there is almost nothing Dial-a-fix can do to solve that, as it is a core service. Pretty much nothing works if the RPC service won't start. Windows wants to restart automatically whenever the Remote Procedure Call service fails. There aren't any known "fix-all" solutions for the RPC service like there are for Windows Update, etc.

    B) If you mean the generic error "The RPC server is unavailable", this is actually not in reference to the aforementioned "Remote Procedure Call" service. This generic error actually means that a process tried to communicate with a service that is unavailable (i.e., talked to a "Disabled" service as if it wasn't, without trying to check that it is running first). Generic errors like these would be fixed on a case-by-case basis since anything can cause this to happen to any other thing.


  6. You will see a window open and commands processing. When the window closes the fix will have completed.

    Then go run Dial _A-Fix again please.

    Wot's this then.

    The only things Dial-a-fix doesn't (yet) do that WUFix does are: place Windows Update sites in the Trusted Zone, place Windows Update sites in the exception list of IE Popup Blocker

    The problem is that most people don't notice the "Flush SoftwareDistribution" button which does the other half of the stuff you mentioned.

    The next version of Dial-a-fix will do all of the above but I am not going to place any sites in the Trusted Zone or IE Popup Blocker exceptions because it is unnecessary. I will make sure that they don't go onto the *block* lists, but there's no need for them to be in the Trusted Zone or other exceptions.


  7. I guess it would have helped if I had actually put the solution to this in the tips section; my fault!

    Tarun: the explanation is simple (i.e., please make a writeup on the tips section about this for me, since it's very common and easy to fix). The service is stuck in a state of either stopping or starting, and thus cannot be immediately deleted and recreated by Dial-a-fix. When Dial-a-fix tries this, Windows flags it for removal on the next reboot, which also makes it to where nothing else can be done to the service. Once you reboot, you no longer even HAVE the service. It's just gone completely. This is actually a good thing - now you can reinstall it without any interference. For any given service that is marked by Windows because of Dial-a-fix wanting to change its state while stuck, you just have to reboot and then run the same section(s) in Dial-a-fix that you ran before. (This could happen to any service that Dial-a-fix wants to adjust, not just wuauserv.) The unusual part about bpb's post is that rebooting and running it again DIDN'T fix it. So, when you make the writeup for this, mention that 'wuauserv' / Windows Updates service is the most common thing that this happens to, and also tell users to Flush SoftwareDistribution before AND after running "Fix Windows Update" because flushing is usually the part that fixes their original problem (and usually fixes the reason the service got stuck in the first place).

    bpb: Reboot to start from a clean slate, run Dial-a-fix, click "Flush SoftwareDistribution" and click NO, reboot again, *then* check "Fix Windows Update" and click GO. Hopefully you won't get the error again. If you still do, this would be a first for me, and that means it's being caused by something I've yet to encounter (which is unusual because I've encountered practically everything :gold: ).


  8. This has actually happened before... it turns out it is because the default template removes limited user accounts from the Users group, which is what my post above was about (replacing the group declaration in the INF). Have you tested it again with another limited user account? Am I to understand you are actually able to use repair permissions without it breaking limited user accounts now? o_O


  9. I just thought of this, and I've never tested it, but it just might work:

    Open the following file in notepad:

    C:\WINDOWS\INF\defltwk.inf

    (This is the file "repair permissions" calls)

    Find the following lines:

    [Group Membership]

    %SceInfUsers%__Memberof =

    Add this after the equals sign: *S-1-5-32-545

    It will now look like this:

    [Group Membership]

    %SceInfUsers%__Memberof = *S-1-5-32-545

    Save the file, and run DAF's repair permissions again.

    Warning: if I somehow misunderstand how this works then this could break something else. If you want to be safe, make a backup copy of SAM and SECURITY before proceeding. (You can Google "ERDNT" do make a full registry hive backup or use System Restore to set a restore point or something, I guess. More info at the Lunarsoft wiki in the System Volume Information article).


  10. Windows wants to delete it next time you reboot. Go ahead and restart the computer. Then immediately use Dial-a-fix and the same sections you checked before (especially Fix Windows Update) and see what happens now (it will probably work). Then, click Flush SoftwareDistribution and choose whether you want to save the update history or not (I usually don't but the feature to save history was requested). NOTE: Don't click Flush if you hadn't yet run "Fix Windows Update" which puts the service back after you rebooted.


  11. 1st: Would dial-a-fix, Flush Software Distribution cause sp3 to be available again for download?

    2nd: What would correct the System Properties entry to show that sp3 was no longer installed?

    1st: Probably not, but I can't guarantee that. It won't hurt anything to use Flush, so you might as well try it.

    2nd: Too complicated, and just changing the text there would be useless anyway. It'd be better to identify and solve the issue preventing you from installing SP3 and get SP3 reinstalled (by using the full .exe download at microsoft.com). Were you having BSoDs? Are there files in C:\WINDOWS\Minidump that could be examined (by us)? Could the problem be any of this? http://msinfluentials.com/blogs/jesper/arc...ing-xp-sp3.aspx


  12. I've used nLite several times and had it mess things up as well, and I consider myself well-versed in Windows internals.

    Also, due to a bug in Repair permissions, I recommend that all limited user accounts are temporarily upgraded to Administrator accounts before running it.


  13. Judging by the thread title, I have to assume you're saying you're getting a Windows Installer 1706 error about the HP SDP application. The only advice I can give you is to remove its entry using Windows Installer Clean-up Utility (search microsoft.com for that).


  14. This is a bug in Dial-a-fix. My bad!

    Can't remember what file it is (I think it's cmdevtgprov.dll - if this is true you can move that file out of WBEM so Dial-a-fix doesn't see it and it might stop crashing).

    Can't tell you when it'll be fixed, either.


  15. Even without the source code, they could make an own software they they name Dial-a-fix and pass it off as malware or fake PC repair software to the masses.

    Without the source code, it would be very easy for WinAntiSpyware or others to make an own software they call Dial-a-fix and sully your name into the ground by making it not work, or report fake repairs.

    Sometimes, having access to the code versus not having access is what pushes the decision over the line towards ripping it off.

×
×
  • Create New...