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-09-27T11:05:59+00:00

    Thanks Mike. Please try installing Photos.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2022-09-26T17:58:17+00:00

    Hi Ramesh,

    First time I've used ProcMon, hopefully it went OK.

    Here is the link to the Log: https://1drv.ms/u/s!ApcmPXxreWpehNk5O-5tkWJiQcZMYw?e=Ef2fyv

    Regards

    Was this answer helpful?

    0 comments
  4. Ramesh 181.9K Reputation points Volunteer Moderator
    2022-09-26T12:29:10+00:00

    Mike,

    In this output, there is an additional ProgID (cached) → ("AppXvsqkg1th80rv6s2rkh5m1hjp3hxryydd"). But no info about this item, and not sure if it's causing the issue.

    Running a ProcMon trace would give us a detailed insight. If you decide to run it, here are the instructions:

    Place a JPG file on your desktop.

    Download ProcMon from Microsoft

    Close all running programs.

    Start ProcMon and begin monitoring (Ctrl + E).

    Restore down ProcMon window size such that you can see the JPG file on your desktop.

    Right-click on the JPG file, click Open With, and select the WinRT entry.

    Once the error window appears, switch to ProcMon and stop tracing.

    Save events (All Events) to a .PML format log file.

    Zip the file and upload it to your OneDrive.

    Was this answer helpful?

    0 comments