Latest CU Error? "This file is not a valid Appx package because it is missing a manifest or block map"

S

scaramonga

Active Member
Messages
146
Reaction score
42
Latest update (8973) brings this error on LTSC 24. Same integration as always with prior versions? Image creates OK, but?

First time had this. On latest 11258 NTLite.

Probably MS fucking around again?
 

Attachments

  • Annotation 2026-07-31 034826.png
    Annotation 2026-07-31 034826.png
    120.7 KB
  • 8894.xml
    8894.xml
    29.6 KB
With Windows 11 Pro, I had no problem integrating this update (Preview) and these Appx
But I haven't tried it from ISO 26100.8973
 
I had the host with the July CU when I integrated the updates.
Now I have the Preview host (26200.8973)
 
Yup, latest CU causes these 2 files to fail. Prior CU does not: ???
 

Attachments

  • Annotation 2026-08-01 102546.png
    Annotation 2026-08-01 102546.png
    117.6 KB
  • Annotation 2026-08-01 101147.png
    Annotation 2026-08-01 101147.png
    120.1 KB
scaramonga said:
The same system I create all my images on, Windows 10 22H2 19405-5555, lol.
Click to expand...

That's explains it

this is a backported bug behavior from Canary build 29634
you can't add apps together in a single dism session, if the host OS is pre 26100

something changed in AppXAllUserStore.dll cause it to be compatible only with host OS 26100 or later
in your case, CU is added before apps, hence the image AppXAllUserStore.dll is updated, hence the error occurs

ir's not dism error itself
 
abbodi86 said:
That's explains it

you can't add apps together in a single dism session, if the host OS is pre 26100
Click to expand...
Well, that's nonsense, as my above images prove otherwise. The only fault is with latest CU update, as on my 'pre 26100 host', every other CU update works just fine? :) (unless something has changed suddenly in this update?, then it would be a first)

SSU 8872 - 8962 difference here, so, little has changed, and less than 2 weeks between them? 8872 works, 8962 (latest) don't, and unless MS has changed something?, it explains nothing. ;)
 
Last edited:
Because the latest CU update AppXAllUserStore.dll inside the image (install.wim), which is used by the servicing stack to add appx/msix

you can check youself
use NTLite on 26100+ host OS, and the error will not occur even with latest CU
 
So, let's get this straight.

I can no longer continue creating images on my 'pre 26100' system?, as MS have changed the rules again, thus 'forcing' me to update to the 'rot' before I try and make an image that is less rotten?
 
more or less
until they fix the bug (if it's not intentional change)

for now, you can use NTLite to integrate apps alone first, then integrate updates in new session
 
abbodi86 said:
That's explains it

this is a backported bug behavior from Canary build 29634
you can't add apps together in a single dism session, if the host OS is pre 26100

something changed in AppXAllUserStore.dll cause it to be compatible only with host OS 26100 or later
in your case, CU is added before apps, hence the image AppXAllUserStore.dll is updated, hence the error occurs

ir's not dism error itself
Click to expand...
So, it's not the same problem as the DismHost.exe error ?
With the host 26200.8973
 
abbodi86 said:
You get 0x80080203 error? or different?
Click to expand...
It's 0xc0000005

With this error :
Code: 
DISM Provider Store: PID=1876 TID=2300 Failed to get the provider MsuManager from the remote provider store. - CProxyProviderStore::GetProvider(hr:0x80070032)

And this warning for example :
Code: 
CBS Current tick count: 915 lower than last tick count: 934. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Perhaps the same problem as with a CU a few months ago.
The problem also appears when canceling the NTLite process, for example (after encountering the error when integrating Appx from a 26100.1 image)
 
Last edited:
You must log in or register to reply here.
Back
Top