Windows 11 24H2 Upgrade. Apps doesn't work.

Anonymous
2025-02-05T09:26:49+00:00

Hi

We have started the testing phase of the Windows 11 24H2 Enterprise migration. In production, we are currently using Windows 10 22H2 Enterprise.

The deployment of Windows 11 via our software distribution tools is working smoothly. The jobs are executed without any issues, and the migration is successful.

Setting up new laptops also works without any problems.

However, after upgrading from Windows 10 to Windows 11, certain apps, such as Notepad, Snipping Tool, and Paint (possibly others as well), no longer work. Clicking on the apps does nothing.

It is important to mention that our company policy does not allow access to the Windows Store, as it is blocked via GPO.

As far as I understand, the apps are trying to update after the upgrade. However, since the Store is disabled, this does not work.

To test, we made the following changes in the GPO:

Enabled Windows Store: "Turn off the Store application" → Disabled

Only display the private store: "Only display the private store within the Microsoft Store" → Enabled

The good news: When setting up new laptops, it now works – after a certain time, the apps can be launched.

However, for upgrades from Windows 10 to Windows 11 (which is our main migration scenario), the issue persists.

Clicking on the apps does nothing – they do not start.

In the Event Log (AppxDeployment-Server), I see the following entry:

Event ID 486

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "Logging data because access was denied for file: \?\C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe\logo.png, user SID: S-1-5-18".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe\logo.png: owner is S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe\logo.png: user has access 0x1200A9".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe\logo.png: SDDL is O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:P(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1200a9;;;BA)(A;;0x1200a9;;;SY)(A;;0x1200a9;;;BU)(A;;0x1200a9;;;AC)(A;;0x1200a9;;;S-1-15-2-2)".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe: owner is S-1-5-32-544".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe: user has access 0x1F01FF".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe: SDDL is O:BAG:S-1-5-21-3080342968-2314478147-660929040-513D:AI(A;OICI;0x1200a9;;;AC)(A;OICI;0x1200a9;;;S-1-15-2-2)(A;OICI;0x1200a9;;;BU)(A;OICIID;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICIID;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIID;FA;;;SY)(A;CIID;0x1200a9;;;BA)(A;OICIID;0x1200a9;;;LS)(A;OICIID;0x1200a9;;;NS)(A;OICIID;0x1200a9;;;RC)".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps: owner is S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps: user has access 0x1F01FF".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files\WindowsApps: SDDL is O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:PAI(A;OICI;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICI;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICI;FA;;;SY)(A;CI;0x1200a9;;;BA)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;OICI;0x1200a9;;;RC)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files: owner is S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files: user has access 0x1301BF".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:\Program Files: SDDL is O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1301bf;;;SY)(A;OICIIO;GA;;;SY)(A;;0x1301bf;;;BA)(A;OICIIO;GA;;;BA)(A;;0x1200a9;;;BU)(A;OICIIO;GXGR;;;BU)(A;OICIIO;GA;;;CO)(A;;0x1200a9;;;AC)(A;OICIIO;GXGR;;;AC)(A;;0x1200a9;;;S-1-15-2-2)(A;OICIIO;GXGR;;;S-1-15-2-2)".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:: owner is S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:: user has access 0x1301BF".

Fehler beim AppX Deployment-Vorgang, Fehler "0x0" von API "C:: SDDL is O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1301bf;;;SY)(A;OICIIO;GA;;;SY)(A;;0x1301bf;;;BA)(A;OICIIO;GA;;;BA)(A;;0x1200a9;;;BU)(A;OICIIO;GXGR;;;BU)(A;OICIIO;GA;;;CO)(A;;0x1200a9;;;AC)(A;OICIIO;GXGR;;;AC)(A;;0x1200a9;;;S-1-15-2-2)(A;OICIIO;GXGR;;;S-1-15-2-2)".

Fehler beim Festlegen der Vertrauensstellungsbezeichnung für das Paket "Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe" mit Kennzeichen "0x102". Fehler: 0x80070005.

Even installing Microsoft.UI.Xaml.2.8.x64.appx does not resolve the issue: Invoke-WebRequest -Uri [removed_url] -OutFile $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx Add-AppxPackage $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx Where could the issue be? Has anyone experienced this before?

Many thanks for your help.

Cheers

***Move from Windows / Windows 11 / Install and upgrade***

Windows Windows Client for IT Pros Devices and deployment Set up upgrades and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-02-06T11:08:57+00:00

    Hello,

    Although you have tried to fix the problem by modifying the GPO settings, such as disabling ‘Turn off Store apps’ and enabling ‘Show only private shops in the Microsoft Store’, which solved the problem on newly installed systems, the problem still persists for This solved the problem on newly installed systems, but for upgraded systems, the problem still exists. Error code Event ID 486 in the event log and the error message indicate that the AppX deployment operation failed because file access was denied.

    There are several solutions you can consider for this issue:

    Permission adjustment: Ensure that all files in the C:\Program Files\WindowsApps directory and its subdirectories have the correct access permissions for the relevant user or service. It may be necessary to manually check and correct these permission settings.

    Offline installation of necessary app updates: Since it is not feasible to update apps directly through the Windows Store, try to find standalone installers for these apps and install them either manually or through a script after the migration is complete.

    Have a nice day.

    Best Regards,

    Hania

    0 comments No comments