I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
stating file 0x80070002 cant be found. I returned the drive to the store and
replaced it, but I still get the same failure. Could I have gotten 2 bad
drives or is there something I can do/chnge in Vista to correct this? Thanks
for your help! Tom

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/com....vista.general

Hello Tomen1,

Have a look here:
Description of the System Update Readiness Tool for Windows Vista

<http://support.microsoft.com/kb/947821>

I hope this new tool, can solve your problem.

Good luck
- -- --

"Tomen1" wrote:

> I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
> stating file 0x80070002 cant be found. I returned the drive to the store and
> replaced it, but I still get the same failure. Could I have gotten 2 bad
> drives or is there something I can do/chnge in Vista to correct this? Thanks
> for your help! Tom
>
> ----------------
> This post is a suggestion for Microsoft, and Microsoft responds to the
> suggestions with the most votes. To vote for this suggestion, click the "I
> Agree" button in the message pane. If you do not see the button, follow this
> link to open the suggestion in the Microsoft Web-based Newsreader and then
> click "I Agree" in the message pane.
>
> http://windowshelp.microsoft.com/com....vista.general

On Sun, 20 Apr 2008 18:06:01 -0700, Tomen1
<(E-Mail Removed)> wrote:

>I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
>stating file 0x80070002 cant be found. I returned the drive to the store and
>replaced it, but I still get the same failure. Could I have gotten 2 bad
>drives or is there something I can do/chnge in Vista to correct this? Thanks
>for your help! Tom

Extremely unlikely two hard drives in a row would fail in the same
way. Since 0x80070002 is a catch all error flag which gets shown for
many causes I would suspect while trying to backup Vista encountered
some file corruption or some other problem with the file system which
stopped it dead it it's tracks.

Since Vista uses NTFS, it is a much better file system than the old
FAT and FAT 32 file systems so it generally can repair itself. The
catch 22 is you often have to tell it to fix itself.

Go to Windows Explorer and one at a time right click on each drive
folder, then properties. From the Tools tab, click the check now
button, ensure that 'automatically fix file system errors' is checked.
Do not check the second option. When you do your C drive since that is
always in use it will say it can't now, but ask to schedule a scan
next time you reboot. Do it. A special screen will come up in the boot
sequence just ahead of the point it would normally load Windows. This
will show the progress of file system scan. It goes by fast, you may
be able to read the summary results which say what if anything was
wrong and that NTFS fixed itself. Rarely it can't fix something. Once
done, it should only take a few minutes tops per drive, try your
backup routine again and see if it gets past the log jam.

First of all, THANKS to all who responded to my problem! Adam was right. It
seems there were some problems on C drive...and chkdsk fixed them. My backup
to the usb drive completed fully with no errors. I think many folks would
benefit from trying this fix also. Again...Thank you...Tom

"Adam Albright" wrote:

> On Sun, 20 Apr 2008 18:06:01 -0700, Tomen1
> <(E-Mail Removed)> wrote:
>
> >I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
> >stating file 0x80070002 cant be found. I returned the drive to the store and
> >replaced it, but I still get the same failure. Could I have gotten 2 bad
> >drives or is there something I can do/chnge in Vista to correct this? Thanks
> >for your help! Tom
>
> Extremely unlikely two hard drives in a row would fail in the same
> way. Since 0x80070002 is a catch all error flag which gets shown for
> many causes I would suspect while trying to backup Vista encountered
> some file corruption or some other problem with the file system which
> stopped it dead it it's tracks.
>
> Since Vista uses NTFS, it is a much better file system than the old
> FAT and FAT 32 file systems so it generally can repair itself. The
> catch 22 is you often have to tell it to fix itself.
>
> Go to Windows Explorer and one at a time right click on each drive
> folder, then properties. From the Tools tab, click the check now
> button, ensure that 'automatically fix file system errors' is checked.
> Do not check the second option. When you do your C drive since that is
> always in use it will say it can't now, but ask to schedule a scan
> next time you reboot. Do it. A special screen will come up in the boot
> sequence just ahead of the point it would normally load Windows. This
> will show the progress of file system scan. It goes by fast, you may
> be able to read the summary results which say what if anything was
> wrong and that NTFS fixed itself. Rarely it can't fix something. Once
> done, it should only take a few minutes tops per drive, try your
> backup routine again and see if it gets past the log jam.
>
>

