Hi Lashon Cortez,
The behavior you’re seeing, where file associations revert to “Microsoft WinRT Storage API” or Windows Photo Viewer and produce the “Invalid value for registry” error, is typically tied to corruption in the per‑user app registration state. Even after repairing or resetting the Photos app, the registry hash protecting file associations can remain invalid, which causes Windows to fall back to legacy handlers.
The best supported way to repair this is to fully re‑register the Photos app for the affected users. You can do this by running PowerShell as administrator and executing: Get-AppxPackage *Microsoft.Windows.Photos* | Reset-AppxPackage This clears the corrupted registration and rebuilds the association state. If the issue persists, you may also export and re‑import default app associations using Dism /Online /Export-DefaultAppAssociations:assoc.xml and Dism /Online /Import-DefaultAppAssociations:assoc.xml, applied only to the impacted profiles.
For deeper investigation, I recommend checking Event Viewer > Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server and AppModel-Runtime, as these will record any failures when defaults are reset. If you see repeated errors tied to Photos, that confirms the app package is failing validation for those users.
I hope this guidance helps you stabilize file associations for the affected accounts. If this explanation is useful, please hit “Accept Answer” so I know your concern is resolved. 😊
Jason.