Skip to main content
Super User

Return to Answer

added 505 characters in body
Source Link
Ken
Ken
  • 26
  • 3

PowerShell command with the All Users option may work for Windows 10.

EDIT: Reorganized my post for added clarity.

Permissions on the WindowsApps folder permissions at %ProgramFiles%\WindowsApps may prevent you from successfully re-register existing Universal Apps. Here are the stepsThe first step is to grant yourself access rights.

Admin CommandCommand Prompt - Run as Administrator ( 
Start > Run or Search > Command or CMD > Right-click and click Run as Admin).

PowerShell - Run as Administrator
Start > Run or Search > PowerShell > Right-click and click Run as Admin.

Using an Administrator Command Prompt

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Optionally you could add any other specific users other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Next, temporarily Unrestrict the PowerShell environment to run it.

Using an AdminAdministrator PowerShell Prompt (Start > Run or Search > powershell > Run as Admin)

Set-ExecutionPolicy Unrestricted (use before if necessary)
Set-ExecutionPolicy RemoteSigned (use afterwards if you run Unrestricted)

Command includingFix All Universal Apps and use the All Users option to attempt to re-register WindowsApps.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

The command above attempts to re-register all Universal Apps. You could also re-register Universal Apps individually as outlined below.

Fix Calculator App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

Fix Windows Store App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register $env:ProgramFiles\WindowsApps\Microsoft.WindowsStore_COPYYOURSPECIFICVERSIONPATHHERE\AppxManifest.xml

Final tip:Final tip:  
If there is a working clean-install v1511 instance or a successfully upgraded v1511 instance you can also copy the contents of C:\Program Files\WindowsApps from the good instance to the bad one. Do not overwrite, simply allow any missing components to copy without replacing any existing components.

The steps above have worked for me on several Windows 10 instances that we experienced problems on post in-place upgrading to version 1511 build 10586.

Regardless, I do not blame you if you wantanyone who wants to wait for an official fix from Microsoft.

PowerShell command with the All Users option may work.

EDIT: Reorganized my post for added clarity.

Permissions on the WindowsApps folder at %ProgramFiles%\WindowsApps may prevent you from successfully re-register existing Universal Apps. Here are the steps to grant yourself access rights.

Admin Command Prompt (Start > Run or Search > CMD > Run as Admin)

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Optionally you could add any other specific users other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Next, temporarily Unrestrict the PowerShell environment to run it.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Set-ExecutionPolicy Unrestricted (use before if necessary)
Set-ExecutionPolicy RemoteSigned (use afterwards if you run Unrestricted)

Command including the All Users option to attempt to re-register WindowsApps.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

The command above attempts to re-register all Universal Apps. You could also re-register Universal Apps individually as outlined below.

Fix Calculator App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

Fix Windows Store App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register $env:ProgramFiles\WindowsApps\Microsoft.WindowsStore_COPYYOURSPECIFICVERSIONPATHHERE\AppxManifest.xml

Final tip: If there is a working clean-install v1511 instance or a successfully upgraded v1511 instance you can also copy the contents of C:\Program Files\WindowsApps from the good instance to the bad one. Do not overwrite, simply allow any missing components to copy without replacing any existing components.

The steps above have worked for me on several Windows 10 instances that we experienced problems on post in-place upgrading to version 1511 build 10586.

Regardless, I do not blame you if you want to wait for an official fix.

PowerShell command with the All Users option may work for Windows 10.

EDIT: Reorganized my post for added clarity.

WindowsApps folder permissions at %ProgramFiles%\WindowsApps may prevent you from successfully re-register existing Universal Apps. The first step is to grant yourself rights.

Command Prompt - Run as Administrator 
Start > Run or Search > Command or CMD > Right-click and click Run as Admin.

PowerShell - Run as Administrator
Start > Run or Search > PowerShell > Right-click and click Run as Admin.

Using an Administrator Command Prompt

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Optionally you could add any other specific users other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Next, temporarily Unrestrict the PowerShell environment to run it.

Using an Administrator PowerShell Prompt

