Powershell 7 x86 and x64

[Matt.Wreede]

Hello,

For Powershell 7, we install both x86 and x64 on Windows 11 x64.

The expectation then, is to be able to patch both revisions with PatchMyPC.

Currently, it looks like the Powershell Core Latest is keyed to both x64 and x86. x64 detects the 64 bit MSI install correctly, and patches it.

x86 does not; it does not see the x86 install of Powershell 7 on a our 64 bit fleet.

Is this expected, or is it something that could be 'fixed'? The goal would be: See x86 Powershell 7 'older', and update to 'latest' (7.5.0 as of 2025-01-29).

Thanks!

[Michael (Patch My PC)]

I'll give this a test, but you should be able to patch both.

You will need to ensure you have deployments for both the x64 and x86 assigned to the device.

[Matt.Wreede]

For us, the:

PowerShell Core 7.5.0 (x64)   PMPC-2025-01-23   17331   117   1   Yes   Yes   1/23/2025 10:05:00 AM   

Shows as being 'required' on 'everything' basically, since it just came out.

While:

PowerShell Core 7.5.0 (x86)   PMPC-2025-01-23   0   0   44   Yes   Yes   1/23/2025 10:07:00 AM

Is showing (0). Which makes me think(?) the metadata associated might be 'limited' to x86 devices; we have zero x86 devices.   

[Michael (Patch My PC)]

I just tested this and it updated both the x86 and the x64 version.

I installed the 7.4.4 x86 and x64 on the machine. And both 7.5.0 x86 and x64 updates ran on the devices.

I would suggest submitting a support ticket and we'll see what is going on.
Technical Support: Open a Support Case - Patch My PC

Sending the output of this script can help us as well to see what the registry looks like on the device as well in regards to the installed applications.
CustomerTroubleshooting/PowerShell/Export-PMPCInstalledSoftware.ps1 at Release · PatchMyPCTeam/CustomerTroubleshooting

Be sure to grab any rolled over logs with the 'dates' in the name as well, example: [ IntuneManagementExtension-20240801-055755.log ]

• %ProgramData%\PatchMyPC\*
  
  • This folder contains User based installation logs as well as notification settings
• %ProgramData%\PatchMyPCInstallLogs\*
  
  • This will contain logs from individual application installers
• %ProgramData%\PatchMyPCIntuneLogs\*
  
  • PatchMyPC-CustomSoftwareDetectionScript*.log
  • PatchMyPC-CustomSoftwareUpdateDetectionScript*.log
  • PatchMyPC-ScriptRunner*.log
    
    • This may be found in [%ProgramData%\PatchMyPC\] if the Install was initiated by the user from Company Portal.
  • PatchMyPC-SoftwareDetectionScript*.log
  • PatchMyPC-SoftwareUpdateDetectionScript*.log
• %ProgramData%\Microsoft\IntuneManagementExtension\Logs\*
  
  • AgentExecutor*.log
  • AppActionProcessor*.log
  • AppWorkload*.log
  • IntuneManagementExtension*.log
  • Win32AppInventory*.log

[Matt.Wreede]

Perfect! We're in a PoC right now, so I'll let the Engineer know as well, but I want to get a good understanding of your process. Great response time on the forum, if nothing else I'll get a case in.

[Andrew Jimenez (Patch My PC)]

Hi Matt,

Andrew from the catalog team here. Just to confirm, are you using the WSUS patches for this app? We just found that we had a prereq on the 32-bit version of our PowerShell WSUS update that would only allow it to install on 32-bit OSes. We're working on fixing the WSUS rules for this update now, and hope to have a fix automatically rolled out sometime this week.

[Matt.Wreede]

Hi Matt,

Andrew from the catalog team here. Just to confirm, are you using the WSUS patches for this app? We just found that we had a prereq on the 32-bit version of our PowerShell WSUS update that would only allow it to install on 32-bit OSes. We're working on fixing the WSUS rules for this update now, and hope to have a fix automatically rolled out sometime this week.

Correct! WSUS/ConfigMgr. I received the email from the case too, so that's perfect.

[Andrew Jimenez (Patch My PC)]

This is now resolved in our latest catalog release.