Windows 10 Apps closing immediately

[fiza]

When logged in as local admin the Microsoft Store and Apps work fine.

When logged in with a student account the Microsoft Store does not load with message "Try that again".

The Apps (3D Paint, Video, Calculator) all open and then immediately close.

 

I can't see any GP settings that would cause this

 

 

Any ideas please?

[BOOT]

Did you remove any apps via script\dism?

[fiza]

Did you remove any apps via script\dism?

 

yes we did

[BOOT]

There's a known issue with removing the [Microsoft.MicrosoftSolitaireCollection] app. It removes dependencies and stops other apps from registering.

[fiza]

Ok so I changed the script to leave SolitaireCollection in place and now the Apps don't open but get underlined in the start menu.

Any ideas please?

[BOOT]

Looks like the apps aren't registering successfully on login.

Try using this tool to register them:

https://github.com/SN29856L/RegAllAppX/blob/master/RegAllAppX.exe

 

Run as the user you're testing and it'll log appx registration errors to a log file.

[fiza]

Looks like the apps aren't registering successfully on login.

Try using this tool to register them:

https://github.com/SN29856L/RegAllAppX/blob/master/RegAllAppX.exe

 

Run as the user you're testing and it'll log appx registration errors to a log file.

 

Doesnt seem to want to run when I am logged in as the user the Apps do not work for. That user is a student user account.

The Apps work fine when I log in as the local admin.

[Rob_D]

We had similar issues and pinned it down to roaming profiles.

 

For us, if the user already had a cached profile on that machine (we delprof everything at shutdown) then it broke the modern apps (like calculator/photos/paint3d).

Clearing down the users roaming profile fixed it (the powershell scripts are no good as they have to be run as an administrator in the affected user's logon environment - and we can't do both with staff/student accounts), but it breaks again as soon as the user logs onto a machine with an old profile cached.

[fiza]

We had similar issues and pinned it down to roaming profiles.

 

For us, if the user already had a cached profile on that machine (we delprof everything at shutdown) then it broke the modern apps (like calculator/photos/paint3d).

Clearing down the users roaming profile fixed it (the powershell scripts are no good as they have to be run as an administrator in the affected user's logon environment - and we can't do both with staff/student accounts), but it breaks again as soon as the user logs onto a machine with an old profile cached.

Thanks. We have roaming profiles too. Did you come up with a solution other than not use roaming profiles?

[Rob_D]

Thanks. We have roaming profiles too. Did you come up with a solution other than not use roaming profiles?

Unfortunately, no. We installed a 3rd party calculator and are looking at moving to UEV and local profiles instead.

If we do come up with something then I'll post it here.