Using the dir command in a cmd window, results are not correct/as expected

0

Have a directory C:\...platform-tools, contents include abd.exe.

dir lists all the files in the directory.

dir a* list all files in the directory starting with the letter a.

dir ab* results in File Not Found;

abd results in File Not Found.;

Tried rebooting. Would a corrupt file cause this? Any idea what's wrong?

Stephen Schachter

Posted 2019-06-01T19:26:24.427

Reputation: 1

1Which version of Windows? Standard command line (e.g. cmd.exe)? A screen shot would help. – willus – 2019-06-01T19:32:12.387

Windows 10, standard cmd line. – Stephen Schachter – 2019-06-01T19:57:23.647

1The standard Win 10 dir command should definitely show abd.exe with ab* as an argument. Difficult to diagnose without more info. Did you try attrib on abd.exe to see if it has any strange attributes? – willus – 2019-06-01T20:04:28.587

Close this; I am an idiot, mis-typed, feel very silly, thanks for the help! – Stephen Schachter – 2019-06-01T22:43:48.020

I believe you can delete your own question that has no answers. There should be a "delete" link somewhere under tags. – Kamil Maciorowski – 2019-06-02T09:07:48.213

No answers