Windows 10: Batch file no report from external hard drive

I have created this batch file that I often use in a command prompt to remove .tmp., .bak, and other files created by a program that I use:


del c:\data\*.wbk /s
del c:\data\music\*.clp /s
del c:\*.tmp /s
del c:\data\music\*.asv /s
del c:\data\music\*.asvx /s
del c:\*.bak /s
del c:\*.bakx /s
del c:\*.cvr /s
del I:\Finale25TempFolder\*.tmp

The c: directories always report which files are deleted, which files should be but wouldn't be deleted, and if no files to be deleted were found. When the command reaches the I: drive (only that one folder there), the .tmp files are deleted, so the command is working, but there is no report. The I: drive is a Western Digital Passport portable drive. How do I get the I: drive in this batch file to report as do the c: drive items?


:)

 

CMD commands not working in windows 10

I have Batch files which I use to backup new data from my PC to USB and External drive, as well as External Drive to my laptop. These have been working fine for some years now.

However my Win10 laptop currently does not recognise any CMD prompts; all Administrator run commands end up with the following:

"{command eg XCOPY, RUN, IPCONFIG etc.} is not recognized as an internal or external command,operable program or batch file."

Duplicating the process by double clicking the batch file from either the laptop or the same one on the external Hard drive, opens the CMD window, quickly scrolls through the commands and then closes

But on inspection, no commands at all have succeeded.

The very same batch files (with different drive letters) still work fine between my PC, External Drive and USB.

Please advise.

 

Check disk on a 1 bad sector but drive is 88% healthy, sshd 2 b mbr

The results are as follows;

U:\>

U:\>Stage 1: Examining basic file system structure ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1048064 file records processed.

'1048064' is not recognized as an internal or external command,

operable program or batch file.

U:\>File verification completed.

'File' is not recognized as an internal or external command,

operable program or batch file.

U:\> 8622 large file records processed.

'8622' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 bad file records processed.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 2: Examining file name linkage ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 17170 reparse records processed.

'17170' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1155756 index entries processed.

'1155756' is not recognized as an internal or external command,

operable program or batch file.

U:\>Index verification completed.

'Index' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 unindexed files scanned.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 unindexed files recovered to lost and found.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\> 17170 reparse records processed.

'17170' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 3: Examining security descriptors ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\>Security descriptor verification completed.

'Security' is not recognized as an internal or external command,

operable program or batch file.

U:\> 53847 data files processed.

'53847' is not recognized as an internal or external command,

operable program or batch file.

U:\>CHKDSK is verifying Usn Journal...

Invalid parameter - verifying

U:\> 35872856 USN bytes processed.

'35872856' is not recognized as an internal or external command,

operable program or batch file.

U:\>Usn Journal verification completed.

'Usn' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 4: Looking for bad clusters in user file data ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1048048 files processed.

'1048048' is not recognized as an internal or external command,

operable program or batch file.

U:\>File data verification completed.

'File' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 5: Looking for bad, free clusters ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 297247241 free clusters processed.

'297247241' is not recognized as an internal or external command,

operable program or batch file.

U:\>Free space verification is complete.

'Free' is not recognized as an internal or external command,

operable program or batch file.

U:\>Adding 1 bad clusters to the Bad Clusters File.

'Adding' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Windows has made corrections to the file system.

'Windows' is not recognized as an internal or external command,

operable program or batch file.

U:\>No further action is required.

'No' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>1950916280 KB total disk space.

'1950916280' is not recognized as an internal or external command,

operable program or batch file.

U:\> 760452004 KB in 448531 files.

'760452004' is not recognized as an internal or external command,

operable program or batch file.

U:\> 263136 KB in 53848 indexes.

'263136' is not recognized as an internal or external command,

operable program or batch file.

U:\> 4 KB in bad sectors.

'4' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1212176 KB in use by the system.

'1212176' is not recognized as an internal or external command,

operable program or batch file.

U:\> 65536 KB occupied by the log file.

'65536' is not recognized as an internal or external command,

operable program or batch file.

U:\>1188988960 KB available on disk.

'1188988960' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\> 4096 bytes in each allocation unit.

'4096' is not recognized as an internal or external command,

operable program or batch file.

U:\> 487729070 total allocation units on disk.

'487729070' is not recognized as an internal or external command,

operable program or batch file.

U:\> 297247240 allocation units available on disk.

'297247240' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>C:\WINDOWS\system32>

So after butting the drive back in the orignal pc healt status at 92%.

Going to rma the drive.

 

Yes. I've tested that on one of my external drives. Seems you only get the report of deletions if you used the /s option (which you didn't for I. Silly, but even though you don't need it, add the /s to the 'I:' line and it will work like all the others.