Set-ExecutionPolicy Unrestricted (use before if necessary)
Set-ExecutionPolicy RemoteSigned (use afterwards if you run Unrestricted)

Fix All Universal Apps and use the All Users option.

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

The command above attempts to re-register all Universal Apps. You could also re-register Universal Apps individually as outlined below.

Fix Calculator App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

Fix Windows Store App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register $env:ProgramFiles\WindowsApps\Microsoft.WindowsStore_COPYYOURSPECIFICVERSIONPATHHERE\AppxManifest.xml

Final tip:  
If there is a working clean-install v1511 instance or a successfully upgraded v1511 instance you can also copy the contents of C:\Program Files\WindowsApps from the good instance to the bad one. Do not overwrite, simply allow any missing components to copy without replacing any existing components.

The steps above have worked for me on several Windows 10 instances that we experienced problems on post in-place upgrading to version 1511 build 10586.

Regardless, I do not blame anyone who wants to wait for an official fix from Microsoft.

added 505 characters in body
Source Link
Ken
Ken
  • 26
  • 3

PowerShellPowerShell command with the All UsersAll Users option may work.

Admin PowerShellEDIT: Reorganized my post for added clarity.

Permissions on the WindowsApps folder at %ProgramFiles%\WindowsApps may prevent you from successfully re-register existing Universal Apps. Here are the steps to grant yourself access rights.

Admin Command Prompt (Start > Run or Search > powershellCMD > Run as Admin)

Get-AppXPackageicacls -AllUsers"%ProgramFiles%\WindowsApps" |/save Foreach"%TEMP%\WindowsApps.acl" {Add-AppxPackage/Q
takeown -DisableDevelopmentMode/F -Register"%ProgramFiles%\WindowsApps"
icacls “$($_.InstallLocation)\AppXManifest.xml”}"%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

That command will attempt to re-register all Universal AppsOptionally you could add any other specific users other than the Current User. If it fails

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, you may needrestore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Next, temporarily Unrestrict the PowerShell environment to run it.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

You could alsoCommand including the All Users option to attempt to re-register Universal Apps individually. To do so requires either access to %ProgramFiles%\WindowsApps or the RegistryWindowsApps.

