IE11 ERROR exit code = 0x00003715 (14101)

[minh]

Hi everyone! New forum member here working for a company of about 100,000 clients. We are seeing a high number of IE11 deployment failures in our enterprise and several of my end users, like many others in this forum, are not getting IE11 to install properly. I've attached the IE11_Main and CBS log files of one of my users who seems to be having one of the more common issues that we can't seem to pinpoint a root cause for.

We've run the Windows Update Diagnostic, SURT, performed a clean boot, installed all pre-requisites, and run the offline installer. While at least one of these steps has helped in a few cases, I have several where this does not help. Thanks in advance!

 

[NoelDP]

It looks to me like you have a corrupted Image from which you're building your installs
The CBS log shows the following at the start of the summary...

2015-09-28 15:41:05, Info CSI 00000525 [SR] Repairing 124 (0x000000000000007c) components

The list of files which SFC can't repair makes interesting reading....

	Line 36444: 2015-09-28 15:41:08, Info                  CSI    0000052c [SR] Cannot repair member file [l:22{11}]"license.rtf" of Microsoft-Windows-License-Default-Ultimate.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 36447: 2015-09-28 15:41:08, Info                  CSI    0000052e [SR] Cannot repair member file [l:22{11}]"license.rtf" of Microsoft-Windows-License-Default-HomeBasic.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
....
....
....
	Line 36603: 2015-09-28 15:41:08, Info                  CSI    00000596 [SR] Cannot repair member file [l:22{11}]"license.rtf" of Microsoft-Windows-License-Eval-Enterprise.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 36606: 2015-09-28 15:41:08, Info                  CSI    00000598 [SR] Cannot repair member file [l:22{11}]"license.rtf" of Microsoft-Windows-License-OEM-HomeBasicN.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 36609: 2015-09-28 15:41:08, Info                  CSI    0000059a [SR] Cannot repair member file [l:22{11}]"license.rtf" of Microsoft-Windows-License-OEM-UltimateE.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 36612: 2015-09-28 15:41:08, Info                  CSI    0000059c [SR] Cannot repair member file [l:24{12}]"spwizimg.dll" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

In short, it looks to me as if someone building the WIM decided to remove/void ALL the Windows EULA/SLA files - ignoring the fact that they are a required part of any Windows installation.

There are also a couple of other missing/void files which, again, are a necessary part of any Windows install.

You should check the integrity of the source Image, and if necessary rebuild and redistribute.

 

[minh]

Thanks for the response!

I had a chat with our Single Image SME on the topic and we have a few more details to share as a result. Our company used Credant for hard disk encryption at one point in time and he believes the reason for the .rtf issues is because Credant has potentially corrupted those files or left them encrypted.

As for the "spwizimg.dll" file, that used to be used to update the background and user icon in the build. We have moved away from that method for quite awhile now so we are tracking down whether or not there's any correlation of the issue to the dates of these builds.

Would removing/replacing these files be a potential solution? With the number of machines that potentially have this issue, a script/package to replace files would be much more palatable than reimaging all of them.

 

[NoelDP]

In theory it's possible to do it with a script - you'd need to change permissions on the Winsxs folder, insert the files and set permissions/ownership on them, and then reset the permissions on the winsxs folder.

There is a tool that could do it (mostly automatically) for you - SFCFix - if you don't mind passing executables around the network (as far as I know it's not particularly network-friendly, and has to run locally). If you Google that, you'll find its writer fairly easily.

 

[minh]

Thanks for the suggestion! We'll play around with SFCFix and see if it helps.

 

[minh]

After trying out SFCFix, we were able to fix the files that sfc /scannow couldn't initially. However, the IE11 installation still failed with a "Neutral package installation failed (exit code = 0x80092004 (2148081668))." error message. The Microsoft case I had open did produce a working solution which was the following command from an elevated command prompt:

FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*11.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /upfname /quiet /norestart"

I'll be trying this on more machines with the same error to see if this is a common resolution in our environment.

 

[NoelDP]

Ah - the forced-uninstall of IE11

That wouldn't affect the SFC results much - you'd still have a mass of mismatched/missing files?