Windows 10 v1511 explorer.exe crashes Error: 0x800f081f

Hi,

Thank you for posting your query in Microsoft Community.

Sorry for the inconvenience caused.

The Method 2: Clean boot had already been tried, but I went and made sure it was configured as such. 

Did Method 1 and it says that an error was found and fixed. It said: "One or more Windows Update components are configured incorrectly." and it's marked as "Fixed". 

Problem is still there. 

I found another problem when trying to open an image using the default image viewer within Windows 10. I get "The remote procedure call failed.".

It seems that this windows update screwed something up.

If it helps, my case number is 1314433891.

Hello,

Thank you for keeping us updated.

Appreciated the steps you have taken so far to resolve the issue.

Step 1: Let us try to run the troubleshooter for Windows apps and check if it helps.

App Troubleshooter is an automated tool which we have developed to address a number of known issues that can prevent the Apps from running properly. This troubleshooter automatically fixes some issues, including suboptimal screen resolution, incorrect security or account settings etc. You can click on this link to download and run the Apps troubleshooter.

Step 2: Let us run SFC scan and see if it brings any difference.

The sfc /scannow (System File Checker) command scans all protected system files, and replaces incorrect versions with correct Microsoft versions.

1. Press Windows + X key on the keyboard.
2. Click on Command Prompt (Admin).
3. At the command prompt window, type the following commands:
4. Select Run as Administrator.
5. Type sfc /scannow and hit Enter.

Hope it helps.

Kindly let us know if you need any further assistance with Windows, we are glad to assist you.

Step 1: App troubleshooter didn't find any issue present.

If I click "Explore additional options" within the app after it has finished diagnosis, it closes/crashes and a few seconds later this error pops up:

There's a pattern here.

Step 2: I had already run sfc /scannow as described in my original post. I did run it again and it found corrupt files but was unable to fix some of them. This is the same as before and the tech people stumbled upon that as well.

Problem still exists.

Here's something from the log from c:\Windows\Logs\CBS\CBS.log that the sfc created:

Lots and lots of lines like this:

2015-11-27 11:30:14, Info                  CSI    0000006f@2015/11/27:11:30:14.936 Primitive installers committed for repair
2015-11-27 11:30:14, Info                  CSI    00000070@2015/11/27:11:30:14.944 Primitive installers committed for repair
2015-11-27 11:30:14, Info                  CSI    00000071@2015/11/27:11:30:14.944 Primitive installers committed for repair

and in the end there are some things like this:

