If you launch a 32-bit instance of Powershell (%SystemRoot%\\syswow64\\WindowsPowerShell\\v1.0\\powershell.exe), then the registry provider only sees the limited 32-bit part
The REG.EXE command can write to 64-bit registries so the below should be safe for 32/64-bit from powershell.
®.EXE @('ADD','HKLM\YOURPATH\...','/v','KEY','/t','REG_DWORD','/d','12c','/f','/reg:64')
Seems quite a bit simpler and less error prone than the other solutions. This may have came out years after mind you.