Folder that can't be deleted

  • Thread starter Thread starter ms
  • Start date Start date
ms said:
[snip...]
The instruction that I and Pegasus gave you are run at the Command
Prompt, not in the Start Menu Run Box. To open a Command Prompt type
CMD in the Run box and then click on OK or press Enter. A Command
session will start, run the commands at the black screen that just
opened. To drag items to the Command Prompt grab them from the
Explorer GUI and drag them to the minimized cmd.exe on the Taskbar and
hold it for a second or two, the Command Prompt window will maximize
and you can then drop the item at the prompt.
Click to expand...

Thanks for the data. It worked just as you described. After dragging, I
could see the proper path statement for the file in the Command window.
Hit Enter, saw "are you sure"- seeing that was a good sign, hit y, Enter,
got to C prompt again.

But back in windows, the corrupted folder is still there.

Please confirm, but at this point I guess I go back to Pegasus reply.
Click to expand...

Did you run a chkdsk as suggested by Dave?

John
 
ms said:
[snip...]
The instruction that I and Pegasus gave you are run at the Command
Prompt, not in the Start Menu Run Box. To open a Command Prompt type
CMD in the Run box and then click on OK or press Enter. A Command
session will start, run the commands at the black screen that just
opened. To drag items to the Command Prompt grab them from the
Explorer GUI and drag them to the minimized cmd.exe on the Taskbar
and hold it for a second or two, the Command Prompt window will
maximize and you can then drop the item at the prompt.
Click to expand...

Thanks for the data. It worked just as you described. After dragging,
I could see the proper path statement for the file in the Command
window. Hit Enter, saw "are you sure"- seeing that was a good sign,
hit y, Enter, got to C prompt again.

But back in windows, the corrupted folder is still there.

Please confirm, but at this point I guess I go back to Pegasus reply.
Click to expand...

Did you run a chkdsk as suggested by Dave?

John
Click to expand...
My hesitation is this: You experts can run "repair" and never think
twice. For me, I learned that cleaners, fixers, tweakers, can be real
trouble. So I try to be careful.

I just ran plain chkdsk:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>chkdsk
The type of the file system is NTFS.
Volume label is C drive.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
**File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
3454132 KB in 18595 files.
6052 KB in 1851 indexes.
0 KB in bad sectors.
98620 KB in use by the system.
65536 KB occupied by the log file.
11799304 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
2949826 allocation units available on disk.

The ** is IMO of interest. But I realize this is checking C, my data is
in D, the bad folder is in D.

So should I now run chkdsk D, or do I even need to run \R ?

And if I do run \R, should it run first on C, then on D?

What next?

And I hope Dave and Pegasus also see this. All you fellows have been very
helpful.

ms
 
ms said:
ms wrote:

[snip...]


The instruction that I and Pegasus gave you are run at the Command
Prompt, not in the Start Menu Run Box. To open a Command Prompt type
CMD in the Run box and then click on OK or press Enter. A Command
session will start, run the commands at the black screen that just
opened. To drag items to the Command Prompt grab them from the
Explorer GUI and drag them to the minimized cmd.exe on the Taskbar
and hold it for a second or two, the Command Prompt window will
maximize and you can then drop the item at the prompt.

Thanks for the data. It worked just as you described. After dragging,
I could see the proper path statement for the file in the Command
window. Hit Enter, saw "are you sure"- seeing that was a good sign,
hit y, Enter, got to C prompt again.

But back in windows, the corrupted folder is still there.

Please confirm, but at this point I guess I go back to Pegasus reply.
Click to expand...

Did you run a chkdsk as suggested by Dave?

John
Click to expand...

My hesitation is this: You experts can run "repair" and never think
twice. For me, I learned that cleaners, fixers, tweakers, can be real
trouble. So I try to be careful.

I just ran plain chkdsk:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>chkdsk
The type of the file system is NTFS.
Volume label is C drive.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
**File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
3454132 KB in 18595 files.
6052 KB in 1851 indexes.
0 KB in bad sectors.
98620 KB in use by the system.
65536 KB occupied by the log file.
11799304 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
2949826 allocation units available on disk.

