Windows 10: matching wildcards in dir

In a folder I have several files starting with test, like test00, test0000, test1.txt, test1111, test 01.txt

If I do a dir test0*

I expect to get all files which match test0* like test00 and test0000 but I also get test 01.txt and I'm not sure why. I mean "test 01.txt" to my thinking should not match test0*, right? wrong?

I've been programming and using Windows since NT so now I feel kind of stupid.

Or not??

RON

:)

 

Results of a filename search giving unrelated results along with correct results

The 8.3 file name probably contains the string "0288". You can find out with this Console command:

dir /x 0857*.*

Please post the exact location of these files if you need more detailed instructions.

 

Can't delete .exe file - "Could not find this item","This is no longer located in C:\Users\Owner\Downloads." "Verify the item's location and try again."

I solved this problem by using the DEL command with a wildcard *

Open a command window and run as administrator. Navigate to the location of the offending file

Example:

Where test. is the problem file

c:\Users\test\AppData\Local\Temp\

at the prompt type DEL and then the file name followed by the wildcard

DEL test*

and return

All files with the name test and any extension, (including none) will be deleted

type DIR to verify the file has been deleted.

You can now delete any folder structure that remains

 

For me dir works as expected in powershell but not cmd.

cmd ignores the space in the filename (but not in the comparator eg dir "d:\temp\test "*)

Code: Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> dir d:\temp Directory: D:\temp Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 10-Oct-17 22:09 6 test 0.txt -a---- 10-Oct-17 22:24 0 test 2.txt -a---- 10-Oct-17 22:04 6 test0.txt -a---- 10-Oct-17 22:04 6 test01.txt -a---- 10-Oct-17 22:24 0 test2.txt PS C:\WINDOWS\system32> dir d:\temp\test0* Directory: D:\temp Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 10-Oct-17 22:04 6 test0.txt -a---- 10-Oct-17 22:04 6 test01.txt PS C:\WINDOWS\system32> cmd Microsoft Windows [Version 10.0.16299.15] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>dir d:\temp\test0* Volume in drive D has no label. Volume Serial Number is 646D-8050 Directory of d:\temp 10-Oct-17 22:04 6 test0.txt 10-Oct-17 22:04 6 test01.txt 10-Oct-17 22:09 6 test 0.txt 3 File(s) 18 bytes 0 Dir(s) 30,857,822,208 bytes free C:\WINDOWS\system32>dir "d:\temp\test "* Volume in drive D has no label. Volume Serial Number is 646D-8050 Directory of d:\temp 10-Oct-17 22:09 6 test 0.txt 10-Oct-17 22:24 0 test 2.txt 2 File(s) 6 bytes 0 Dir(s) 30,857,822,208 bytes free C:\WINDOWS\system32>dir "d:\temp\test0"* Volume in drive D has no label. Volume Serial Number is 646D-8050 Directory of d:\temp 10-Oct-17 22:04 6 test0.txt 10-Oct-17 22:04 6 test01.txt 10-Oct-17 22:09 6 test 0.txt 3 File(s) 18 bytes 0 Dir(s) 30,857,822,208 bytes free[/quote] Not sure of the solution (except to use powershell)

 

THANKS! That "cleared" it up. I mean, it is something for some reason I never knew. Unfortunately this is not being run in either CMD or Powershell but in .NET/C#.

It's not a problem in my code, I was just surprised.

Well, it could be a problem for users who expect one thing and get another. If so I'll show them your explanation.

RON