Re: working on a specific registry entry

Not sure exactly what you're after, but possibly something like

$key = Get-Item "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs"
$key.GetValueNames() | `
where {([io.path]::GetFileName($_)).Contains('mscor')}

--
Jon


"Thufir" <hawat.thufir@xxxxxx> wrote in message
news:1d9d446c-5efe-4208-90e9-2bcc41f9d5f0@xxxxxx

"Thufir" <hawat.thufir@xxxxxx> wrote in message
news:5a95c08a-1033-49b8-8a7a-82d8ee6b1303@xxxxxx
All the shared DLLs. Everything you see in the right pane when clicking the
key in the left pane within regedit.
It returns those entries there containing 'mscor' in their name.

It doesn't actually touch the file itself. It just parses the path like a
string, and examines the relevant info - in this particular case the
filename.


--
Jon

"Thufir" <hawat.thufir@xxxxxx> wrote in message
news:3fe67612-fd09-4ef6-bf78-fd0161abfa6a@xxxxxx

To process the data in the entry, you could use something like ....

#-------------------
$key = Get-Item "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs"

foreach ($ValueKey in $key.GetValueNames()) {
if ($Key.GetValue($ValueKey) -eq 4096) {$ValueKey}
}
#-------------------

There are better tools around to search all the hives in their entirety.
You'd be sitting there a long time otherwise I would suspect. I wouldn't
personally recommend Powershell for that.

This is one such tool, which is pretty good...

RegScanner
http://www.nirsoft.net/utils/regscanner.html


--
Jon

"Jon"
Well if one is going to run and learn another
process well then perhaps try the free IIS's
Microsoft's (local or remote) data parser,
Log Parser 2.2 (with built-in Microsoft
ChartSpace chart maker)!

Log Parser parses almost anything in
almost any Windows language. If Log
Parse doesn't parse what one needs
(either via the Log Parser's command
line usage or by Log Parser's scripting
each parsed line field by field) well then
one can add into Log Parser their needed
parsing!

As for the registry:

LogParser.exe -h -i:reg

Input format: REG (Registry properties)
Returns properties of registry keys and values

Notice: IIS does not need to be running
or installed in order to use Log Parser
for either data parsing or chart making.

Search the Internet
(and this newsgroup)
for usage of:

Microsoft's Log Parser
command line usage,
or fully script enabled
either in COM or .NET
(from the IIS group)

Remember, ever since PowerShell
added HTTP / HTTPS usage (like IIS)
Log Parser became PowerShell's data
parser (like Log Parser is for IIS) too!

"Flowering Weeds" <floweringnoweedsno@xxxxxx> wrote in message
news:up1azvEvIHA.3564@xxxxxx
Nice plug. Are those flowering weeds legal?

--
Jon