Calculator AppAdmin PowerShell (for ExampleStart > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft“$($_.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifestInstallLocation)\AppXManifest.xml"xml”}

The next problem you may encounter is the rights on the WindowsApps folder at %ProgramFiles%\WindowsApps preventing even read-only operations. And, in this case, higher permission operationscommand above attempts to re-register existingall Universal Apps.

Temporarily you could work around the permission issue. Then you You could register individualalso re-register Universal Apps one-by-one. The ICACLS command can be used to take ownership and then return it to the TrustedInstallerindividually as outlined below.

Administrator Command PromptFix Calculator App (Start > Run or Search > CMD > Run as Adminsee version path in %ProgramFiles%\WindowsApps)

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icaclsAdd-AppxPackage "%ProgramFiles%\WindowsApps"-DisableDevelopmentMode /grant-Register "%username%""C:F\Program /QFiles\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

Separately you could also add another specific user other than the Current User.Fix Windows Store App (see version path in %ProgramFiles%\WindowsApps)

icaclsAdd-AppxPackage "%ProgramFiles%\WindowsApps"-DisableDevelopmentMode /grant-Register "EXACTUSERNAME"$env:F /QProgramFiles\WindowsApps\Microsoft.WindowsStore_COPYYOURSPECIFICVERSIONPATHHERE\AppxManifest.xml

FinallyFinal tip: If there is a working clean-install v1511 instance or a successfully upgraded v1511 instance you can also copy the contents of C:\Program Files\WindowsApps from the good instance to the bad one. Do not overwrite, restore ownership rightssimply allow any missing components to TrustedInstaller using this commandcopy without replacing any existing components.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Afterwards try the commandsThe steps above again while the necessary rights are in place.

Those have worked for me on several Windows 10 instances that we experienced problems on post in-place upgrading to version 1511 build 10586.

Regardless, I do not blame you if you want to wait for an official fix.

PowerShell command with the All Users option may work.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

That command will attempt to re-register all Universal Apps. If it fails, you may need to temporarily Unrestrict the PowerShell environment to run it.

You could also re-register Universal Apps individually. To do so requires either access to %ProgramFiles%\WindowsApps or the Registry.

Calculator App (for Example)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

The next problem you may encounter is the rights on the WindowsApps folder at %ProgramFiles%\WindowsApps preventing even read-only operations. And, in this case, higher permission operations to re-register existing Universal Apps.

Temporarily you could work around the permission issue. Then you could register individual Universal Apps one-by-one. The ICACLS command can be used to take ownership and then return it to the TrustedInstaller.

Administrator Command Prompt (Start > Run or Search > CMD > Run as Admin)

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Separately you could also add another specific user other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Afterwards try the commands above again while the necessary rights are in place.

Those have worked for me on several Windows 10 instances we experienced problems on post version 1511 build 10586.

PowerShell command with the All Users option may work.

EDIT: Reorganized my post for added clarity.

Permissions on the WindowsApps folder at %ProgramFiles%\WindowsApps may prevent you from successfully re-register existing Universal Apps. Here are the steps to grant yourself access rights.

Admin Command Prompt (Start > Run or Search > CMD > Run as Admin)

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Optionally you could add any other specific users other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Next, temporarily Unrestrict the PowerShell environment to run it.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Command including the All Users option to attempt to re-register WindowsApps.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

The command above attempts to re-register all Universal Apps. You could also re-register Universal Apps individually as outlined below.

Fix Calculator App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

Fix Windows Store App (see version path in %ProgramFiles%\WindowsApps)

Add-AppxPackage -DisableDevelopmentMode -Register $env:ProgramFiles\WindowsApps\Microsoft.WindowsStore_COPYYOURSPECIFICVERSIONPATHHERE\AppxManifest.xml

Final tip: If there is a working clean-install v1511 instance or a successfully upgraded v1511 instance you can also copy the contents of C:\Program Files\WindowsApps from the good instance to the bad one. Do not overwrite, simply allow any missing components to copy without replacing any existing components.

The steps above have worked for me on several Windows 10 instances that we experienced problems on post in-place upgrading to version 1511 build 10586.

Regardless, I do not blame you if you want to wait for an official fix.

Source Link
Ken
Ken
  • 26
  • 3

PowerShell command with the All Users option may work.

Admin PowerShell (Start > Run or Search > powershell > Run as Admin)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

That command will attempt to re-register all Universal Apps. If it fails, you may need to temporarily Unrestrict the PowerShell environment to run it.

Set-ExecutionPolicy Unrestricted (use before if necessary)
Set-ExecutionPolicy RemoteSigned (use afterwards if you run Unrestricted)

You could also re-register Universal Apps individually. To do so requires either access to %ProgramFiles%\WindowsApps or the Registry.

Calculator App (for Example)

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_COPYYOURSPECIFICVERSIONPATHHERE\appxmanifest.xml"

The next problem you may encounter is the rights on the WindowsApps folder at %ProgramFiles%\WindowsApps preventing even read-only operations. And, in this case, higher permission operations to re-register existing Universal Apps.

Temporarily you could work around the permission issue. Then you could register individual Universal Apps one-by-one. The ICACLS command can be used to take ownership and then return it to the TrustedInstaller.

Administrator Command Prompt (Start > Run or Search > CMD > Run as Admin)

icacls "%ProgramFiles%\WindowsApps" /save "%TEMP%\WindowsApps.acl" /Q
takeown /F "%ProgramFiles%\WindowsApps"
icacls "%ProgramFiles%\WindowsApps" /grant "%username%":F /Q

Separately you could also add another specific user other than the Current User.

icacls "%ProgramFiles%\WindowsApps" /grant "EXACTUSERNAME":F /Q

Finally, restore ownership rights to TrustedInstaller using this command.

icacls "%ProgramFiles%\WindowsApps" /setowner "NT Service\TrustedInstaller"

Afterwards try the commands above again while the necessary rights are in place.

Those have worked for me on several Windows 10 instances we experienced problems on post version 1511 build 10586.