Skip to content

MicrosoftPowerBIMgmt.Profile cannot be installed or updated due to Authenticode signature verification failure #344

Open
Open
MicrosoftPowerBIMgmt.Profile cannot be installed or updated due to Authenticode signature verification failure#344

Description

@SGarlapatiatma
Siva (SGarlapatiatma)
opened on Feb 19, 2026

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.

Steps to reproduce

Run the command
Set-PSRepository PSGallery -InstallationPolicy Trusted
Install-Module -Name MicrosoftPowerBIMgmt -Scope CurrentUser -Force

Expected behavior

Module installed successfully

Actual behavior

PackageManagement\Install-Package : The module 'MicrosoftPowerBIMgmt.Profile' cannot be installed or updated because
the authenticode signature of the file 'MicrosoftPowerBIMgmt.Profile.cat' is not valid.

Error details

PackageManagement\Install-Package : The module 'MicrosoftPowerBIMgmt.Profile' cannot be installed or updated because
the authenticode signature of the file 'MicrosoftPowerBIMgmt.Profile.cat' is not valid.

Environment data

Name                           Value
----                           -----
PSVersion                      5.1.17763.8385
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.8385
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Version

Latest Version

Visuals

Install-Module -Name MicrosoftPowerBIMgmt -Scope CurrentUser -Force
PackageManagement\Install-Package : The module 'MicrosoftPowerBIMgmt.Profile' cannot be installed or updated because
the authenticode signature of the file 'MicrosoftPowerBIMgmt.Profile.cat' is not valid.

Workaround:
Install-Module -Name MicrosoftPowerBIMgmt -Scope CurrentUser -Force -SkipPublisherCheck

