Internal Error: Get-RegistryMRU use the wrong data type for numbers about meerkat

[kmahyyg]

Also, Get-MAC stucked for so long, at least about 5mins, The wsmprovhost.exe eats about 1GiB memory when executing. After checking src, I think it should not be run by default when running Invoke-Meerkat.

[TonyPhipps]

Would you mind sharing the command used to execute?

[TonyPhipps]

The underlying command for get-mac is fairly straightforward:

$Path = "$ENV:SystemDrive\Users"
Get-ChildItem -Path $Path -File -Recurse

If this command takes a long time on the same system, it explains why the Get-MAC module take a long time. Note the hash option takes significantly longer, which is unavoidable if needed.

[TonyPhipps]

The original error with Get-RegistryMRU will be difficult to reproduce, and does not occur on any system I've encountered. It's possible a try statement on line 163 inside the foreach-object may fix the issue, but I'd rather not troubleshoot blindly.

line 163

$asciiArray = $hexArray | ForEach-Object { [CHAR][BYTE]([CONVERT]::toint32($_,16)) }

[kmahyyg]

Would you mind sharing the command used to execute?

Just load the psm file and run Invoke-Meerkat

[kmahyyg]

The original error with Get-RegistryMRU will be difficult to reproduce, and does not occur on any system I've encountered. It's possible a try statement on line 163 inside the foreach-object may fix the issue, but I'd rather not troubleshoot blindly.

line 163

$asciiArray = $hexArray | ForEach-Object { [CHAR][BYTE]([CONVERT]::toint32($_,16)) }

I run the original version on my personal PC, since I've no idea with powershell itself, may I send you the related registry file exported from my PC? Will it be helpful for diagnostics?