As I suffer from exactly Tomen's problem, I tried your suggestion, which
looks promising (although I had to get the standalone version, as I wasn't
having an Update problem, so wasn't offered it!). Bizarrely, when I tried to
run it, it failed with error 0x8007000d - which is defined as 'Invalid
Data'!!!!!! Can't win!

Must now try Adam's solution - as it worked for Tomen!

"Engel" wrote:

> Hello Tomen1,
>
> Have a look here:
> Description of the System Update Readiness Tool for Windows Vista
>
> <http://support.microsoft.com/kb/947821>
>
> I hope this new tool, can solve your problem.
>
> Good luck
> - -- --
>
> "Tomen1" wrote:
>
> > I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
> > stating file 0x80070002 cant be found. I returned the drive to the store and
> > replaced it, but I still get the same failure. Could I have gotten 2 bad
> > drives or is there something I can do/chnge in Vista to correct this? Thanks
> > for your help! Tom
> >
> > ----------------
> > This post is a suggestion for Microsoft, and Microsoft responds to the
> > suggestions with the most votes. To vote for this suggestion, click the "I
> > Agree" button in the message pane. If you do not see the button, follow this
> > link to open the suggestion in the Microsoft Web-based Newsreader and then
> > click "I Agree" in the message pane.
> >
> > http://windowshelp.microsoft.com/com....vista.general

Adam

Hoping for great things like Tomen, I tried to run CHKDSK as you described
but the scheduled operation on restart would not happen (twice). So I tried
it from the command prompt (without /F) and discovered the following issues:

No bad records or sectors
8 orphaned files
Master file table's (MFT) BITMAP attribute is incorrect
The Volume Bitmap is incorrect
Windows found problems with the file system.

As advised, I then tried to run chkdsk /f and was told that the drive
couldn't be locked and so it cannot run because the volume is in use by
another process. Asked if I wanted to schedule a run next time system
restarts - YES.
Immediately responds with a message: chkdsk could NOT schedule this volume
to be checked next time the sytem restarts.
What to try next????? Interfering with the boot process? How?

"Adam Albright" wrote:

> On Sun, 20 Apr 2008 18:06:01 -0700, Tomen1
> <(E-Mail Removed)> wrote:
>
> >I am trying to back up to a WD Passport 250gb usb drive. Every time it fails
> >stating file 0x80070002 cant be found. I returned the drive to the store and
> >replaced it, but I still get the same failure. Could I have gotten 2 bad
> >drives or is there something I can do/chnge in Vista to correct this? Thanks
> >for your help! Tom
>
> Extremely unlikely two hard drives in a row would fail in the same
> way. Since 0x80070002 is a catch all error flag which gets shown for
> many causes I would suspect while trying to backup Vista encountered
> some file corruption or some other problem with the file system which
> stopped it dead it it's tracks.
>
> Since Vista uses NTFS, it is a much better file system than the old
> FAT and FAT 32 file systems so it generally can repair itself. The
> catch 22 is you often have to tell it to fix itself.
>
> Go to Windows Explorer and one at a time right click on each drive
> folder, then properties. From the Tools tab, click the check now
> button, ensure that 'automatically fix file system errors' is checked.
> Do not check the second option. When you do your C drive since that is
> always in use it will say it can't now, but ask to schedule a scan
> next time you reboot. Do it. A special screen will come up in the boot
> sequence just ahead of the point it would normally load Windows. This
> will show the progress of file system scan. It goes by fast, you may
> be able to read the summary results which say what if anything was
> wrong and that NTFS fixed itself. Rarely it can't fix something. Once
> done, it should only take a few minutes tops per drive, try your
> backup routine again and see if it gets past the log jam.
>
>

On Mon, 21 Apr 2008 17:29:06 -0700, John Edwards
<(E-Mail Removed)> wrote:

>Adam
>
>Hoping for great things like Tomen, I tried to run CHKDSK as you described
>but the scheduled operation on restart would not happen (twice). So I tried
>it from the command prompt (without /F) and discovered the following issues:
>
>No bad records or sectors
>8 orphaned files
>Master file table's (MFT) BITMAP attribute is incorrect
>The Volume Bitmap is incorrect
>Windows found problems with the file system.
>
>As advised, I then tried to run chkdsk /f and was told that the drive
>couldn't be locked and so it cannot run because the volume is in use by
>another process. Asked if I wanted to schedule a run next time system
>restarts - YES.
>Immediately responds with a message: chkdsk could NOT schedule this volume
>to be checked next time the sytem restarts.
>What to try next????? Interfering with the boot process? How?

Well the telltale thing is Windows now confirms it found problems.
Something is apparently getting loaded at boot that locks the drive
preventing Windows from operating on it. Could be anything. Suspects
would be anti-virus, etc..

Hope the following helps you get over the hump:

http://www.vistax64.com/tutorials/67...sk-chkdsk.html

Above is a nice site with a lot of detailed help. I would try Method
Two or Three from Safe mode. Check the site for much more detail.
Basically you want to do it manually, hopefully from Command Prompt.

Type the following EXACTLY as it appear with the spaces shown:

chkdsk /r

or

chkdsk C: /r

When you answer y after you enter either of the above you are in
effect telling Windows to do what you tried earlier next time you boot
but it refused.

Commands entered directly at the command prompt window are more brute
force and should work.

Adam

Many thanks for resolving that - chkdsk /f ran fine from an elevated command
line. However, it appeared to show no problems, other than '5 unindexed files
processed'.

So I ran sfc /scannow (again), which told me that 'Windows Resource
Protection found corrupt files, but was unable to fix some of them. It
referred me to CBS.log, which I have examined in detail (!) and can find
nothing to support that result (unless either of the following do so: a)
several examples of duplicate directory ownership were ignored; b) very many
examples of 'move file' from "\SystemRoot\WinSXS\Temp\PendingRenames\......"
to "\SystemRoot\WinSXS\FileMaps\...").
There is NO mention of a corrupt file which cannot be repaired and indeed
the last line says "[SR] Repair complete".

