Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, September 18, 2018 9:28 PM
Windows 10 Calculator not working for regular users.
I can log into the machine with my Account (Domain Admin) and it works fine.
I can log in with the Root Admin account and it works fine.
If anyone else logs into the machine, even if I grant them Local Admin Privileges, the program will not work.
And NO I will not be granting them Domain Admin... haha
I have tried Numerous suggestions that have been posted.
- Reset the app (Current user)
- Reset the app (All users)
- Re-Register the App (Current User)
- Re-Register the App (All Users)
- Reset All apps (Current user)
- Reset All apps (All users)
- Re-Register All Apps (Current User)
- Re-Register All Apps (All Users)
- Went to the MS Store to try re-downloading the App - The button does nothing
I have other machines that were setup and deployed after these, that everything works normally. (Different Update Packs?)
The craziest part of all this is that it works normally if the current user is Root Admin or Domain Admin, but nothing else.
Any ideas?
All replies (15)
Wednesday, September 19, 2018 9:39 AM
Hi,
According to the current situation, I’d like to confirm your PC’s version through Settings > System > About and regular user means local account or domain account?
In addition, what type of profile domain Admin and regular user are using, local or roaming profile?
* *
“the program will not work” Is there any error message? You can share a screenshot through OneDrive and attach a shared link in your reply.
Note: Please ease your privacy information in the upload picture.
Hope these are helpful.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, September 20, 2018 2:59 PM
I am not sure where PC Version info would make any difference as it is happening on several different machines:
- DELL Optiplex 5060, 7060, and XPS 15 9560 - all running Win10 v1803 - with all updates.
These are Network Domain Accounts.
The error message is as follows: "You'll need a new app to open this calculator" But, as I said, It opens normally for My Domain Admin account, The Root Admin account, but not for anyone else.
Additionally, It works fine on machines that I have recently setup and deployed.
Thursday, September 27, 2018 10:10 AM
Hi,
I suggest that you go to this link to follow steps to run the troubleshooter for Windows 10 apps.
After performing the above resolution, try and check if the issue is fixed. If the issue persists, reset the Windows Store by following these steps:
1. Press the Windows key + R to launch the Run dialog box.
2. Type Wsreset.exe and press Enter.
Best
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, October 16, 2018 1:32 PM
I tried this on most of the affected machines... no change.
Again, the issue is not that the app is not installed, it is that it does not work if the user does NOT have Domain Admin rights.
If the user logs out of the machine, and I log in, the app works fine.
I then log out and the user logs back in, Doesn't work again.
My belief is that this is caused by a recent Update. I tried having one of the users log in before I ran the updates to 1803 from factory delivered 1709, and the apps work fine. Run the Upgrades to 1803, stops working. I cannot leave the machines on 1709 though. We have GPs that require it to be on 1803.
Has anyone identified what updates may be causing this?
From what what my research has found, the issue goes back quite a ways, but seems to come and go.
Friday, December 14, 2018 12:07 PM
We, a school in the Netherlands, have the same problem.
We are in the process to upgrade from Windows 10 1607 tot Windows 10 1803. For existing domain users (with a roaming profile) the Windows Calculator is not available. When we delete the roaming profile and start with a clean profile it works fine.
Does anybody knows what is blocking the usage of Windows Store Apps (Windows Calculator in this case) after deploying an new image based on a upgrade of Windows 10?
Only solution that worked until now is removing the roaming profile. That is not a good solution for 1500 employess and 13000 students.
Already tried: register the appxpackage, wreset.
Tuesday, January 29, 2019 2:22 PM
Was this ever resolved?
Wednesday, January 30, 2019 11:22 AM
Hi,
We have seen the same thing.
If you run the powershell command Get-AppxPackage -AllUsers -Name Microsoft.WIndowsCalculator you can see two versions of the calculator one that is installed and a newer one which is staged. I guess that when a new user tries to access the calculator it tries to use the new version so it won't load.
Does anyone else know more about this?
Thanks
Friday, February 1, 2019 5:20 AM
Hello, J Townsend,
I am also experiencing the issue with one user running on version 1709 . If I log in as Local or a Domain Admin the calculator is there. But if I log in as one particular user it doesn't even show that it is installed. If I log in as any other domain user the calculator is there. So it's just affecting that one user on that one computer. I have tried the following:
- Windows updates.
- Powershell: Get-AppxPackage -allusers *windowscalculator* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
- Got the affected user to log into a different computer and the calculator was available to him.
- Reset the app.
- Updated the Window store and it's apps.
- Ran the Windows store troubleshooter.
- Manually download the app from the store - bombed out.
None of the above worked. Until I decided to uninstall the recent updates and then he was able to go back into the store and download it without error.
Those updates were:
KB4480967
KB4090007
KB4480978
KB4094276
KB4293700
KB4055237
KB4055994
Apologies I'm not sure if it is one update that causes the issue, a combination of updates from that list or all the updates.
Friday, March 1, 2019 5:35 PM
*** I FOUND WHAT WAS CAUSING THIS FOR ME!!!***
The policy setting "Hide and disable all items on the desktop" located under User Config/Admin Templates/Desktop. If i turn this off and recreate my profile the calc is back. Problem is i really need this policy though. Maybe this will help someone here.
Same thing here. This is a new 1809 build. XenDesktop with UPM. Tried enabling the policy "Allow deployment operations in special profiles" under Computer/Admin Templates/Windows Components/App Package Deployment. Still no go. I swear MS is trying to make us look like idiots in front of user. And doing a great job of it too. At least they have one thing down.
Monday, May 6, 2019 3:17 PM | 1 vote
To anyone else experiencing this issue, in my case, I found the technical issue, but no structural solution. This did not happen in our 1703 environment and caused delays in our 1809 rollout. Microsoft support did not help one bit.
The issue appears to be any user account logging in for the first time with a Roaming User Profile.
C:\Users\username\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h4txyewy\TempState
There are 3 files StartUnifiedTileModelCache.dat, TileCache_100_0_Data.bin, TileCache_100_0_Header.bin
Workaround #1
One workaround is to delete the profile, let the person log back in with the roaming profile and the account works again the second time. This works but does not make sense to me.
Workaround #2
Here's a workaround that works for my environment:
Gather from a good machine those 3 files using a non-roaming user account, i.e. log on with an administrator account, and log off, copy the files to another location to be used.
Replace the 3 files of the user profile before they log in
OR
while the person is logged in, set up a repair script to kill ShellExperienceHost.exe to replace the three files
I created an SCCM Application to "repair" it while running it in the user's software center.
So far in my environment, the three files can be used across other machines
Thursday, May 30, 2019 12:47 PM
After trying most of the suggestions on this post, here is the only thing that worked for me.
The user moved from another department that used Roaming Profiles, our department does not. The user's roaming profile was turned off before logging into a new workstation. No Sticky Notes or Calculator were available to her in her new local profile.
Backed up her profile outside of the rootdrive/users/ directory. Deleted her profile from the System Properties tool (after verifying that it was not registered as a roaming profile, which removed her account from the workstation. Logged her back in to create a new profile, and the two missing applications then worked. I then copied back her favorites, etc from the backup of the profile. I assume at this point I could re-initiate roaming profiles for her and things would still work (they worked in the other department).
This doesn't help those with hundreds of affected accounts, but it worked for this one-off issue.
Monday, July 22, 2019 5:12 PM
Thanks Khang_N for this information. I replaced the 3 files as noted in Workaround #2, then ran the command listed in the proposed answer of this technet thread.
The calculator and several other missing apps were then restored and functioning for subsequent user logons. We're running Windows 10 version 1803 with roaming profiles and access blocked to the Windows Store by domain policy.
Thursday, August 1, 2019 1:14 AM
Did you ever get this resolved? I'm facing the same issue.
Monday, October 21, 2019 6:29 PM
Had the same problem.
What I did was log in as admin on the PC
Add the user to the local admin group
log back in as that user, if the apps arent there run the powershell command to reinstall
They will show up now
Remove the user from local admin group and the apps will still remain. I just tested it and it fixed the issue.
Friday, January 10, 2020 10:59 AM
I have a reliable workaround via registry in my environment but unfortunately still no fix. W10 1803, using Roaming Profiles. At least doesn't require messing with local admin groups or deleting profiles.
This also requires the user to have logged in to a PC at least once to trigger the Appx failure. So its a reactive fix. Annoyingly the reg key involved is under HKLM but the keys are specific to the user SID.
- Open Regedit and go to HKLM\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore
- Delete the user's SID key (or you can delete any SID keys from here, it doesn't seem to have a negative impact on other users of the machine).
- Reboot user's PC. When the user logs back in (at least in my environment), all Appx applications (Calc, Sticky Notes etc.) work fine. A reboot is required as Windows seems to configure itself (I assume initialising the Appx files) at boot. Logging off alone will not make the apps work.
Unfortunately the Appx applications will often be broken again when the user roams to a new PC, requiring the same step.
As the reg keys to delete are user SID specific, a query is needed to script delete, requiring Powershell. I run a script weekly on all machines to delete any existing HKLM Appx SID keys on all machines. This provides some pre-emptive fixing for users who have the issue but perhaps haven't noticed yet. The trade off is a slight boot delay due to the configuring windows step.
This issue, plus roaming causing the start menu to malfunction are the final 2 big problems giving our W10 deployment a bad name.
"I swear MS is trying to make us look like idiots in front of user." . This statement from a previous poster is too true.