2015-11-27 11:36:49, Info                  CSI    000049ed [SR] Beginning Verify and Repair transaction
2015-11-27 11:36:49, Info                  CSI    000049ee Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 PLvXf+OpSM+SFE348T26Q8uNEte+29MkAt7SIIqkYPI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2015-11-27 11:36:49, Info                  CSI    000049ef [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-27 11:36:49, Info                  CSI    000049f0@2015/11/27:11:36:49.633 Primitive installers committed for repair

2015-11-27 11:36:49, Info                  CSI    000049f2 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-27 11:36:49, Info                  CSI    000049f3 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-27 11:36:49, Info                  CSI    000049f4 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 PLvXf+OpSM+SFE348T26Q8uNEte+29MkAt7SIIqkYPI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 11:36:49, Info                  CSI    000049f5 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 PLvXf+OpSM+SFE348T26Q8uNEte+29MkAt7SIIqkYPI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 11:36:49, Info                  CSI    000049f6 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

I went through the whole file, searching for the string "corrupt" and found that in all the other cases of running dism and sfc, they're complaining about this same file.

I updated my NVIDIA drivers from 358.91 to 359. Problem still persists and sfc /scannow still returns the same error.

I did analyze the log file though and found out this:

With the old 358.91 driver it expected the hash "{l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}" but found "{l:32 PLvXf+OpSM+SFE348T26Q8uNEte+29MkAt7SIIqkYPI=}".

With the new 359 driver it expects the hash "{l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}" (same as before) but found "{l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=}". This means that the file has been changed between drivers but for some reason Windows expects some other version. This might even mean that the file isn't corrupted.

I'm not even sure that this has anything to do with my problem.

The new log:

2015-11-27 12:28:31, Info                  CSI    000049f2 [SR] Beginning Verify and Repair transaction
2015-11-27 12:28:31, Info                  CSI    000049f3 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 12:28:31, Info                  CSI    000049f4 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-27 12:28:31, Info                  CSI    000049f5@2015/11/27:12:28:31.268 Primitive installers committed for repair
2015-11-27 12:28:31, Info                  CSI    000049f6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 12:28:31, Info                  CSI    000049f7 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-27 12:28:31, Info                  CSI    000049f8 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-27 12:28:31, Info                  CSI    000049f9 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 12:28:31, Info                  CSI    000049fa Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-27 12:28:31, Info                  CSI    000049fb [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-11-27 12:28:31, Info                  CSI    000049fc@2015/11/27:12:28:31.299 Primitive installers committed for repair
2015-11-27 12:28:31, Info                  CSI    000049fd [SR] Repair complete
2015-11-27 12:28:31, Info                  CSI    000049fe [SR] Committing transaction

Hello,

Thank you for your reply.

Appreciate the steps you have taken so far to fix this issue.

If you are unable to repair some files after performing SFC scan, I suggest you to refer “Windows Resource Protection found corrupt files but was unable to fix some of them.

Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log”. Under the section “Run the System File Checker tool (SFC.exe)” to repair the corrupted files after performing SFC scan.

Use the System File Checker tool to repair missing or corrupted system files

Hope it helps.

Let us know the status, we are glad to assist you further.

Hello,

Thank you for the update on the issue.

I would suggest you to Run the powershell command

The powershell command helps to fix the corruptions in system/programs files due to which the apps might not be working. Please follow the below mentioned steps to the run the command:

1. Open an Elevated Powershell prompt by pressing the Windows Key, typing Powershell, then pressing Ctrl+Shift+Enter 

2. Paste the following command into Powershell and execute it:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Hope this information is helpful. Please write back to us if you need any further assistance, we'll be glad to assist you.

Hello,

Thank you for your reply.

Appreciate the steps you have taken so far to fix this issue.

If you are unable to repair some files after performing SFC scan, I suggest you to refer “Windows Resource Protection found corrupt files but was unable to fix some of them.

Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log”. Under the section “Run the System File Checker tool (SFC.exe)” to repair the corrupted files after performing SFC scan.

Use the System File Checker tool to repair missing or corrupted system files

Hope it helps.

Let us know the status, we are glad to assist you further.

The advice to manually replace a corrupted system file with a known good copy of the file does not work for me. I do not have a known good copy of said file.

Also, the file has been replaced by updating the NVidia drivers but Windows is still expecting some other version of the file. To me it seems the file is not corrupt but rather this is an error of the hash check mechanism.

Since last time I've run all the updates available but I'm still getting the same errors.

Hello,

Thank you for the update on the issue.

I would suggest you to Run the powershell command

The powershell command helps to fix the corruptions in system/programs files due to which the apps might not be working. Please follow the below mentioned steps to the run the command:

1. Open an Elevated Powershell prompt by pressing the Windows Key, typing Powershell, then pressing Ctrl+Shift+Enter 

2. Paste the following command into Powershell and execute it:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Hope this information is helpful. Please write back to us if you need any further assistance, we'll be glad to assist you.

This looks like a script run during my remote desktop sessions with tech support.

I'm getting a whole lot of red errors. Like so:

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.
Merge Failure : error 0x80070003 : Cannot register the Microsoft.Messaging_1.11.19004.0_x86__8wekyb3d8bbwe package beca
use there was a merge failure with the following file: C:\Program Files\WindowsApps\Microsoft.Messaging_1.11.19004.0_ne
utral_split.language-is_8wekyb3d8bbwe\resources.pri
NOTE: For additional information, look for [ActivityId] aebcd165-32c2-0002-1add-bcaec232d101 in the Event Log or use th
e command line Get-AppxLog -ActivityID aebcd165-32c2-0002-1add-bcaec232d101
At line:1 char:38
+ ...  | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.I ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Program File...ppXManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

No change on the errors part.

But now when I try to open images, like .png files, they get opened in MSPaint. The Photos app seems to be gone.

Hello,

Thank you for the update on the issue.

Let’s follow the below mentioned steps and check if that helps:

New User Account

Try these steps to create a new user account and check if it fixes the issue. Refer to the steps below to create a new User Account:

1. Go to Settings.

2. Choose Accounts and then select Other User Accounts towards the left.

3. Select Add an Account.

4. Enter a user name and hit Next.

5. Click on Finish.

6. Sign out from the current Account and Log into the new account.

7. Check if issue persists.

In addition to the above steps, I would suggest you to please refer to the below mentioned Microsoft article for more information

Create a local user account in Windows 10

http://windows.microsoft.com/en-us/windows-10/create-a-local-user-account-in-windows-10

Hope this information is helpful. Please write back to us if you need any further assistance, we'll be glad to assist you.