Upgrade Windows 11 Pro 23H2 to a currently supported release before reinstalling Photos, because 23H2 Pro stopped receiving updates on November 11, 2025 and is not a supported baseline for diagnosing a new Photos package in October 2026.^1^
1. Upgrade Windows, then install Photos
- Back up important files.
- Open Settings > Windows Update.
- Select Check for updates.
- If a supported Windows 11 feature update is offered, select Download and install. Microsoft’s 23H2 release-health page directs eligible devices to upgrade this way.^2^
- Restart when prompted and run Windows Update again until no further updates are offered.
- Open Microsoft Store > Library > Get updates, then install Microsoft Photos.
Do not target 24H2 merely as an intermediate destination: Windows 11 Home and Pro 24H2 also reached end of servicing on October 13, 2026.^3^
The available information does not establish that Photos 2608.1401.18.0 has a confirmed regression. Error 0x80073CF6 specifically means that the package could not be registered; the inner reference to windows.fileTypeAssociation.progIdGeneration identifies the registration stage that failed, but does not by itself prove whether the package or the older OS caused it.^4^
2. If Windows Update does not offer a supported release
Use current Windows installation media for an in-place upgrade, not a clean installation:
- Create Windows installation media.
- While signed in to Windows, connect or mount the media.
- Open its drive in File Explorer and run
setup.exe. - Select Change what to keep.
- Select Keep personal files and apps.
- Complete the installation, then retry Photos from Microsoft Store.
This option preserves personal data, installed applications, and settings.^5^
3. If Photos still fails on the supported Windows release
Since Store reset, DISM/SFC, removal, restart, and WinGet have already failed, do not repeat them. Capture the deployment event that immediately accompanies a fresh Store installation attempt.
Open PowerShell as administrator, attempt the Photos installation once, and then run:
Get-AppxLog |
Where-Object {
$_.LevelDisplayName -in 'Error','Critical' -or
$_.EventId -eq 404
} |
Select-Object -Last 30 TimeCreated, EventId, Message |
Format-List
Also inspect:
Event Viewer > Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational
Match Error, Critical, or Warning events to the exact installation time. These records should expose the package name, extension, and more specific inner failure hidden behind 0x80073CF6.^6^
If the same windows.fileTypeAssociation.progIdGeneration / 0x80004001 failure remains after upgrading, submit the following through Get Help or Microsoft Support:
- Windows edition, version, and build after the upgrade
- Photos package version
- Full AppXDeployment-Server event text
-
Get-AppxLogoutput - Exact installation timestamp
- Confirmation that other Store apps install normally
That evidence is needed to distinguish a Photos manifest/package regression from a device-specific AppX registration problem.
4. Last nondestructive repair option
If package registration fails for Photos even on a supported release and the logs indicate damaged Windows deployment state, reinstall the current Windows version while preserving files, apps, and settings. Microsoft identifies reinstalling using Windows Update as the least disruptive reinstallation option; installation media with Keep personal files and apps is the alternative.^7^
Avoid a clean installation unless the nondestructive methods fail, because a clean install removes personal files, applications, settings, and manufacturer customizations.
References
- Windows 11, version 23H2 reaching end of updates (Home, Pro)
- Windows 11, version 23H2 known issues and notifications
- Ending Support in 2026
- Troubleshooting packaging, deployment, and query of Windows apps
- Reinstall Windows with the installation media | Microsoft Support
- MSIX deployment troubleshooting
- Recovery options in Windows | Microsoft Support