Activity

  1. Bigdoingz100 commented on Feb 26, 2026

    @Bigdoingz100
    Bigdoingz100
    on Feb 26, 2026

    Set-PSRepository PSGallery -InstallationPolicy Trusted
    Install-Module -Name MicrosoftPowerBIMgmt -Scope CurrentUser -Force

  2. iolalimited commented on Mar 3, 2026

    @iolalimited
    Andy Walker (iolalimited)
    on Mar 3, 2026

    Is there likely to be a fix for this anytime soon do we think?

    I'm not happy skipping the publisher check because there is an unquantified risk with what has been uploaded.

    Even trying to force the previous version seems fraught with gotcha's.

    Is this officially raised as an issue with Microsoft?

  3. adityapatwardhan commented on Mar 3, 2026

    @adityapatwardhan
    Aditya Patwardhan (adityapatwardhan)
    on Mar 3, 2026
    Member

    Siva (@SGarlapatiatma) - can you please provide us with the version of the modules: PackageManagement and PowerShellGet.

    Get-Module -ListAvailable "PackageManagement", "PowerShellGet"

  4. SGarlapatiatma commented on Mar 3, 2026

    @SGarlapatiatma
    Siva (SGarlapatiatma)
    on Mar 3, 2026
    Author

    @SGarlapatiatma - can you please provide us with the version of the modules: PackageManagement and PowerShellGet.

    Get-Module -ListAvailable "PackageManagement", "PowerShellGet"

    ModuleType Version Name ExportedCommands

    Binary 1.0.0.1 PackageManagement {Find-Package, Get-Package, Get-PackageProvider, Get-Packa...
    Script 1.0.0.1 PowerShellGet {Install-Module, Find-Module, Save-Module, Update-Module...}

  5. alerickson commented on Mar 3, 2026

    @alerickson
    alerickson
    on Mar 3, 2026
    Member

    Siva (@SGarlapatiatma) Andy Walker (@iolalimited) Please update PowerShellGet and PackageManagement to the latest stable version: https://www.powershellgallery.com/packages/PowerShellGet/2.2.5 https://www.powershellgallery.com/packages/PackageManagement/1.4.8.1.

    If you have any issues with bootstrapping the NuGet provider please see: https://learn.microsoft.com/en-us/powershell/gallery/how-to/getting-support/bootstrapping-nuget?view=powershellget-2.x

    If possible. it's better to switch to PSResourceGet, which is the module we're actively developing to completely replace PowerShellGet: https://www.powershellgallery.com/packages/Microsoft.PowerShell.PSResourceGet/1.2.0-rc3

  6. iolalimited commented on Mar 4, 2026

    @iolalimited
    Andy Walker (iolalimited)
    on Mar 4, 2026

    alerickson Sorry, I don't quite follow.

    I'm using a hosted Windows Agent to install PS Modules and deploy PBI reports to a workspace. The PS that is failing is:-
    Install-Module -Name MicrosoftPowerBIMgmt -Verbose -Scope CurrentUser -Force -AllowClobber

    The agent is Windows 2025:-
    2026-02-27T14:27:46.5044097Z Microsoft Windows Server 2025
    2026-02-27T14:27:46.5044239Z 10.0.26100

    The PS Version is 2.268.1:-
    2026-02-27T14:27:55.9739375Z Task : PowerShell
    2026-02-27T14:27:55.9739443Z Description : Run a PowerShell script on Linux, macOS, or Windows
    2026-02-27T14:27:55.9739532Z Version : 2.268.1

    But the Install-Module is throwing an authenticode signature error:-
    2026-02-27T14:28:11.0418918Z PackageManagement\Install-Package : The module 'MicrosoftPowerBIMgmt.Profile' cannot be installed or updated because
    2026-02-27T14:28:11.0419603Z the authenticode signature of the file 'MicrosoftPowerBIMgmt.Profile.cat' is not valid.
    2026-02-27T14:28:11.0420550Z At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1:9711 char:34
    2026-02-27T14:28:11.0420986Z + ... talledPackages = PackageManagement\Install-Package @PSBoundParameters
    2026-02-27T14:28:11.0421331Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2026-02-27T14:28:11.0423106Z + CategoryInfo : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package],
    2026-02-27T14:28:11.0424269Z Exception
    2026-02-27T14:28:11.0425628Z + FullyQualifiedErrorId : InvalidAuthenticodeSignature,ValidateAndGet-AuthenticodeSignature,Microsoft.PowerShell.P
    2026-02-27T14:28:11.0426377Z ackageManagement.Cmdlets.InstallPackage

    Many thanks,
    Andy

  7. iolalimited commented on Mar 4, 2026

    @iolalimited
    Andy Walker (iolalimited)
    on Mar 4, 2026

    I see 1.3.80 has been released and this has solved the issue. Many thanks,

    Andy

  8. Sujai-Sparks commented on Mar 4, 2026

    @Sujai-Sparks
    Sujai-Sparks
    on Mar 4, 2026

    Hi, unfortunately, after using the "-SkipPublisherCheck", I see the new MicrosoftPowerBIMgmt version 1.3.80 is getting installed, but the Connect-PowerBIServiceAccount cmdlet is failing to login to PowerBI service :(

    Any help please?

    I'm getting the following error:
    2026-03-04T07:52:30.7855907Z Connect-PowerBIServiceAccount : One or more errors occurred.
    2026-03-04T07:52:30.7856530Z At C:\a\r2\a_Package OI Reports_Feature\drop\DeployReports\publishpowerbi.ps1:1365 char:1
    2026-03-04T07:52:30.7857005Z + Connect-PowerBIServiceAccount -Credential $credential
    2026-03-04T07:52:30.7857584Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2026-03-04T07:52:30.7858160Z + CategoryInfo : WriteError: (Microsoft.Power...IServiceAccount:ConnectPowerBIServiceAccount) [Connect-Po
    2026-03-04T07:52:30.7858639Z werBIServiceAccount], AggregateException
    2026-03-04T07:52:30.7859338Z + FullyQualifiedErrorId : One or more errors occurred.,Microsoft.PowerBI.Commands.Profile.ConnectPowerBIServiceAcc
    2026-03-04T07:52:30.7859770Z ount
    2026-03-04T07:52:30.7860146Z
    2026-03-04T07:52:30.7907056Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.4420.0 Microsoft Windows 10.0.17763 [2026-03-04
    2026-03-04T07:52:30.7907573Z 07:52:30Z] [MSAL:0001] WARNING SetAuthorityUri:78 Initializing authority from URI
    2026-03-04T07:52:30.7908062Z 'https://login.microsoftonline.com/organizations/' without authority type, defaulting to MsSts
    2026-03-04T07:52:30.7926981Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.4420.0 Microsoft Windows 10.0.17763 [2026-03-04
    2026-03-04T07:52:30.7927795Z 07:52:30Z] [MSAL:0001] WARNING TryEnqueueMsaDeviceCredentialAcquisitionAndContinue:1052 MsaDeviceOperationProvider is
    2026-03-04T07:52:30.7928470Z not available. Not attempting to register the device.
    2026-03-04T07:52:30.7947983Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.4420.0 Microsoft Windows 10.0.17763 [2026-03-04
    2026-03-04T07:52:30.7948585Z 07:52:30Z] [MSAL:0002] ERROR ErrorInternalImpl:134 Created an error: 7q6ch, StatusInternal::Unexpected,
    2026-03-04T07:52:30.7949069Z InternalEvent::None, Error Code -2147023584, Context '(pii)'
    2026-03-04T07:52:30.8037199Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.4420.0 Microsoft Windows 10.0.17763 [2026-03-04 07:52:30Z
    2026-03-04T07:52:30.8037768Z - 07d1b3e2-b37f-4eb7-9766-8a5ae3841eef] Exception type: Microsoft.Identity.Client.MsalServiceException
    2026-03-04T07:52:30.8038292Z
    2026-03-04T07:52:30.8038631Z , ErrorCode: unknown_broker_error
    2026-03-04T07:52:30.8038752Z
    2026-03-04T07:52:30.8039005Z HTTP StatusCode 0
    2026-03-04T07:52:30.8039196Z
    2026-03-04T07:52:30.8039490Z CorrelationId 07d1b3e2-b37f-4eb7-9766-8a5ae3841eef
    2026-03-04T07:52:30.8039622Z
    2026-03-04T07:52:30.8039935Z To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging

    Note: I'm using Azure DevOps pipelines to run the powershell script. The deploy agent machine has the stable versions of PowerShellGet (2.2.5) and PackageManagement (1.4.8.1)

  9. iolalimited commented on Mar 4, 2026

    @iolalimited
    Andy Walker (iolalimited)
    on Mar 4, 2026

    ...Something still not quite right here.

    2026-03-04T08:00:22.9945512Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.9310.0 Microsoft Windows 10.0.26100 [2026-03-04
    2026-03-04T08:00:23.0002821Z 08:00:20Z] [MSAL:0001] WARNING SetAuthorityUri:78 Initializing authority from URI
    2026-03-04T08:00:23.0078606Z 'https://login.microsoftonline.com/organizations/' without authority type, defaulting to MsSts
    2026-03-04T08:00:23.0083199Z WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.9310.0 Microsoft Windows 10.0.26100 [2026-03-04
    2026-03-04T08:00:23.0090767Z 08:00:20Z] [MSAL:0001] WARNING TryEnqueueMsaDeviceCredentialAcquisitionAndContinue:1052 MsaDeviceOperationProvider is
    2026-03-04T08:00:23.0091426Z not available. Not attempting to register the device.

  10. zzuqdah commented on Mar 19, 2026

    @zzuqdah
    zzuqdah
    on Mar 19, 2026

    Has MSFT ack'ed this issue? Is there any ETA on a resolution?

  11. zzuqdah commented on Apr 10, 2026

    @zzuqdah
    zzuqdah
    on Apr 10, 2026

    I found the workaround below:

    - task: PowerShell@2 displayName: 'Install PowerBIMgmt via PSResourceGet' inputs: targetType: 'inline' pwsh: true script: | $ErrorActionPreference = 'Stop' [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Install-PSResource -Name MicrosoftPowerBIMgmt -Version '1.3.83' -Scope CurrentUser -TrustRepository -Repository PSGallery Import-Module MicrosoftPowerBIMgmt -Force Get-Module MicrosoftPowerBIMgmt* -ListAvailable | Format-Table Name, Version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions