Execute PowerShell code in VB.NET

[robertx]

I am trying to execute PowerShell code to query the registry using System.Management.Automation. The following executes successfully in an elevated PowerShell window and returns the correct key count of 30 on my system:

$Keys = Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree'
$Keys.Count

However, when the same code is executed in VB.NET (as administrator), count is returned as only 1:

Imports System.Collections.ObjectModel
Imports System.Management.Automation

Dim script As String = "$Keys = Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree'
$Keys.Count"

Using powershell As PowerShell = PowerShell.Create()
    powershell.AddScript(script)
    Dim results As Collection(Of PSObject) = powershell.Invoke()

    For Each result As PSObject In results
        MessageBox.Show(result.ToString())
    Next
End Using

This issue seems to be isolated with this particular registry key as I haven't been able to replicate this behaviour with other HKEY_LOCAL_MACHINE registry keys.

[digitalShaman]

The difference could be a result of one running as 32bit process and the other as 64bit. Try compiling the .net app as 32bit.

[jdelano]

Might his be of any value? https://www.codeproject.com/Question...s-Using-VB-NET

[PlausiblyDamp]

I am trying to execute PowerShell code to query the registry using System.Management.Automation. The following executes successfully in an elevated PowerShell window and returns the correct key count of 30 on my system:

$Keys = Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree'
$Keys.Count

However, when the same code is executed in VB.NET (as administrator), count is returned as only 1:

Imports System.Collections.ObjectModel
Imports System.Management.Automation

Dim script As String = "$Keys = Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree'
$Keys.Count"

Using powershell As PowerShell = PowerShell.Create()
    powershell.AddScript(script)
    Dim results As Collection(Of PSObject) = powershell.Invoke()

    For Each result As PSObject In results
        MessageBox.Show(result.ToString())
    Next
End Using

This issue seems to be isolated with this particular registry key as I haven't been able to replicate this behaviour with other HKEY_LOCAL_MACHINE registry keys.

Quick question, is there a reason you are using powershell to do this from you app rather than just having your app query the registry directly?

[robertx]

The difference could be a result of one running as 32bit process and the other as 64bit. Try compiling the .net app as 32bit.

This was the issue. However, the .NET application was compiled as 32-bit. After compiling as 64-bit, the correct result is returned. I am wondering whether it is possible to run this code correctly as 64-bit within a 32-bit process.

[robertx]

Quick question, is there a reason you are using powershell to do this from you app rather than just having your app query the registry directly?

I was trying to execute a larger and more complex PowerShell script part of which was this registry interaction. The script was failing to execute correctly and I discovered that this was the problematic line of code.

[OptionBase1]

This was the issue. However, the .NET application was compiled as 32-bit. After compiling as 64-bit, the correct result is returned. I am wondering whether it is possible to run this code correctly as 64-bit within a 32-bit process.

The following StackOverflow article outlines a solution in C# which should be adaptable to VB.NET with little difficulty:

https://stackoverflow.com/questions/...it-application