Open with - Microsoft WinRT Storage API

Anonymous
2022-09-25T14:21:57+00:00

Hi,

Since my PC updated to Win 11 22H2 Pro, right-clicking on a JPG, one of the options is "Microsoft WinRT Storage API", clicking on this just brings up the error message "Element not found". I can find no way of removing this "open-with" item.

Just to clarify, I have seen posts referring to this where it has taken over as the Default app, this isn't the case here, all the files open in the correct default programs as they should. The problem is removing Microsoft WinRT Storage API altogether from the open-with menu.

Finally, I had the same issue with a laptop - rolling back and new Windows install [21H2 Home] corrected the problem - suggesting it isn't system specific.

Thanks.

Windows for home | Windows 11 | Windows update

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.

0 comments
Answer accepted by question author
Ramesh 181.9K Reputation points Volunteer Moderator
2022-09-27T08:31:39+00:00

Mike,

I'm wondering if this has something to do with Paint3D. The shell seems to be enumerating the program's registry location, and Paint3D's Package ID is wrongly assigned; it's pointing to the regular Paint app.

Please try these two commands from Admin PowerShell window:

  • get-appxpackage *paint* -allusers | remove-appxpackage
  • get-appxpackage Microsoft.Windows.Photos -allusers | remove-appxpackage

Install Paint 3D from Microsoft Store.

(Don't install the Photos app yet.)

See if the erroneous Open With entry is gone. Let's know how it goes.

Was this answer helpful?

30+ people found this answer helpful.
0 comments

54 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ramesh 181.9K Reputation points Volunteer Moderator
    2022-12-09T07:29:57+00:00

    Hi Mark,

    //But I don't know if doing this is a bad idea?//

    Glad you located the problematic ProgID. You can safely remove the value "AppXvsqkg1th80rv6s2rkh5m1hjp3hxryydd" from the OpenWithProgIDs key.

    //But maybe there is a better way of doing this!//

    You can try this command from PowerShell admin:

    • get-appxpackage *clipchamp* -allusers | remove-appxpackage

    And use DARF.vbs (optionally) to see if there are remnant entries related to Clipchamp.

    Edit:

    Fix: “Microsoft WinRT Storage API” Appears in Open With Menu

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Ramesh 181.9K Reputation points Volunteer Moderator
    2022-12-08T16:12:50+00:00

    Hi Mark,

    The fix suggested for the original poster (" Mike-V8" ) doesn't necessarily work for all users. "Microsoft WinRT Storage API" is a placeholder name shown when a package is corrupt. It could be any app. We can only narrow down the offending package's name after analyzing the trace log/registry locations.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-09-27T10:54:48+00:00

    Ramesh,

    A Picture is worth a thousand words!

    As of yet, I haven't associated JPG with an app/program. And as you said I haven't re-installed photos.

    Mike

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Ramesh 181.9K Reputation points Volunteer Moderator
    2022-09-25T16:59:24+00:00

    Thanks for the confirmation, Mike.

    As per DISM, it's the Photos app's ProgID that is currently the default. You may try uninstalling all instances of the Photos app using PowerShell and installing it from the Microsoft Store.

    From an admin PowerShell window, run:

    • get-appxpackage Microsoft.Windows.Photos -allusers | remove-appxpackage

    → Now, right-click on a JPG file and click Open With. Does the "WinRT" entry still exist?

    To reinstall the Photos app, open the Microsoft Store, search for "Microsoft Photos". Alternatively, you can go to the Photos app page via this URL:

    Let's know how it goes.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments