Windows Update will not run ... says service is not running but it is

[sgreenblatt]

Looks like this is a not too uncommon problem. I tried the basics (like making sure the services are running, etc.) but nothing work.

NoelDP seems to have a lot of great tips ... but I'm not having any luck.

I tried to run the SURT ... but it fails with error code 0xc800033ea and I ran Scannow 3 times but it was unable to fix files all 3 times.

I don't have any screenshots to share ... and I tried to attach the zip of my CBS logs but it's too large. The logs are over 4GB ... and zipped they're in the hundreds of MB.

NoelDP ... if you're still out there providing help ... I could use some!!

Thanks,
Steve

 

[wben353]

Please follow Windows Update Posting Instructions. If you don't provide the requested logs, how are we supposed to help you? It appears you are trying to upload the CBSpersist.log. CBS.log is not that large. If I cannot help you NoelDP is the go to guy. He is very busy and may take a while to respond.

 

[sgreenblatt]

CBS.log now attached

The directions on how to post indicate that you need the entire directory. I've attached just the CBS.log now.

Thanks for the the help.

Steve

 

[sgreenblatt]

Any help would be appreciated! Thanks!

Steve

 

[wben353]

Try running SFCfix by Niemero SFCfix.exe Save to desktop and run it. Post SFCfix.txt when it completes. It may take a while to finish. Do you have a Win7 Disk?

 

[NoelDP]

You appear to have a massive number of POQs in the SFC scan results - this is usually caused by having all MUI Language packs installed, resulting in the system 'clogging up' - what's worrying is that your system shouldn't have any MUI Packs installed at all, since it's Home Premium (according to your specs, at least?)

You should uninstall all MUI language packs - and get back down to the basic one that came with the system.

Once you've done that, run SFC /SCANNOW again, and post back with a new CBS.log file.

If you have no MUI packs installed, then I suspect that you have a major problem
Both SFC scans in that log terminated abnormally - with the following error...

2015-10-08 22:20:08, Info                  CSI    00000a6c [SR] Beginning Verify and Repair transaction
2015-10-08 22:20:08, Error                 CSI    00000a6d (F) STATUS_OBJECT_NAME_NOT_FOUND #21666437# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x26ecc70->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[98]"\??\C:\Windows\WinSxS\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x26ecc50, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2015-10-08 22:20:08, Error                 CSI    00000a6e@2015/10/9:02:20:08.429 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2015-10-08 22:22:48, Error                 CSI    00000a6f (F) STATUS_OBJECT_NAME_NOT_FOUND #21666436# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2015-10-08 22:22:48, Error                 CSI    00000a70 (F) STATUS_OBJECT_NAME_NOT_FOUND #21666435# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x26ed568->SIL_OBJECT_ATTRIBUTES {s:40; on:"x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
[gle=0xd0000034]

The error you quote for the CheckSUR failure is not one that I or Google have ever seen before - and has an extra/redundant character in it somewhere. Please try CheckSUR again, and post the error code you get this time.

 

[sgreenblatt]

Results of SFCFix

NoelDp ... thanks for your reply. I'll look into the MUI packs shortly.

In the meantime I was able to get the results from the SFCFix that I ran. I have pasted them below:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-18 15:02:33.728
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1.



FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\utc.app.json.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json has been successfully repaired from C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.23040_none_fe7de82236c5fac8\telemetry.ASM-WindowsDefault.json.


CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-directx-direct3d10.1_31bf3856ad364e35_7.1.7601.16492_none_9f6794084b5ae01c\d3d10_1core.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.1.7601.17577_none_4fcc6da642d93cf5\esent.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.1.7601.17514_none_ce2d22115368db7a\Faultrep.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.1.7601.17514_none_ce2d22115368db7a\WerFault.exe
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-p..randprintui-printui_31bf3856ad364e35_6.1.7601.17514_none_3a5b55d98a9a0bfd\printui.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-errorreportingcore_31bf3856ad364e35_6.1.7601.18381_none_222f511b6461ebd9\wer.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1\ATL80.dll


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 13
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 3
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2015-10-19 09:10:31.525
----------------------EOF-----------------------

 

[sgreenblatt]

No MUI Language Packs are installed

@NoelDP ... I just checked and there are no additional languages installed. Sounds like a "major problem"

All of my data, etc is backed up on this machine and I only use this laptop when I travel (I have a desktop for primary use). The laptop didn't come with a Windows disk (probably bc it doesn't even have a CD drive). I'm not sure how I could get back to factory setup ... but I guess that might be a possibility.

Steve

 

[NoelDP]

There should be a Recovery partition with associated software installed - check the manual for details.

The SFCFix results are about as expected - the FIXED files didn't actually need to be fixed at all, since once the updates are all in, they would be properly controlled (it's a coding bug by MS rather than a real problem)

It may simply be that the errors you do have are confusing matters for SFC - I'll post a fix protocol for the ones found later and we'll see what happens.

 

[NoelDP]

I've uploaded a file - SFCFix.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and drag the SFCFix.zip file over onto the SFCFix.exe file you downloaded earlier - this should force SFCFix to run the file

It will create a new log file - please upload that.
*
Now run SFC /SCANNOW again (it may take a while) and post the new CBS.log file

 

[sgreenblatt]

