Microsoft Store updates odd since CU KB5058411

bikemanAMD said:

Well Mine somehow solved with my clean install

But i didn't use Media Creation tool

I downloaded Rufus, setup my ISO with that as i prefer a Local account first, then add my MS Account later in the install procedure

Then once i have the accounts all set, then i do all the updates, and then install rest of the software, and any other updates

So far my Windows store is working exactly normal

Anyways
Do hope you get your issues solved fully at some point as well

Click to expand...

Never used Rufus, so has no idea I could install Windows in a different way.

At any rate. I think this is MS’s issue to solve as I followed all of the standard procedures for a clean install as per MS’s guidance.

Annoying, but not critical.

I have auto update MS Store updates turned off. I wonder if they would update if auto update apps in enabled rather than a manual check? I know that many apps are updated in the background particularly the "Runtime" ones. Last week when I had a problem updating the apps I saw that other apps were installed in the background and perhaps were clashing will the manual updates. Just a theory. Mitch.

Mitch said:

I have auto update MS Store updates turned off. I wonder if they would update if auto update apps in enabled rather than a manual check? I know that many apps are updated in the background particularly the "Runtime" ones. Last week when I had a problem updating the apps I saw that other apps were installed in the background and perhaps were clashing will the manual updates. Just a theory. Mitch.

Click to expand...

Background updates by WU, and manual updates from the Store are both handled by the same internal process. It doesn't matter which one triggers the update, and they don't interfere with each other.

Having this same issue on a clean install of Windows 11 Pro 24H2.

Have you guys managed to find a solution to it?

It doesn't seem like it effects anything, but who knows.

Hey small update on this. I was doing some digging in process explorer and the registry. So It's clearly some form of issue with the AppXDeplymentServer. This is a dll that is loaded by the svchost AppXSvc. Funnily enough I checked system32 for that dll and found it and a windows event log file called Microsoft-Windows-AppXDeploymentServer%4Operational.evtx.

Opening this up you get more detail on what AppXDeployment has been doing when updating. So it seems like the way AppXSvc works when updating apps is that it will shutdown the app, remove the installation folder and recreate it with the updated files. It seems like right after it completes the 'Deployment remove operation'.

For example for updating Crossdevice it will log the above and then it logs another event stating Windows cannot remove MicrosoftWindows.CrossDevice_(versionnumber) because the current user does that have package installed.

This is where I believe the normal event viewer logs that 2562 event. I'm not 100% of this it could be further up in the log where it moves the entire folder into deleted apps for some reason(??? Cleanup who knows)

Anyway this points towards a bug with AppXDeploymentServer.dll or the Microsoft store. I don't think it's corruption or DISM and SFC would probably catch it and fix it. Also I would think if it the file was corrupted it would break the signature on it and get picked up by sigcheck, but again, who knows.

In summary, Windows 11 24H2 gives me a headache.

@Webweaver my findings are the same as yours.

I do not think this is a major issue and is most likely cosmetic in nature.

I did a completely clean install of windows 11 24h2 when trying to fix this issue. Initially, the problem was gone, however, as soon as Windows update installed the latest CUs and MS Store updates, the event message reappeared. SFC and DISM always comeback clean.

I reckon a lot of people get this event log, but they don’t check event viewer so wouldn’t know.

Arrrggg I check early this morning for updates from the 'Store' and instantly got the dreaded 'Que' message.

TheVisitor said:

Arrrggg I check early this morning for updates from the 'Store' and instantly got the dreaded 'Que' message.

Click to expand...

That’s annoying.

Thing is, I don’t use apps from the MS store and I have auto updates turned off for the store. Occasionally WU update forces an update through, usually for the store itself or something else system related and I get the error message in event viewer.

I really don’t think this is a thing we can fix and I don’t think it’s anything to worry about. Been running for a couple of months at least with this issue and no system instability to report.

I’d be inclined to ignore it and wait for MS to fix it (if they ever do).

24H2 has been a complete mess IMO. What a crap update.

This is still happening even on 25H2

MetalAlchemist said:

This is still happening even on 25H2

Click to expand...

Yes it is. I don't think it actually means anything though.