Edit: This Issue has been - fortunately or unfortunately - solved by Yet Another Clean Install, as it has been specified toward the end of the text of this question.
Still, as advised by @Ramhound, we need to specify the fact that before noticing the manifestation of this Issue, the User Account Control had been disabled long time ago. For a certain period of time, still our Microsoft Windows Universal Windows Platform Static Software Applications have been working quite all right.
Now begins the Original Text of the Question.
Our Microsoft Windows Universal Windows Platform Static Software Applications have started vanishing today after their launch into execution.
We have already fully updated twice the Microsoft Windows 10 Operating System today. Everything has been working out smoothly. We would not blame the applying of any Software Update Packages this time.
What we have done has been to take the ownership of the WindowsApps Folder ourselves. It would have been enough just to add only Read Access to ourselves, as we just wanted to read a certain piece of data from within it.
Instead of doing that, we have gotten greedy and we have taken ownership of the whole Folder with all of its Sub-Folders and Files. We do not know how to set it back, as we cannot select the TrustedInstaller User when we have to.
Update:
Great answer, @harrymc. It did fix our Issue with the TrustedInstaller User.
We also had to check the following check-mark and to recursively apply the ownership to the Sub-Folders and to the Files within the WindowsApps Folder.
It would be great if you could improve your answer so that everything is automatically done recursively.
However, this did not solve our Issue. We have renamed the title of this question.
We might not be blamable at all. Other than this erroneous setting of the ownership of the WindowsApps Folder to ourselves, we have not done anything obviously wrong to the machine today. We have to imagine that the two Software Update Packages that we have applied today have messed up something related to the Microsoft Windows Universal Windows Platform Static Software Applications.
Behavior:
Some Microsoft Windows Universal Windows Platform Static Software Applications, such as the Microsoft Windows Calc Static Software Application or the Microsoft Windows Skype Static Software Application, are appearing shortly for a few seconds and then they are simply vanishing.
Some Microsoft Windows Universal Windows Platform Static Software Applications, such as the RCS-RDS-Digi Digi.Online Static Software Application, are processing something for a few tens of seconds and then they are simply vanishing.
Update:
What we have done other than messing up the ownership of the WindowsApps Folder has been to uninstall a certain number (around six) Static Software Applications - not only Microsoft Windows Universal Windows Platform Static Software Applications - before applying the two Software Update Packages.
Maybe the Microsoft Windows Installer had already gotten broken after the uninstallation of those around six Static Software Applications.
We have also applied the Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Microsoft Windows PowerShell One-Liner. It has been working out smoothly, except for Microsoft.Windows.StartMenuExperienceHost and for Microsoft.Windows.ShellExperienceHost.
However, the Microsoft Windows Universal Windows Platform Static Software Applications are still vanishing.
To sum up, here is the number of potential mistakes that we have committed:
The uninstallation of around six Static Software Applications - not only Microsoft Windows Universal Windows Platform Static Software Applications - from the Apps and Features Pane. Maybe they have been just too many at a time. Maybe they should have been followed by a reboot of the machine.
The erroneous setting of the ownership for ourselves for the
WindowsAppsFolder.The installation of two Software Update Packages. Maybe they have been just too many per day. Each of them have been automatically followed by a reboot of the machine.
Update:
Just to make sure that we did it correctly, we have rerun the icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller" /t One-Liner with the /t Switch in it.
The behavior is persisting.
Update:
Just to double-check everything, we have also rerun the Microsoft Windows PowerShell One-Liner, this time with the -AllUsers Switch:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
This time we have got lots of Error Messages.
For instance, once it was searching for the C:\AppXManifest.xml File and it was complaining that it does not exist. Therefore, the InstallLocation Variable was probably not set for that Static Software Application.
What we did notice today has been the fact that the Microsoft Windows Edge Web-Browser is working. It is located in the SystemApps Folder.
So, indeed, we might had messed up everything. Possible scenario:
The erroneous ownership setting of the
WindowsAppsFolder has made further modifications to these Static Software Applications impossible by theTrustedInstallerUser.The two Software Package Updates have modified something in an erroneous way, without complaining. The Success Message presented to the User was "You are up to date".
Even after the restoration of the correct ownership of the
WindowsAppsFolder to theTrustedInstallerUser, these Static Software Applications are no longer working.
Update:
Millions of thanks, guys, for your help, but apparently troubleshooting this Issue is going nowhere and it is working extremely, extremely slow.
We might have to reinstall the whole thing sometimes.
Just to note the output of the patch suggested by @harrymc, this is how far we have gone:
- The Troubleshooter of the Microsoft Windows Store Static Software Applications does not want to wake up itself from its own slumber that easily.
- Awakened in an administrative way, it is also requiring a passkey that should be given by a support professional.
We feel that we have been here before. We have debated this question for more than nine months and ten days. Its answer has been a simple Clean Install of the machine.
So we have to give some credit to @John also.
Closure:
We have finally closed this Issue after another Hellish Week-End.
We have been supported by Al Kim Repelliano or something from support.microsoft.com. We have been able to identify together the fact that during the subsequent manual uninstallations of around six Static Software Applications (not only Microsoft Windows Universal Windows Platform Static Software Applications) that we have performed on Saturday, something has gone wrong.
It might not have been the corruption of the Microsoft Windows Installer. Something else might have gone wrong. Al Kim Repelliano has shown us something, but we have been unable to grasp it that fast. These guys are moving way too fast.
We have decided together that the best solution was to revert the Operating System back to a certain System Restore Point that had happened to take place just before the manual uninstallation of the Backup and Sync from Google Static Software Application.
Al Kim Repelliano has ensured us that everything will work out smoothly. However, after the restoration of the System Restore Point, the Blue Screen of Death has come back into our world.
We have attempted to boot the machine from either of three (!) System Repair Disks. None of them has booted the machine, for unknown reasons.
We have rebooted the machine using an Universal Serial Bus Flash Drive. We have attempted to apply the Repair Option, as advised by @John. For some unknown reason, the System Image Restoration Operation that was supposed to use a System Image located on another Universal Serial Bus External Winchester Hard Disk Drive has failed with a stupid Error Message, although the System Image had been performed quite recently on the same machine.
After a while, one of the three System Repair Disks has miraculously started to work. It has been able to boot the machine. Using the Universal Serial Bus Flash Drive that contains the Installation Kit of the Microsoft Windows 10 Operating System, we have been able to delete the entire Operating System Software Primary Partition and then to recreate it after a few attempts (!).
Therefore, no Repair Option has ever been working this time. The Solution to this Problem has been to perform yet another Clean Install.
It is interesting that we had the inspiration to copy the C:\Users\DOBRE\Documents\ Folder to the Internal_Data (D:) Software Primary Partition before accepting Al Kim Repelliano's speedy urge to apply the restoration of the System Restore Point.
We would like to thank @harrymc, @Ramhound and @John for their patient support that they have been offering to us during the manifestation of this Issue.
