PENDING APPX Installation detection methode

[mcdy]

Hey folks,

am I right, that it isn't possible to change the detection methode of an APPX package?
The problem is the app updates itself, which is fine, but now the detection methode won't success anymore and my log is full of this.
Also it's shown in Software Center.

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_f68ebf27-75ac-417d-a240-8e7cd89dde1a" AND Revision = 1)"    AppDiscovery    11.03.2022 16:23:11    15908 (0x3E24)
    Performing detection of app deployment type Drawboard PDF - Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)(ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_f68ebf27-75ac-417d-a240-8e7cd89dde1a, revision 1) for user.    AppDiscovery    11.03.2022 16:23:11    15908 (0x3E24)
    In-line script returned error output: & : Fehler bei der AuthorizationManager-šberprfung.
In Zeile:1 Zeichen:3
+ & 'C:\WINDOWS\CCM\SignedScripts\DetectWindows8AppBundle.ps1' -AppName ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : Sicherheitsfehler: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
    AppDiscovery    11.03.2022 16:23:11    15908 (0x3E24)
+++ Did not detect app deployment type Drawboard PDF - Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)(ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_f68ebf27-75ac-417d-a240-8e7cd89dde1a, revision 1) for S-1-5-21-13620034-1472260336-3426108985-1335.    AppDiscovery    11.03.2022 16:23:11    15908 (0x3E24)

The only option is a PowerShell based installation with my own detection methode - isn't it?

THX mcdy

 

[mcdy]

Hello,

any help is greatly appreciated.

Thanks!
mcdy

 

[mcdy]

Nobody?
Am I the only one who had to install Window Store programs using SCCM?
Normally everyone should have this problem.

Thanks!
mcdy

 

[Pollewops]

Yes I do have the same issues...did you already manage to get around this. I see only the method using a powershell script with an own creted detection method.

 

[martin.dufresne]

Same problem here ! something is missing for sure...