Change PC Settings link is broken after update to windows 8.1

Yes!  The non-system reset solution to this problem at last!  Why is this so hard to find?  Thank you!!

I had this problem. I could not get into PC settings. Frustrated, i uninstalled all my apps because none of the apps were working. Just a blank blue screen. Today i did the WSreset as advised. Everything seems to be normal now. If only i had got to this page earlier. 

Thanks.

Struggled with Store, Settings, Skydrive etc not working.

Got the Store working and some other apps too using dowloaded troubleshooters from Microsoft, but PC Settings was a no go as well as Skydrive and Photos.

I made a new user using admin tools in control panel and PC Settings was working for this user so I knew it could work and after much more digging around I found this thread here:

http://social.technet.microsoft.com/Forums/sqlserver/en-US/c4147bcc-a430-43fe-b4e9-f999552568da/81-store-apps-wont-load?forum=w8itprogeneral

It had all of the steps I used to get the Store working again and those that had failed on the pc settings, and then this:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\ImmersiveControlPanel\AppxManifest.xml

Right click the start button and open a command prompt and then paste the above and hit enter.

PC settings working without even needing to reboot, hope this helps someone, paste it forward into other threads you all have no doubt looked at w/o finding this solution.

This fixed my PC Settings for me!!

Hi,

I have had several of these problems which I believe I have mostly repaired but I am going through a few more gleaning tid bits. :)

What I don't understand is, when you recommend "sfc", why don't you recommend "DISM" as well? In combination they are a GOD send! Here are some excerpts of a doc:

DISM /Online /Cleanup-Image /RestoreHealth

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Fixing component store corruption in Windows 8, 8.1 and Windows Server 2012

(Windows Vista, 7, 2008 and 2008 R2 was the System Update and Readiness Tool

(KB947821), commonly called CheckSUR.)

http://blogs.technet.com/b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx

joscon [Microsoft] Wed, Sep 26 2012 11:13 AM 120

One of the most used tools when fixing corruption for Windows Vista, 7, 2008 and 2008

R2 was the System Update and Readiness Tool (KB947821), commonly called CheckSUR. The

CheckSUR tool was an excellent way for most people to see what corruption had happened

on their store, and potentially fix that corruption if the tool contained the payload

to do so. I’ve written in the past how to use this mechanism to also fix corruption

when the CheckSUR utility doesn’t include the payload for your files to “fool”

CheckSUR into resolving the problem without needing to do all sorts of whacky

permission changes

The way this works in Windows 8 and Windows Server 2012 is different, in a fantastic

way. It’s called Inbox Corruption Repair and it brings the functionality of CheckSUR

into Windows rather than requiring a separate download to get the utility like you do

now. This is exposed in two ways, the first is really unseen by the end user and

happens when we detect a corrupted state when attempting to install fixes via Windows

Update. When this happens, we'll fix the corruption silently and then re-install the

prior packages. The manual way to use this tool is via DISM. The way this is exposed

is via the DISM /Cleanup-Image functionality. Here’s what the available switches do:

/CheckHealth: This checks to see if a component corruption marker is already present in

the registry. We’ll inform the user if there is corruption but nothing is fixed or

logged anywhere. This is merely a quick way to see if corruption currently exists.

Think of it as a read-only CHKDSK. This operation should be almost instantaneous.

/ScanHealth: This checks for component store corruption and records that corruption to

the C:\Windows\Logs\CBS\CBS.log but no corruption is fixed using this switch. This is

useful for logging what, if any, corruption exists. This operation takes ~5-10mins.

/RestoreHealth: This checks for component store corruption, records the corruption to

C:\Windows\Logs\CBS\CBS.log and FIXES the corruption using Windows Update. This

operation takes ~10-15mins or more depending on the level of corruption.

Best Regards,

Crysta