Commandd Prompt Will, Power Shell Won't

A beautiful Spot Light appeared on my lock screen and I wanted to save
it. I went to:

C:\Users\Boris\AppData\Local\Packages
\Microsoft.Windows.ContentDeliveryManager_cw5n1h2t xyewy\LocalState\Assets

and copied all files there out to

C:\Users\Boris\SpotLightPics, in order to have a place to batch rename
the spotlight files.

In Power Shell I performed

C:\Users\Boris\SpotLightPicsren *.* *.jpg

But Power Shell came back at me with "ren : Cannot process argument
because the value of argument "path" is not valid. Change the value of
the "path"argument and run the operation again."

Multiple tries or copy/pasting path didn't help.

I tried the same in plain old Command Prompt, and all went well.

Why the difference?

Also, there were only 19 Spot Light files in C:\Users\Boris\AppData\Local
\Packages\Microsoft.Windows.ContentDeliveryManager _cw5n1h2txyewy
\LocalState\Assets, none of which I'd ever seen, and the one I wanted to
save was not there. The dates on the files were splotchy; five this
month, some one month last year, but no order whatsoever. In general,
there were two copies of each file, one landscape, and one portrait.

"Boris" wrote

| In Power Shell I performed
|
| C:\Users\Boris\SpotLightPicsren *.* *.jpg
|
| But Power Shell came back at me with "ren : Cannot process argument
| because the value of argument "path" is not valid. Change the value of
| the "path"argument and run the operation again."
|

Maybe PS doesn't handle wildcards? There's a group
for that he
microsoft.public.windows.powershell

| I tried the same in plain old Command Prompt, and all went well.
|
| Why the difference?
|

I don't use PS, but I do know the two things are
entirely different. Basic console window is essentially
DOS. PS is an extended set of applets, designed to
mimic Linux console, and to a great extent wrapping
..Net. (Microsoft decided that if they're going to build
a new, ugly language to seduce Linux network admins,
that belongs in 1993 along with the Linux console fanatics,
then they might as well go all the way and make every
aspect as bad as possible. They tried to make the
ugliest, least useful system ever with WMI/WBEM, but
no one used it, so they had to try again.

Boris wrote:

Why the difference?

In short, pretending that you can use old "DOS" habits inside powershell
will bite you over and over again.

The arguments and switches to powershell cmdlets are different even
though some of them have the same name as the cmd.exe built-ins.

"Andy Burns" wrote

| In short, pretending that you can use old "DOS"
| habits inside powershell will bite you over and over again.

Did he pretend or was he bitten by bad design?

More specifically, the dubious decision was made
to allow DOS names to be reused as aliases. Why
aliases at all? It's idiotic. It's like saying that you can
use angry or furious to mean annoyed, in case you're
too lazy to think about it. That undermines language,
with only the pretense of making it easier to learn
new things.

|
| The arguments and switches to powershell cmdlets are different even
| though some of them have the same name as the cmd.exe built-ins.

They don't have the same name. ren is an
*alias* of Rename-Item.

https://docs.microsoft.com/en-us/pow...w=powershell-6

https://ss64.com/ps/rename-item.html

Mayayana wrote:

the dubious decision was made to allow DOS names to be reused as
aliases. Why aliases at all?

You're right, when I use powershell I avoid aliases entirely