New results files

Sorry for the delay. Here are the new files as requested.

I found out how to factory reset my laptop (there's a button for this express purpose) ... so that's an option as well (although not a great one).

Thanks again!!

 

[NoelDP]

SFCFix looks like it did the job, at least!
The SFC scan reveals that it fixed two errors, but failed on another two...

	Line 23432: 2015-10-25 10:52:36, Info                  CSI    0000036d [SR] Repairing 4 components
	Line 23433: 2015-10-25 10:52:36, Info                  CSI    0000036e [SR] Beginning Verify and Repair transaction
	Line 23436: 2015-10-25 10:52:36, Info                  CSI    00000370 [SR] Cannot repair member file [l:24{12}]"ntfs.sys.mui" of Microsoft-Windows-NTFS.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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 23437: 2015-10-25 10:52:36, Info                  CSI    00000371 [SR] Cannot verify component files for Microsoft.VC90.MFCLOC, Version = 9.0.30729.4148, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

...and we're down to a much more reasonable 148 POQs, and SFC terminated properly, as well!

Please try running the SURT tool again, and post the new CheckSUR.log file with luck it'll complete this time and we can see what other damage there is left to repair.

 

[sgreenblatt]

CheckSUR.log results

Well it ran this time! I've attached the log. Let me know what else you think could help.

Steve

 

[NoelDP]

Major advance!

OK - this is the important stuff from the log...

Checking Component Store
(f)	CSI Catalog Missing	0x00000002	51c55792a77ddffa2c36fc5cc92cf7e67263b0004bb0b4970f3a00524f5bdbec.cat	policy.8.0...ft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_516e2e610f48bda6	Missing catalog or invalid CatalogThumprint
(fix)	CSI Catalog Missing	CSI File Replaced	Deleted CatalogThumbprint
(f)	CSI Manifest Missing	0x00000002	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_516e2e610f48bda6.manifest	x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_516e2e610f48bda6	
(f)	CSI Payload File Missing	0x00000000	msvcp80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d	
(f)	CSI Payload File Missing	0x00000000	msvcm80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d	
(f)	CSI Manifest Missing	0x00000002	x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9.manifest	x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9	
(f)	CSI Catalog Missing	0x00000002	813c74c7711815cf656f96f0ce5d9e57a31c3c4f98b607c8425cdbe8d5ccb436.cat	microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_d1c738ec43578ea1	Missing catalog or invalid CatalogThumprint
(fix)	CSI Catalog Missing	CSI File Replaced	Deleted CatalogThumbprint

Summary:
Seconds executed: 1081
 Found 6 errors
 Fixed 2 errors
  CSI Manifest Missing Total count: 2
  CSI Catalog Missing Total count: 2
  Fixed: CSI Catalog Missing.  Total count: 2
  CSI Payload File Missing Total count: 2

Unavailable repair files:
	winsxs\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_516e2e610f48bda6.manifest
	winsxs\manifests\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9.manifest

I'll post a fix for the missing manifests files later.

 

[NoelDP]

Here we go...
I've uploaded a file - sgbab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sgbab in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[sgreenblatt]

It took a while to figure out how copy the manifest files (I had to change ownership on the directory where the manifest files were located) and then it took a while for the CheckSUR to run ... but it's looking better (I think). Here are the results.

Thanks again!
Steve

 

[NoelDP]

Yup - CheckSUR has done the necessary job, leaving us with only these errors...

Checking Component Store
(f)	CSI Payload File Missing	0x00000000	msvcp80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d	
(f)	CSI Payload File Missing	0x00000000	msvcm80.dll	x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d	
(f)	CSI Payload File Missing	0x00000000	MFC90CHS.DLL	x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.4148_none_4973eb1d754a9dc9

Now please run another SFC /SCANNOW and post the new CBS.log - and we'll see what else needs fixing at the same time.

 

[sgreenblatt]

Definitely getting closer

In order to run SFC again i had to reboot my laptop. Apparently some updates had been downloaded (which hasn't happened in a long time).

I then ran SFC and zipped the results. Unfortunately the file is too big to attach (even zipped). I've put it in Dropbox here: https://www.dropbox.com/s/6nqfbiqr1k6qtft/CBS.zip?dl=0

Thanks (yet) again.

Steve

 

[NoelDP]

SFC found the following problems...

	Line 3668: 2015-10-29 20:50:24, Info                  CSI    00000353 [SR] Repairing 2 components
	Line 3669: 2015-10-29 20:50:24, Info                  CSI    00000354 [SR] Beginning Verify and Repair transaction
	Line 3672: 2015-10-29 20:50:24, Info                  CSI    00000356 [SR] Cannot repair member file [l:24{12}]"ntfs.sys.mui" of Microsoft-Windows-NTFS.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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 3673: 2015-10-29 20:50:24, Info                  CSI    00000357 [SR] Cannot repair member file [l:24{12}]"MFC90CHS.DLL" of Microsoft.VC90.MFCLOC, Version = 9.0.30729.4148, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing

I'll post a fix protocol for all the files as soon as I can find the time!

 

[NoelDP]

I've uploaded a file - sgbac.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:\sgbac
hit the enter key - if you get a 'Not Found' error try
DIR D:\sgbac
or
DIR E:\sgbac

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

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