When I updated the ProcNModules script a few weeks ago, I didn't notice any errors it was producing. However, I've run the script on win 7 hosts recently and I've started to get feedback for certain DLLs not being found (screenshot below):
Research into this led to me to find that some of these cmdlet calls are the problem:
I'll update this module accordingly, but I wonder if this may exist throughout the code base if Get-Item or Get-ChildItem are used and try to collect data from hidden and/or system files. Can you flag it as a bug and assign it to me to resolve?
When I updated the ProcNModules script a few weeks ago, I didn't notice any errors it was producing. However, I've run the script on win 7 hosts recently and I've started to get feedback for certain DLLs not being found (screenshot below):
Research into this led to me to find that some of these cmdlet calls are the problem:
Specifically
Get-Item
andGet-ChildItem
will not access hidden (and system forGet-ChildItem
) files, even with an administrative PS session. The fix is to specify the -Force parameter. https://technet.microsoft.com/en-us/library/hh849788.aspx https://technet.microsoft.com/en-us/library/hh849800.aspxI'll update this module accordingly, but I wonder if this may exist throughout the code base if Get-Item or Get-ChildItem are used and try to collect data from hidden and/or system files. Can you flag it as a bug and assign it to me to resolve?