no longer able to restart Windows Explorer

It's been 2 weeks with no response to my sfc /scannow log. The problem persists, and I am at a loss as to how to solve it. The symptoms occur every time I run a Windows update

- c:\windows\system32\explorer.exe fails to start with Windows as directed in the SHELL registry key. Attempts to start this process using conventional methods (eg. "New Task" in Task Manager) fail; the process does not appear on the list in Task Manager.
- c:\windows\explorer.exe runs "normally" - that is, it is able to start, however system tray icons such as VOLUME, POWER, and NETWORK indicators are irrestorably missing.
- When calling c:\windows\system32\explorer.exe while another instance of explorer.exe is active, the result is a window within the existing explorer.exe process.
- The problem resolves itself after 2-3 days and remains resolved until the next round of system updates.
- Windows behaves oddly when the shell does not start on logon i.e. when HKEY_LOCAL_MACHINE\SOFTWARE\WINDOWS NT\WINLOGIN\SHELL = C:\WINDOWS\SYSTEM32\EXPLORER.EXE when this process fails to launch. For instance, I am unable to load my touchpad settings during this time; the default settings load instead. I am unable to modify these settings until the symptoms clear up. This is very disorienting for me, as I tend to type while resting my palm heels on either side of the touchpad, so I frequently touch the touchpad, and the default settings interpret this as a LEFT MOUSE CLICK unlike my custom settings.

SFC /SCANNOW Command tutorial shows how to replace any named problem files. If this fails you can consider doing a Repair Install.

Have you checked thoroughly for infection using Malwarebytes and your AV as it may not repair until disinfected. If you are running a bloatware AV then uninstall it and install Microsoft Security Essentials, run a Full scan and try running with it for awhile to see the difference.

In addition work through the other Troubleshooting Steps for Windows 7 which almost always uncovers the problem.

Also; in addition to what greg mentioned; I would do a spyware scan as well using the program at the link below; even though it may not be something spyware related; its still worth doing a full scan of your system.

SUPERAntiSpyware - Downloading File

There is almost never any point in running an SFC scan more than once unless file changes have occured. Almost the only thing it chanes is the look of the summary report. I'lltake a look at the log when I get back to a real pc :)

OK - back a a PC now :)

Here's the error from the SFC log...

Code:

 Line 239561: 2014-03-23 12:42:30, Info                  CSI    00000430 [SR] Repairing 1 components
 Line 239562: 2014-03-23 12:42:30, Info                  CSI    00000431 [SR] Beginning Verify and Repair transaction
 Line 239563: 2014-03-23 12:42:30, Info                  CSI    00000432 [SR] Cannot repair member file [l:40{20}]"UIAutomationCore.dll" of Microsoft-Windows-UIAutomationCore, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

There don't appear to be any other errors on the past couple of weeks, in the CBS background log.

I'll post a fix for this in a few minutes.

I've uploaded a file - pkxaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\pkxaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\pkxaa
or
DIR E:\pkxaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\pkxaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply