Hello Brown SOLIVER,
Identical PowerShell commands can return different results because a 32-bit PowerShell process and a 64-bit PowerShell process do not see the same view of the operating system on a 64-bit Windows installation. The most common cause is WOW64 redirection, where a 32-bit PowerShell session is transparently redirected from %windir%\System32 to %windir%\SysWOW64, causing the command to access different binaries, DLLs, and tools than a 64-bit session.
Registry access is another major factor. Microsoft documents that 32-bit and 64-bit applications use separate logical registry views, and a 32-bit PowerShell session is often redirected to keys under HKLM\SOFTWARE\Wow6432Node, while a 64-bit session reads the native 64-bit registry view. As a result, the same command may discover different installed applications, registry values, COM registrations, or configuration settings.
You should also verify module and provider architecture compatibility, because some PowerShell modules, WMI providers, COM objects, and .NET assemblies are installed only for one architecture. A command that succeeds in a 64-bit session may return incomplete data or fail entirely in a 32-bit session due to missing architecture-specific dependencies.
When troubleshooting, first confirm the process architecture using $env:PROCESSOR_ARCHITECTURE and ensure that both sessions are reading the same file paths and registry view. In enterprise environments, I generally recommend running the native 64-bit PowerShell host whenever possible to avoid WOW64 redirection and registry virtualization inconsistencies.
If my answer is useful for you, please hit Accept the answer for me please.
HL.