The Win32_ModuleLoadTrace event WMI class indicates that a process has loaded a new module.
Methods
Win32_ModuleLoadTrace has no methods.
Properties
Win32_ModuleLoadTrace returns 9 properties:
'DefaultBase','FileName','ImageBase','ImageChecksum','ImageSize','ProcessID',
'SECURITY_DESCRIPTOR','TIME_CREATED','TimeDateSTamp'
Unless explicitly marked as writeable, all properties are read-only. Read all properties for all instances:
Get-CimInstance -ClassName Win32_ModuleLoadTrace -Property *
Most WMI classes return one or more instances.
When
Get-CimInstance
returns no result, then apparently no instances of class Win32_ModuleLoadTrace exist. This is normal behavior.Either the class is not implemented on your system (may be deprecated or due to missing drivers, i.e. CIM_VideoControllerResolution), or there are simply no physical representations of this class currently available (i.e. Win32_TapeDrive).
DefaultBase
Default base address for loading the image, as listed in the binary image header. If the requested address is unavailable, the image is loaded at the ImageBase address, which causes recalculation of images addresses.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property DefaultBase
FileName
File name of the loaded module from the binary image header.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property FileName
ImageBase
Base address where the module is loaded into process memory.
For more information about using uint64 values in scripts, see Scripting in WMI.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property ImageBase
ImageChecksum
Binary image checksum for the module as listed in the image header. The image checksum is a hash that is used to verify that the image has not been changed. The hash is usually set when the module is linked and is not an encryption mechanism.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property ImageChecksum
ImageSize
Size, in bytes, of the loaded module.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property ImageSize
ProcessID
Identifies the process that loaded the module.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property ProcessID
SECURITY_DESCRIPTOR
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property SECURITY_DESCRIPTOR
TIME_CREATED
For more information about using uint64 values in scripts, see Scripting in WMI.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property TIME_CREATED
TimeDateSTamp
Binary image time stamp as listed in the image header. TimeDateSTamp is used with FileName and ImageSize to identify the binary image uniquely.
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property TimeDateSTamp
Examples
List all instances of Win32_ModuleLoadTrace
Get-CimInstance -ClassName Win32_ModuleLoadTrace
Learn more about Get-CimInstance
and the deprecated Get-WmiObject
.
View all properties
Get-CimInstance -ClassName Win32_ModuleLoadTrace -Property *
View key properties only
Get-CimInstance -ClassName Win32_ModuleLoadTrace -KeyOnly
Selecting Properties
To select only some properties, pipe the results to Select-Object -Property a,b,c
with a comma-separated list of the properties you require. Wildcards are permitted.
Get-CimInstance
always returns all properties but only retrieves the ones that you specify. All other properties are empty but still present. That’s why you need to pipe the results into Select-Object
if you want to limit the visible properties, i.e. for reporting.
Selecting Properties
The code below lists all available properties. Remove the ones you do not need:
$properties = 'DefaultBase',
'FileName',
'ImageBase',
'ImageChecksum',
'ImageSize',
'ProcessID',
'SECURITY_DESCRIPTOR',
'TIME_CREATED',
'TimeDateSTamp'
Get-CimInstance -ClassName Win32_ModuleLoadTrace | Select-Object -Property $properties
Limiting Network Bandwidth
If you work remotely, it makes sense to limit network bandwidth by filtering the properties on the server side, too:
Get-CimInstance -Class Win32_ModuleLoadTrace -Property $property |
Select-Object -Property $property
Selecting Instances
To select some instances, use Get-CimInstance and a WMI Query. The wildcard character in WMI Queries is % (and not “*”).
The parameter -Filter runs a simple query.
Listing all instances where the property Caption starts with “A”
Get-CimInstance -Class Win32_ModuleLoadTrace -Filter 'Caption LIKE "a%"'
Using a WQL Query
The parameter -Query uses a query similar to SQL and combines the parameters -Filter and -Property. This returns all instances where the property Caption starts with “A”, and returns the properties specified:
Get-CimInstance -Query "SELECT TimeDateSTamp, DefaultBase, ImageBase, SECURITY_DESCRIPTOR FROM Win32_ModuleLoadTrace WHERE Caption LIKE 'a%'"
Any property you did not specify is still present but empty. You might need to use
Select-Object
to remove all unwanted properties:Get-CimInstance -Query "SELECT TimeDateSTamp, DefaultBase, ImageBase, SECURITY_DESCRIPTOR FROM Win32_ModuleLoadTrace WHERE Caption LIKE 'a%'" | Select-Object -Property TimeDateSTamp, DefaultBase, ImageBase, SECURITY_DESCRIPTOR
Accessing Remote Computers
To access remote systems, you need to have proper permissions. User the parameter -ComputerName to access one or more remote systems.
Authenticating as Current User
# one or more computer names or IP addresses:
$list = 'server1', 'server2'
# authenticate with your current identity:
$result = Get-CimInstance -ClassName Win32_ModuleLoadTrace -ComputerName $list
$result
Authenticating as Different User
Use a CIMSession object to authenticate with a new identity:
# one or more computer names or IP addresses:
$list = 'server1', 'server2'
# authenticate with a different identity:
$cred = Get-Credential -Message 'Authenticate to retrieve WMI information:'
$session = New-CimSession -ComputerName $list -Credential $cred
$result = Get-CimInstance Win32_ModuleLoadTrace -CimSession $session
# remove the session after use (if you do not plan to re-use it later)
Remove-CimSession -CimSession $session
$result
Learn more about accessing remote computers.
Requirements
To use Win32_ModuleLoadTrace, the following requirements apply:
PowerShell
Get-CimInstance
was introduced with PowerShell Version 3.0, which in turn was introduced on clients with Windows 8 and on servers with Windows Server 2012.
If necessary, update Windows PowerShell to Windows PowerShell 5.1, or install PowerShell 7 side-by-side.
Operating System
Win32_ModuleLoadTrace was introduced on clients with Windows Vista and on servers with Windows Server 2008.
Namespace
Win32_ModuleLoadTrace lives in the Namespace Root/CIMV2. This is the default namespace. There is no need to use the -Namespace parameter in Get-CimInstance
.
Implementation
Win32_ModuleLoadTrace is implemented in Krnlprov.dll and defined in Krnlprov.mof. Both files are located in the folder C:\Windows\system32\wbem
:
explorer $env:windir\system32\wbem
notepad $env:windir\system32\wbem\Krnlprov.mof