Windows error number 1392

Discussion in 'FirstDefense-ISR Forum' started by OftenBaffled, Jul 23, 2010.

Thread Status:
Not open for further replies.
  1. OftenBaffled

    OftenBaffled Registered Member

    Joined:
    Sep 20, 2008
    Posts:
    11
    Chaps,

    I'd appreciate it if anyone can come up with any ideas about this one.

    Im running XP Pro. SP3 and FDISR 3.31.233.

    I've recently noticed error messages as shown below in bold.
    The funny thing is that the errors only show in the logs and in the text on the FDISR program window. They do not show in Transfer Info. > Error.
    The above being the case, it's difficult to say if this is a new thing or not as I only tend to keep an eye on Transfer Info. > Error.

    The first two errors are the most mysterious ones as there's no useful information there, no pointer to a problem folder or anything else that could provide a clue.

    Any suggestions?

    Thanks in advance.

    OB

    22/07/2010 21:13:27 Error - AAR::GetFileSecurity: The file or directory is corrupted and unreadable.
    22/07/2010 21:13:27 Windows error number 1392
    22/07/2010 21:13:27 Error - FindFirstFile: The file or directory is corrupted and unreadable.
    22/07/2010 21:13:27 Windows error number 1392
    22/07/2010 21:13:27 Error - Reading folder: \\?\0:\WINDOWS\Installer\{C3DAC196-8487-4E2E-94F3-9CBE361EB712}
     
  2. pandlouk

    pandlouk Registered Member

    Joined:
    Jul 15, 2007
    Posts:
    2,551
    Run a checkdisk. If it fixes it ok, if not see below...

    Scan with an antirootkit /antimalware from within windows and from a winpe/ bartpe. "Ghost" errors like the first two often indicate the presence of stealth rootkits.

    Panagiotis
     
  3. OftenBaffled

    OftenBaffled Registered Member

    Joined:
    Sep 20, 2008
    Posts:
    11
    Thanks for the suggestion, Pandlouk, I'll try that and report back.
     
  4. OftenBaffled

    OftenBaffled Registered Member

    Joined:
    Sep 20, 2008
    Posts:
    11
    Pandlouk,

    All sorted now.

    Checkdisk wouldn't run when scheduled from within Windows or by CMD. I kept getting the "Cannot open volume for direct access" error.

    Ran Checkdisk from PE - it found and fixed a few errors.

    Ran multiple scumware scans from PE - all clear.

    Ran FDISR - zero errors.

    So we're all good. :cool:

    Many thanks for your help.

    OB
     
  5. pandlouk

    pandlouk Registered Member

    Joined:
    Jul 15, 2007
    Posts:
    2,551
    You are welcome. :)

    Panagiotis
     
Thread Status:
Not open for further replies.