The ** is IMO of interest. But I realize this is checking C, my data is
in D, the bad folder is in D.

So should I now run chkdsk D, or do I even need to run \R ?

And if I do run \R, should it run first on C, then on D?

What next?

And I hope Dave and Pegasus also see this. All you fellows have been very
helpful.
Click to expand...

You need to run chkdsk on the D: drive where the file is located.

John
 
ms said:
ms wrote:



[snip...]


The instruction that I and Pegasus gave you are run at the Command
Prompt, not in the Start Menu Run Box. To open a Command Prompt
type CMD in the Run box and then click on OK or press Enter. A
Command session will start, run the commands at the black screen
that just opened. To drag items to the Command Prompt grab them
from the Explorer GUI and drag them to the minimized cmd.exe on the
Taskbar and hold it for a second or two, the Command Prompt window
will maximize and you can then drop the item at the prompt.

Thanks for the data. It worked just as you described. After
dragging, I could see the proper path statement for the file in the
Command window. Hit Enter, saw "are you sure"- seeing that was a
good sign, hit y, Enter, got to C prompt again.

But back in windows, the corrupted folder is still there.

Please confirm, but at this point I guess I go back to Pegasus
reply.

Did you run a chkdsk as suggested by Dave?

John
Click to expand...

My hesitation is this: You experts can run "repair" and never think
twice. For me, I learned that cleaners, fixers, tweakers, can be real
trouble. So I try to be careful.

I just ran plain chkdsk:

The ** is IMO of interest. But I realize this is checking C, my data
is in D, the bad folder is in D.

So should I now run chkdsk D, or do I even need to run \R ?

And if I do run \R, should it run first on C, then on D?

What next?

And I hope Dave and Pegasus also see this. All you fellows have been
very helpful.
Click to expand...

You need to run chkdsk on the D: drive where the file is located.

John
Click to expand...
Below is on D partition

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
**File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)..
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
11284344 KB in 80879 files.
31076 KB in 7001 indexes.
0 KB in bad sectors.
227668 KB in use by the system.
65536 KB occupied by the log file.
3815020 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
953755 allocation units available on disk.

D:\>

** still shows OK. ??

According to my data on chkdsk, they expect the error should show up
above, it does not.

Run chkdsk\r anyway?

ms
 
ms said:
Below is on D partition

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
**File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)..
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
11284344 KB in 80879 files.
31076 KB in 7001 indexes.
0 KB in bad sectors.
227668 KB in use by the system.
65536 KB occupied by the log file.
3815020 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
953755 allocation units available on disk.

D:\>

** still shows OK. ??

According to my data on chkdsk, they expect the error should show up
above, it does not.

Run chkdsk\r anyway?
Click to expand...

Run chkdsk /f

Make sure that you have a backup of your files before you run this.

John
 
Run chkdsk /f

Make sure that you have a backup of your files before you run this.

John
Click to expand...

I didn't think I had to ask this, but I give up.
----
C:\>d:

D:\>chkdsk\f
The system cannot find the path specified.

D:\>
----

I was all ready to finally run chkdsk\f, and you see the message. What is
the correct Dos command, if that's not it?

Hope you see this soon, as I again saved all my data, that's a drag.

ms
 
ms said:
I didn't think I had to ask this, but I give up.
----
C:\>d:

D:\>chkdsk\f
The system cannot find the path specified.

D:\>
----

I was all ready to finally run chkdsk\f, and you see the message. What
is the correct Dos command, if that's not it?

Hope you see this soon, as I again saved all my data, that's a drag.

ms
Click to expand...

Correction to above: I had the slash wrong. Corrected it and ran as
follows:
---
C:\>d:

D:\>chkdsk/f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is D drive.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
11512120 KB in 82213 files.
31824 KB in 7351 indexes.
0 KB in bad sectors.
227156 KB in use by the system.
65536 KB occupied by the log file.
3587008 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
896752 allocation units available on disk.

