3

Some of my shortcuts in Windows are pointing to targets that look like CLSIDs, and I cannot modify the target, it's grayed out. They look like this: {ED228FDF-9EA8-4870-83b1-96b02CFE0D52} (non-working example).

Is there a way to "start" these CLSIDs directrly from the command line (without using the link), ie. if I know a CLSID, can I start it from the command line, without making a shortcut?

I've tried to start it with XP like start {ED228FDF-9EA8-4870-83b1-96b02CFE0D52}, but it gives a "file not found" type of error.

n611x007
  • 6,336
  • 14
  • 61
  • 88
  • What are these shortcuts to? – Karan Apr 21 '13 at 21:55
  • @Karan my current target is a 'connect to VPN' icon that was created by an installer. But I recall from 9x days that the Recycle bin was accessible this way... actually when I've tried to confirm this, I ran into http://www.autohotkey.com/docs/misc/CLSID-List.htm – n611x007 Apr 21 '13 at 22:24
  • @Karan No, I mean this notation with the `::` prefix actually works with start/run too, not just AHK. And also with `start`. But I wonder why does some of them not work, what is this notation and what does windows actually do? It does *not* work with my VPN starter. – n611x007 Apr 21 '13 at 22:29

1 Answers1

4

See the Canonical Names of Control Panel Items article for the complete list, grouped according to the Windows version supported. You can even create shortcuts using explorer /e,::{CLSID}.

As per this source:

A shell namespace path may be a file system path but may also refer to class objects by using the notation of two colons followed by a CLSID in curly braces.

The IShellFolder shell interface's ParseDisplayName method is responsible for handling "references to items in the [shell] namespace that have a GUID associated with them using the "::{GUID}" syntax".

Karan
  • 55,947
  • 20
  • 119
  • 191