I'm becoming extremely frustrated about this and I'd like to try a Repair
Installation (as I haven't yet installed SR1) - but, from what I read, I
can't, as Vista was installed on my new PC (Medion) and I only have a
Recovery Disc.

I would sooner avoid a full re-installation, due to the volume of data,
software, drivers, updates/patches and settings that I would have to
reinstate!

Do you have any other suggestions please?

John

"Adam Albright" wrote:

> On Mon, 21 Apr 2008 17:29:06 -0700, John Edwards
> <(E-Mail Removed)> wrote:
>
> >Adam
> >
> >Hoping for great things like Tomen, I tried to run CHKDSK as you described
> >but the scheduled operation on restart would not happen (twice). So I tried
> >it from the command prompt (without /F) and discovered the following issues:
> >
> >No bad records or sectors
> >8 orphaned files
> >Master file table's (MFT) BITMAP attribute is incorrect
> >The Volume Bitmap is incorrect
> >Windows found problems with the file system.
> >
> >As advised, I then tried to run chkdsk /f and was told that the drive
> >couldn't be locked and so it cannot run because the volume is in use by
> >another process. Asked if I wanted to schedule a run next time system
> >restarts - YES.
> >Immediately responds with a message: chkdsk could NOT schedule this volume
> >to be checked next time the sytem restarts.
> >What to try next????? Interfering with the boot process? How?
>
> Well the telltale thing is Windows now confirms it found problems.
> Something is apparently getting loaded at boot that locks the drive
> preventing Windows from operating on it. Could be anything. Suspects
> would be anti-virus, etc..
>
> Hope the following helps you get over the hump:
>
> http://www.vistax64.com/tutorials/67...sk-chkdsk.html
>
> Above is a nice site with a lot of detailed help. I would try Method
> Two or Three from Safe mode. Check the site for much more detail.
> Basically you want to do it manually, hopefully from Command Prompt.
>
> Type the following EXACTLY as it appear with the spaces shown:
>
> chkdsk /r
>
> or
>
> chkdsk C: /r
>
> When you answer y after you enter either of the above you are in
> effect telling Windows to do what you tried earlier next time you boot
> but it refused.
>
> Commands entered directly at the command prompt window are more brute
> force and should work.
>
>

On Tue, 22 Apr 2008 11:18:01 -0700, John Edwards
<(E-Mail Removed)> wrote:

>Adam
>
>Many thanks for resolving that - chkdsk /f ran fine from an elevated command
>line. However, it appeared to show no problems, other than '5 unindexed files
>processed'.
>
>So I ran sfc /scannow (again), which told me that 'Windows Resource
>Protection found corrupt files, but was unable to fix some of them. It
>referred me to CBS.log, which I have examined in detail (!) and can find
>nothing to support that result (unless either of the following do so: a)
>several examples of duplicate directory ownership were ignored; b) very many
>examples of 'move file' from "\SystemRoot\WinSXS\Temp\PendingRenames\......"
>to "\SystemRoot\WinSXS\FileMaps\...").
>There is NO mention of a corrupt file which cannot be repaired and indeed
>the last line says "[SR] Repair complete".
>
>I'm becoming extremely frustrated about this and I'd like to try a Repair
>Installation (as I haven't yet installed SR1) - but, from what I read, I
>can't, as Vista was installed on my new PC (Medion) and I only have a
>Recovery Disc.
>
>I would sooner avoid a full re-installation, due to the volume of data,
>software, drivers, updates/patches and settings that I would have to
>reinstate!
>
>Do you have any other suggestions please?

Not really. Interesting, I started today with Vista showing a BSOD.
While it recovered by simply rebooting, it launched chkdsk on it's own
and reported a whole bunch of errors, which it fixed. Everything seems
fine now on my system. If I were you I'd just watch it a couple days
and see if the problem fixes itself or gets worse.

If you want to gamble a bit if you haven't done it in awhile running
defrag might help since it will shuffle all kinds of data around using
different sectors. The risk is if something is really screwed up it
could hang in the middle of running defrag and put you in much worse
shape where you could end up with real serious data loss.

Adam

Glad your system has recovered, but I've had this problem for over a month
now (ever since I acquired an external HDD and first tried to use Backup!),
so I don't think it's going to go away by itself! Also, I run a defrag every
week - including this morning.
I found the Vistax64 Tutorials a fascinating source of information - and so
well written and laid out - is it a MS facility or indy?
I read up on the Repair Installation routine there, and decided to see
whether my disc would let me do it. After a false start (and after disabling
virus-checker and spyware - as well as UAC), it surprisingly let me choose
'upgrade' (without getting updates) and then seemed to be going well for a
couple of hours, until a reboot (at least the second) produced a hang on a
black screen (with just a flashing cursor top-left): great!
Without the benefit of any communication, I took the chance of re-booting in
safe mode, with the intention of trying to roll back the graphics driver (as
I know from bitter experience that the latest nVidia drivers cause JUST this
effect on my system - and nVidia (and Medion) don't answer my queries on
this!). However, before having a chance to do so, I was told that the upgrade
had failed and the 'previous version' of Windows was reinstated (apparently
perfectly). Maybe the safe mode restart caused the failure???

I might give it another go (perhaps while I mow the lawn!!!), but do you
have any tips on avoiding the same graphics problem (I thought I might delete
the downloads of the later nVidia drivers, but where would I find the failed
drivers which were unpacked from them before I rolled-back?); or any other
tips!!

Sorry this has strayed a fair way from your first advice!

John


"Adam Albright" wrote:

> On Tue, 22 Apr 2008 11:18:01 -0700, John Edwards
> <(E-Mail Removed)> wrote:
>
> >Adam
> >
> >Many thanks for resolving that - chkdsk /f ran fine from an elevated command
> >line. However, it appeared to show no problems, other than '5 unindexed files
> >processed'.
> >
> >So I ran sfc /scannow (again), which told me that 'Windows Resource
> >Protection found corrupt files, but was unable to fix some of them. It
> >referred me to CBS.log, which I have examined in detail (!) and can find
> >nothing to support that result (unless either of the following do so: a)
> >several examples of duplicate directory ownership were ignored; b) very many
> >examples of 'move file' from "\SystemRoot\WinSXS\Temp\PendingRenames\......"
> >to "\SystemRoot\WinSXS\FileMaps\...").
> >There is NO mention of a corrupt file which cannot be repaired and indeed
> >the last line says "[SR] Repair complete".
> >
> >I'm becoming extremely frustrated about this and I'd like to try a Repair
> >Installation (as I haven't yet installed SR1) - but, from what I read, I
> >can't, as Vista was installed on my new PC (Medion) and I only have a
> >Recovery Disc.
> >
> >I would sooner avoid a full re-installation, due to the volume of data,
> >software, drivers, updates/patches and settings that I would have to
> >reinstate!
> >
> >Do you have any other suggestions please?
>
> Not really. Interesting, I started today with Vista showing a BSOD.
> While it recovered by simply rebooting, it launched chkdsk on it's own
> and reported a whole bunch of errors, which it fixed. Everything seems
> fine now on my system. If I were you I'd just watch it a couple days
> and see if the problem fixes itself or gets worse.
>
> If you want to gamble a bit if you haven't done it in awhile running
> defrag might help since it will shuffle all kinds of data around using
> different sectors. The risk is if something is really screwed up it
> could hang in the middle of running defrag and put you in much worse
> shape where you could end up with real serious data loss.
>
>