"Windows Module Installer has stopped working" message constantly

There's a fairly critical error in the last CheckSUR that ran -

Code:

(f) CSI Payload File Corrupt 0x00000000 cmiv2.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f

this file is central to the servicing capabilities of Windows, so the fact it's missing may be causing all your other problems.

The CBS log however is more interesting.
SInce early November, almost the only activity recorded has been repeated installations of the same software at boot.

Code:

2013-11-17 10:28:44, Info                  CSI    00000006 IAdvancedInstallerAwareStore_ResolvePendingTransactions call 1 loaded 8 pending advanced installer operations
2013-11-17 10:28:44, Info                  CSI    00000007 Begin executing advanced installer phase 8 index 0 (sequence 0)
    Old component: [l:0]""
    New component: [l:0]""
    Install mode: uninstall
    Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9}
    Installer name: [25]"RegistryKey SD Applicator"
2013-11-17 10:28:44, Info                  CSI    00000008 End executing advanced installer (sequence 0)
    Completion status: S_OK

One or two people have reported uninstalling .NET 4 for a while, then reinstalling it solves this problem - it's certainly worth trying.

Uninstall it from the Programs listing reboot, then run the cleanup tool from here...
.NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs

Reboot again - TWICE

The try running SFC /SCANNOW and CheckSUR again

post the new CBS folder, and try reinstalling .NET 4.5.1 (the upgrade to .NET 4)

OK - looks like we'll have to try and fix the known file error first, and then see if that gives us more data...


I've uploaded a file - clraa.zip - to my SkyDrive at Noel's SkyDrive
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:\clraa
hit the enter key - if you get a 'Not Found' error try
DIR D:\clraa
or
DIR E:\clraa

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

XCOPY <drive>:\clraa <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 ,
and try running CheckSUR again

If CheckSUR gets into the proper checking phase again, then post the new CheckSUR.log file

Not quire yet :)
The CheckSUR log is clear at least - but there are a small number of errors still present in the completed SFC scan...

Code:

 Line 450987: 2013-12-16 00:12:16, Info                  CSI    00000369 [SR] Repairing 4 components
 Line 450988: 2013-12-16 00:12:16, Info                  CSI    0000036a [SR] Beginning Verify and Repair transaction
 Line 450991: 2013-12-16 00:12:16, Info                  CSI    0000036c [SR] Cannot repair member file [l:16{8}]"kaiu.ttf" of Microsoft-Windows-Font-TrueType-DFKaiSB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 450994: 2013-12-16 00:12:16, Info                  CSI    0000036e [SR] Cannot repair member file [l:20{10}]"DE-wp2.jpg" of Microsoft-Windows-MarketTheme-DE-Component, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 450997: 2013-12-16 00:12:16, Info                  CSI    00000370 [SR] Cannot repair member file [l:64{32}]"Windows User Account Control.wav" of Microsoft-Windows-Shell-SoundThemes-Characters, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 451001: 2013-12-16 00:12:16, Info                  CSI    00000372 [SR] Cannot repair member file [l:42{21}]"System.Web.Mobile.dll" of System.Web.Mobile, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol for them later.

I've uploaded a file - clrab.zip - to my SkyDrive at Noel's SkyDrive
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:\clrab
hit the enter key - if you get a 'Not Found' error try
DIR D:\clrab
or
DIR E:\clrab

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

XCOPY <drive>:\clrab <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