64-bit PowerShell cmdlets
I use PowerShell for many products from Microsoft and other vendors. Of them all, the SCCM cmdlets are the only ones that are available only in 32-bit. So I have to open a separate PowerShell instance when I want to run SCCM commands. Or sometimes I am writing a script that runs 64-bit commands for other products, then I must have the script open a special 32-bit Powershell instance for the SCCM commands.
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
Every cmdlet should support either a 32 or 64-bit PowerShell session.
I recall this being fixed post-R2, so if you're running the latest version of the Cmdlet Library (if pre-1606) or are running 1606 or greater, there should be no behavioral differences between 32 and 64-bit sessions.
If you are seeing any such problems and you're up to date (that is to say you're using the 1604 release of the Cmdlet Library if you're pre-1606, or are already 1606 or newer), then please file a bug on Connect providing more information so we can investigate.