Closed
Description
Description
When building a new image version in every windows version the AzureCosmosDbEmulator installation will fail because of a signature thumbprint mismatch. Please add the new and correct thumbprint.
Provisioning with powershell script: C:/a/1/s/runner-images/images/windows/templates/../scripts/build/Install-AzureCosmosDbEmulator.ps1
Downloading package from https://aka.ms/cosmosdb-emulator to D:\temp\bzd5vuan.msi...
Package downloaded in 12.06 seconds
Checksum verification failed: expected E2BEB2B242FEE3C1DD444C748C1ED1DC0120566ADC0A7BC612EB8EFB8D416089, got BFBA892C3B9E27093A6AA36CD3C447D812CA32D6A4361DB64E753A63C90C2766
At C:\Program Files\WindowsPowerShell\Modules\ImageHelpers\InstallHelpers.ps1:965 char:9
+ throw "Checksum verification failed: expected $expectedHash, ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Checksum verifi...E753A63C90C2766:String) [], RuntimeException
+ FullyQualifiedErrorId : Checksum verification failed: expected E2BEB2B242FEE3C1DD444C748C1ED1DC0120566ADC0A7BC612EB8EFB8D416089, got BFBA892C3B9E27093A6AA36CD3C447D812CA32D6A4361DB64E753A63C90C2766
Platforms affected
- Azure DevOps
- GitHub Actions - Standard Runners
- GitHub Actions - Larger Runners
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Image version and build link
.
Is it regression?
no
Expected behavior
Signature matches and installation continues.
Actual behavior
Signature mismatches and installation and image builds fail.
Repro steps
Step 1. Pull the main branch
Step 2. Build a image with the latest version of either a windows or linux os of your choice eg windows2022
Step 3. Failure will occur at the Install-AzureCosmosDbEmulator.ps1 installation step