KB5134305 / MIM 4.7.13.0 – Strong Name Validation Failure in miisclient.exe and Service/Portal installer

Title: MIM SP3 KB5134305 – Strong name validation errors after upgrading to 4.7.13.0

Hi,

I recently tried upgrading MIM 2016 SP3 from 4.7.6.0 to 4.7.13.0 (KB5134305) in our development environment, but ran into a couple of issues.

Both servers are running Windows Server 2022.

The MIM Synchronization Service update completed successfully, but miisclient.exe now crashes whenever I try to use it.

Event Viewer shows:

Faulting application: miisclient.exe
Version: 4.7.13.0
Faulting module: KERNELBASE.dll
Exception code: 0xe0434352

I also checked the crash dump and found:

System.IO.FileLoadException:
Could not load file or assembly 'miisclient, Version=4.7.0.0'
Strong name validation failed.
HRESULT: 0x8013141A

The synchronization service itself is still running.

I tested the strong-name signatures using StrongNameSignatureVerificationEx and got these results:

miisclient.exe 4.7.13.0: False / False
miisclient.exe 4.7.6.0:  True / True
mscorlib.dll:            True / True

The 4.7.6.0 comparison was done on a separate MIM environment.

I also tried installing the Service and Portal hotfix, but that installation fails with error 1603.

The installation log shows:

GetIISVersionFromRegistry

Could not load file or assembly
'Microsoft.IdentityManagement.PasswordResetCAs,
Version=4.7.0.0'

Strong name validation failed.
HRESULT: 0x8013141A

I checked the MSP file, and its size matches Microsoft's published file size. The digital signature is also valid and signed by Microsoft.

The Service and Portal installation rolled back to 4.7.6.0 and is still working.

Since both components are failing with strong-name validation errors, I'm wondering if there could be an issue with the assemblies included in KB5134305.

Has anyone else tried installing this hotfix and encountered similar problems?

Is this a known issue, or is there anything else I should check?