Unable to see all modules

When I perform the following command (get-process firefox).modules I get a
long list of modules, but when I compare this with Process Explorer they are
somewhat different. I am able to see additional files when using Process
Explorer. In Process Explorer I can see .nls files. Why am I not able to
see all the files when I use the .modules in Powershell?

HermesNL wrote: This is what the SDK has to say about the object you're dealing with:

"A process module represents a.dll or .exe file that is loaded into a
particular process. A ProcessModule instance lets you view information
about a module, including the module name, file name, and module memory
details.

A process can load multiple modules into memory. For example,.exe files
that load additional .dll files have multiple modules."

This is simply not the correct property to get the info you're looking
for. That being said, I don't know what is or if you can even get it
from PowerShell...

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

On Mar 3, 12:54*pm, "Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com>
wrote: Yep, and viewing "DLLs" in Process Explorer is not quite the same
thing as enumerating modules on a .NET Process object. To be honest,
that view "DLLs" in procexp is probably not named quite right. While
process modules attached to a .net process object are always
executable images, the DLLs view in procexp also shows files mapped in
as data (as opposed to "image" or executable). NLS files are just data
files, and are not executable. To get this information from .NET, you
would _probably_ have to resort to p/invoke.

- Oisin