Windows 10: TWINUI Photos App Windows 10

Is there a fix yet for this issue.

:)

 

Microsoft photos app not showing up in Default app list. Jpg Pics opening in TWINUI

Hello,

I am getting an error "Class not Registered" while opening my JPEG images. I have right clicked and checked my available apps list to open JPEG file I could not find "Photos" app in that list. Instead TWINUI was set as a default app. How to disable TWINUI and
restore Microsoft Photos app to open my photos. I tried to find what TWINUI and thought of uninstalling it .But could not get any file or application named TWINUI in my system. I even tried to open Photos app directly from search bar it showed a dull colored
result where other apps are in regular color.

Any suggestion to reinstall the Photo App will be deeply appreciated.

Thank you

 

Windows 10 Photo App TWINUI

Hello Madhavi,

The issue that you're having It could be caused by a problem with the Photos app database. To reset the database, do the following steps:

• 
  Press Windows key + R.
  
• 
  Type: %appdata%\..\Local\Packages\Microsoft.Windows.Photos_8wekyb3d8bbwe\LocalState
  
• 
  Delete all the contents of that folder.
  
• 
  Restart the computer and check if issue persists.
  

Performing this will reset the internal state of the Photos app.

Also, If you are unsure whether you have the latest updates for Windows 10, we suggest that you check it by following the easy steps from this article:
Update Windows 10.

Ensuring your operating system to be always up-to-date will prevent software conflicts and errors.

We look forward to hear from you again about this issue.

 

TWINUI in place of some default apps


After upgrading several systems, on a couple of them I ran into an issue where instead on the standard Windows 10 default apps being listed for such things as Maps, Music Player, Photo Viewer, etc., "TWINUI" was listed. Fortunately it was easy to fix. All you have to do is open the standard default app, close it, go back to Settings, and it was miraculously fixed. It seemed to happen when going into a second user after the initial user setup completed and completing the setup for the second user.

JohnD