Hkcu exe

You are technically correct the Command Prompt Shell with Custom Shell Support does not support different shells for different users in so much as you can't configure that in ICE. However, as I noted above, you can make registry changes to do that. I essentially had configured my setup to have the default shell as explorer. I believe this is how most general Windows users change their shell.

I did not properly setup my image. I needed the default shell to be eshell. This makes the custom shell the default shell and all this could've been done with ICE to begin. I could then override the custom shell per user as I was dong before. The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. If so, it's okay that it's running. I just didn't want it to be something I didn't want.

Thanks for the info! Yep, that should be the entry. But I rather doubt it runs at startup, with no data to tell it what to start. Normally, there would be a path to the executable. Without the data, as noted above by SD2, it's just a dead entry taking up space.

In other words Mike, Leave it or delete it from the registry after using the precaution which should become a routine habit, of exporting that particular key, prior to a change or edit. In this case, you as I had with my T. The key was leftover. Should you ever decide to re-enable this Sonic thingy at startup yuck! No big deal, the choice is yours. Another mystery solved. I'll just things alone since it isn't doing anything and not taking up much space.

I'm sure I have other useless stuff that is taking up more space. Show Ignored Content. Share This Page Tweet. Your name or email address: Do you already have an account? Privacy policy. Because registry keys are items on PowerShell drives, working with them is very similar to working with files and folders. One critical difference is that every item on a registry-based PowerShell drive is a container, just like a folder on a file system drive.

However, registry entries and their associated values are properties of the items, not distinct items. You can show all items directly within a registry key by using Get-ChildItem.

Add the optional Force parameter to display hidden or system items. You can also specify this registry path by specifying the registry provider's name, followed by The registry provider's full name is Microsoft.

Any of the following commands will list the contents directly under HKCU:. These commands list only the directly contained items, much like using DIR in Cmd. To show contained items, you need to specify the Recurse parameter. To list all registry keys in HKCU: , use the following command.