------------
Again, it shows file verification OK

I just tried to delete the folder, still a problem.

My chkdsk data says chkdsk/r is the last resort.

Should I run it, based upon above?

ms
 
ms said:
snip

Correction to above: I had the slash wrong. Corrected it and ran as
follows:
---
C:\>d:

D:\>chkdsk/f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is D drive.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

15358108 KB total disk space.
11512120 KB in 82213 files.
31824 KB in 7351 indexes.
0 KB in bad sectors.
227156 KB in use by the system.
65536 KB occupied by the log file.
3587008 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
896752 allocation units available on disk.

------------
Again, it shows file verification OK

I just tried to delete the folder, still a problem.

My chkdsk data says chkdsk/r is the last resort.

Should I run it, based upon above?

ms
Click to expand...

I read Dave's reply again, and went ahead with /r. Below is the report:

C:\>d:

D:\>chkdsk/r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is D drive.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

15358108 KB total disk space.
11512132 KB in 82213 files.
31824 KB in 7351 indexes.
0 KB in bad sectors.
227156 KB in use by the system.
65536 KB occupied by the log file.
3586996 KB available on disk.

4096 bytes in each allocation unit.
3839527 total allocation units on disk.
896749 allocation units available on disk.

D:\>

I rebooted, then tried to delete the file, still no luck. The rest of my
data seems OK after /r.

Maybe open a new thread, based upon your reply.

ms
 
ms said:
I didn't think I had to ask this, but I give up.
----
C:\>d:

D:\>chkdsk\f
The system cannot find the path specified.

D:\>
----

I was all ready to finally run chkdsk\f, and you see the message. What is
the correct Dos command, if that's not it?

Hope you see this soon, as I again saved all my data, that's a drag.
Click to expand...

Run the Command from the C: prompt:

chkdsk d: /f

Pay attention to spaces and the forward / slash (as opposed to backslash
\). For help on the command do: chkdsk /?

John
 
ms said:
I used a utility that extracts files instead of running a setup file.
Have used it many times with no problems.
Today, ran the utility Filezilla through the extraction process,
resulting in a new folder with the extracted files. I decided to delete
the resultant new folder with extracted files.
The normal delete removed most files in the folder, but the remainder is
a problem. The folder with subfolders and a few files will not delete.
All below have todays date.
I now have a folder with normal file name, 24,456 bytes, no attribute.
In it are 2 subfolders: "i" (name), in it is one file with a text type
symbol, 6,656 bytes.
The other subfolder is "u", a single file in it as above, 206 bytes.
Then there is a separate file, as above, 18,432 bytes.
In trying to delete, I get error messages, can't delete any of the above.
I tried several utilities that delete after reboot, no luck.
I reverted to yesterday's registry, no luck.
How to delete the folder?
Click to expand...

Open a command prompt, carefully type the following command line
and confirm the removal.

rd /s D:\DOWNLOAD\FileZilla_3.2.1_win32-setup

If this doesn't help, see
http://support.microsoft.com/kb/320081

Ben
 
Open a command prompt, carefully type the following command line
and confirm the removal.

rd /s D:\DOWNLOAD\FileZilla_3.2.1_win32-setup

If this doesn't help, see
http://support.microsoft.com/kb/320081

Ben
Click to expand...

Ben, thanks very much. After trying several methods with no luck, this
command worked right off. The corrupted folder is gone.

Now, I'm older and bad sleep, but IIRC, weren't you also very helpful to
me awhile ago on the W98 newsgroup? I still use several W98 computers at
home. Back in those days my moniker was Mike Sa.

Thanks again

ms
 
ms said:
I used a utility that extracts files instead of running a setup file.
Have used it many times with no problems.

Today, ran the utility Filezilla through the extraction process,
resulting in a new folder with the extracted files. I decided to delete
the resultant new folder with extracted files.

