How can I automate scanning all DLLs in the Windows directory for export functions like MiniDumpW?

A PowerShell script can recursively traverse `C:\Windows`, obtain each DLL's absolute path, and use a function like `Get-Exports` (from the PowerShell-Suite) to list export function names. The article provides a script that filters for `MiniDumpW` and other exports. It handles the path format issue by stripping the `Microsoft.PowerShell.Core\FileSystem::` prefix. The complete script is shared on GitHub. This technique is useful for discovering alternative DLLs for lateral movement or privilege escalation.