1392 error

[Kolnikoff]

Hi,

Recently I had an issue with a M$ update (for Silverlight) which screwed
up Winamp. Have almost got my system back to how it should be but the
drive that Winamp was accessing at the time is no longer recognised by
Windows 7 Home Premium, I get a 1392 error.

I have cleaned up my registry with CCleaner but the drive is still not
recognised, any solutions please.
--

Cheers

Kol
'''
<<who doesn't surf as such,>>
<<but plays in the shallows>>

 

[Nil]

Recently I had an issue with a M$ update (for Silverlight) which
screwed up Winamp. Have almost got my system back to how it should
be but the drive that Winamp was accessing at the time is no
longer recognised by Windows 7 Home Premium, I get a 1392 error.

As far as I can tell, a "1392" error indicates a corrupt disk or file
system. I doubt that the MS (spelled with an "S", not a dollar sign)
was responsible for that. It was probably corrupt already and liable to
go at any time.

I have cleaned up my registry with CCleaner but the drive is still
not recognised, any solutions please.

Why did you do that? There is almost zero change that CCleaner could
have helped you with that kind of error. You may have made things worse
by indiscriminately "cleaning" your registry.

 

[Ken1943]

Hi,

Recently I had an issue with a M$ update (for Silverlight) which screwed
up Winamp. Have almost got my system back to how it should be but the
drive that Winamp was accessing at the time is no longer recognised by
Windows 7 Home Premium, I get a 1392 error.

I have cleaned up my registry with CCleaner but the drive is still not
recognised, any solutions please.

Go to Disk Management and see if the drive has been given a drive letter.


KenW

 

[Ken Blake]

I have cleaned up my registry with CCleaner but the drive is still not
recognised, any solutions please.

Using ccleaner (or any other program) to do that is a very bad
mistake. CCleaner is an excellent program in all other respects, but
registry cleaners are useless and very dangerous.

Here's my standard message on this subject:

Registry cleaning programs are *all* snake oil. Cleaning of the
registry isn't needed and is dangerous. Leave the registry alone and
don't use any registry cleaner. Despite what many people think, and
what vendors of registry cleaning software try to convince you of,
having unused registry entries doesn't really hurt you.

The risk of a serious problem caused by a registry cleaner erroneously
removing an entry you need is far greater than any potential benefit
it may have.

Read http://www.edbott.com/weblog/archives/000643.html

and http://aumha.net/viewtopic.php?t=28099

and also
http://blogs.technet.com/markrussin.../02/registry-junk-a-windows-fact-of-life.aspx

Let me point out that neither I nor anyone else who warns against the
use of registry cleaners has ever said that they always cause
problems. If they always caused problems, they would disappear from
the market almost immediately. Many people have used a registry
cleaner and never had a problem with it.

Rather, the problem with a registry cleaner is that it carries with it
the substantial *risk* of having a problem. And since there is no
benefit to using a registry cleaner, running that risk is a very bad
bargain.

 

[Kolnikoff]

Hi,

<snip>

Thanx for the input guys/gals, am now in the process of trying to
recover the files using Recuva, will post on success (or lack of it).
Used SeaTools to 'recognise' the faulty hard disk again.
--

Cheers

Kol
'''
<<who doesn't surf as such,>>
<<but plays in the shallows>>

 

[Paul]

Hi,

Recently I had an issue with a M$ update (for Silverlight) which screwed
up Winamp. Have almost got my system back to how it should be but the
drive that Winamp was accessing at the time is no longer recognised by
Windows 7 Home Premium, I get a 1392 error.

I have cleaned up my registry with CCleaner but the drive is still not
recognised, any solutions please.

http://pcsupport.about.com/od/findbyerrormessage/tp/system_error_codes_1300_1399.09.htm

"Error Code 1392

System error code 1392 means "The file or directory is corrupted and unreadable."
This error code may also display as "ERROR_FILE_CORRUPT" or as the value 0x570."

A problem with an NTFS file system, would be something you might use CHKDSK on.
The file system needs to be checked for consistency. The registry would not
normally have anything to do with that.

In the example here, Windows 7 has a problem when the indexer is running
at the same time as a user program is trying to do something. The indexer
is apparently temporarily locking files as it does its thing.

http://social.technet.microsoft.com.../thread/df935a52-a0a9-4f67-ac82-bc39e0585148/

Your error could either be a "real" error, in which case you'd try CHKDSK.

Or, it's a "fake" error caused by a bug in Windows 7 and the way the indexer
works.

Your description makes it seem the partition is a data partition, and not C:,
in which case a file system check should be able to run without rebooting
the system.

*******

If the partition has lost it's drive letter, there is a command line
syntax for running CHKDSK. I don't know if Windows 7 does it exactly the
same way or not.

http://technet.microsoft.com/en-us/library/bb457122.aspx

"chkdsk \\?\Volume{2d9bd2a8-5df8-11d2-bdaa-000000000000}

You can determine a symbolic link name for a volume by
using the mountvol command."

I didn't find the mountvol command very useful. It doesn't
seem to have an option to list everything which is mounted.

In the registry, I can see some volume strings under "mountpoints2",
but that didn't seem to be a complete list either. So while that
syntax may exist for chhdsk, there is no guarantee you'll be
able to figure out what to type there.

Paul

 

[Kolnikoff]

<snip>

Thanx for the input guys/gals, am now in the process of trying to
recover the files using Recuva, will post on success (or lack of it).
Used SeaTools to 'recognise' the faulty hard disk again.

Got 99.9% (-ish, for the pedants) recovered, now to back 'em up
somewhere. Recuva did the job for me so I can heartily recommend it.
--

Cheers

Kol
'''
<<who doesn't surf as such,>>
<<but plays in the shallows>>