The normal delete removed most files in the folder, but the remainder is
a problem. The folder with subfolders and a few files will not delete.
All below have todays date.

I now have a folder with normal file name, 24,456 bytes, no attribute.
In it are 2 subfolders: "i" (name), in it is one file with a text type
symbol, 6,656 bytes.

The other subfolder is "u", a single file in it as above, 206 bytes.

Then there is a separate file, as above, 18,432 bytes.

In trying to delete, I get error messages, can't delete any of the above.

I tried several utilities that delete after reboot, no luck.

I reverted to yesterday's registry, no luck.

How to delete the folder?

ms
Click to expand...

Thanks to all for the help.

ms
 
ms said:
Ben, thanks very much. After trying several methods with no luck, this
command worked right off. The corrupted folder is gone.
Click to expand...

Glad it worked.
Now, I'm older and bad sleep, but IIRC, weren't you also very helpful to
me awhile ago on the W98 newsgroup? I still use several W98 computers at
home. Back in those days my moniker was Mike Sa.
Click to expand...

I remember.
Thanks again

ms
Click to expand...

Ben
 
Delete it from the recovery console.
Click to expand...

I have never used the Recovery Console function.

Start/Programs, not there, searched on C, no luck. Looked in Control Panel,
not there either.

Where in windows do I find it?

And from your post, I assume when I open it, there is a way to search for
that folder?

ms
 
You must have missed it.

First you'll need to Control Panel|Admin Tools|Local Security Policy
Recovery console: "Allow floppy copy and access to all drives/folders" set
to enabled

Then from the recovery console command line;
SET allowallpaths = TRUE


To start the Recovery Console, start the computer from the Windows 2000
Setup CD-Rom. At the "Welcome to Setup" screen. Press F10 or R to repair a
Windows 2000 installation, and then press C to use the Recovery Console. The
Recovery Console then prompts you for the administrator password. If you do
not have the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Thanks for the help. See below
You must have missed it.

First you'll need to Control Panel|Admin Tools|Local Security Policy
Recovery console: "Allow floppy copy and access to all drives/folders"
set to enabled
Click to expand...
I see Control Panel|Admin Tools|Local Security Policy, but under that the
options don't include Recovery Console.

I do see: Security Settings: Account policies, Local policies, Public Key
policies, IP Security policies

I looked under each but did not see "Allow floppy copy and access to all
drives/folders"
Then from the recovery console command line;
SET allowallpaths = TRUE


To start the Recovery Console, start the computer from the Windows
2000 Setup CD-Rom. At the "Welcome to Setup" screen. Press F10 or R to
repair a Windows 2000 installation, and then press C to use the
Recovery Console. The Recovery Console then prompts you for the
administrator password. If you do not have the correct password,
Recovery Console does not allow access to the computer. If an
incorrect password is entered three times, the Recovery console quits
and restarts the computer. Note If the registry is corrupted or
missing or no valid installations are found, the Recovery Console
starts in the root of the startup volume without requiring a password.
You cannot access any folders, but you can carry out commands such as
chkdsk, fixboot, and fixmbr for limited disk repairs. Once the
password has been validated, you have full access to the Recovery
Console, but limited access to the hard disk. You can only access the
following folders on your computer: drive root, %windir% or
%systemroot%
Click to expand...
A long story. My machine was custom built by a tech, at the time W2K was
brand new to me so I didn't think to ask what passwords he set into the
machine. That was 4 years ago, so I'm sure he does not now remember them.
Awhile ago something changed so on bootup I see the usual user password
screen, but can't guess the password. No big problem.

I am left with Administrator rights, but from your above, it will do no
good to start that process with the OS CD. It may be he did not think
highly of the Recovery Console, so he didn't install it. I hadn't missed
it up to now, as the system is very stable, and ERUNT does a good
registry backup. In the past, I certainly heard lots of mixed comments
about the Recovery Console.

I checked through all my password utilities, none show the admin
password.

How to detect it, or advice?

ms
 
Back
Top