No Problems, Checking and Found Errors

AirPower4ever · 29 Oct 2015

I have I decided to run the sfc /scannow on my systems at home. They are Windows 7 Pro and Home 64-bit. But one of my systems came back with corrupted files; a Pro system.

Now the system does not exhibit any issues in the everyday work, but nonetheless errors. I tried looking at the log and I cannot make heads or tails of it other than there are some failures which I do not understand what they mean.

All the systems have the same Microsoft updates except this one system; this last October rounds had one missing while all my other systems had an update (which I will find out exactly which one).

Can someone see my log and see what's going on? I also attached a screenshot of the SFC error. Thanks

wben353 · 03 Nov 2015

Hi AirPowerForever,
Sorry 'bout the delayed response, too few helpers, too many requests.

I'll see if I can help resolve your issues.
Let me look over the cbs.log. I'll get back to you shortly.

wben353 · 03 Nov 2015

Please download and run System Update Readiness Tool
Run it double-click
Post CheckSUR.log which is in CBS folder, not CBS folder.

It may take some time to complete, depending on the problems it finds.

Results are more condensed, you can look at them & clearly view your issue(s).

I'm having issues with forum e-mail notifications, but I do try to monitor my subscriptions. If I can't resolve your issues, NoelDP most likely can, he's the expert.

AirPower4ever · 04 Nov 2015

Thanks wben353. So I did what you explained and the report is not that long. Looks like 6 problems total and 3 were fixed. I double checked on the system and the folders are there, but the actual file for each one is missing. I get that.

I went and read on the Microsoft site on how to copy files in to these folders and it was over my head. I do have an exact system which I compared the folders to and they have them. So if I need the files we have a source, but I just need to know how to copy them in to newly created folders by System Update Readiness Tool

Here is the attached. Thanks again for the help!

wben353 · 04 Nov 2015

Relevant part of log

Checking Component Store
(f) CSI Payload File Missing 0x00000000 System.Data.SqlXml.dll msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d
(f) CSI Store Directory Missing 0x00000002 winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d\ msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d
(fix) CSI Store Directory Missing CSI Store Directory Created C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d\
(f) CSI Payload File Missing 0x00000000 System.Data.SqlXml.dll msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9
(f) CSI Store Directory Missing 0x00000002 winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9\ msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9
(fix) CSI Store Directory Missing CSI Store Directory Created C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9\
(f) CSI Payload File Missing 0x00000000 gdi32.dll wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.22982_none_c235356aadaa1970
(f) CSI Store Directory Missing 0x00000002 winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.22982_none_c235356aadaa1970\ wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.22982_none_c235356aadaa1970
(fix) CSI Store Directory Missing CSI Store Directory Created C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.22982_none_c235356aadaa1970\

Summary:
Seconds executed: 992
Found 6 errors
Fixed 3 errors
CSI Payload File Missing Total count: 3
CSI Store Directory Missing Total count: 3
Fixed: CSI Store Directory Missing. Total count: 3

Do you have Win7x64 installation disc? If so, pop it in drive, run SFCFix.exe by Niemiro. Program will find missing files, folders, etc. and replace them. Tool is easier to use for all of us if the issue is in winsxs folder. Creates log, places log on desktop and opens it in notepad. By the way, all versions of win7 from Basic to Ultimate are on the disk. The ei.cfg file prohibits all but one from being available. If you rename it or delete it, it then become AIO all-in-one and all versions appear to choose. You can't repair install with a different version or fresh install a different version with your product key.

In the meantime, I'll look through my External HDD win7x64 Pro and see if I have the files.

wben353 · 04 Nov 2015

Good idea to have win7x64 disk, just in case you need to do Repair Install (excellent tutorial by Brink) which reinstalls windows and preserves all your installed programs, files, folders, music, pictures, etc. I do them all the time, piece of cake. You can download win7x64 pro ISO from Microsoft Download Center, you'll need your windows product key.

If you don't have your 25 character M$ product key handy, run attached VB Script. You can double-click or right-click choose>open, or if your interested in the code right-click choose> edit. All the program does is access the key stored in binary form (ones & zeros) in the registry, converts it to alphanumeric & displays it. Simple program.

Here's a free program to remove ei.cfg from ISO if you download the ISO (image file)

Here's link to sevenforms tutorial ei.cfg tutorial

wben353 · 04 Nov 2015

Don't have the 3 illusive files.

I mistakenly spoke on the SFCfix.exe, the 3 missing files are system files. I don't believe SFCFix.exe will find and replace those. Wouldn't hurt a thing to run it,or run it with windows DVD inserted.

You'll have to give NoelDP a shout. He's the expert in this area. Most likely he will have the 3 files, & definitely the knowledge to install them. Problem with system files is ownership. Microsoft's TrustedInstaller has ownership, and won't let you alter, copy, delete, system files, which is exactly what viruses try to do. You can take ownership of the files/folders manually, but I have not been able, even though I followed Brink's tutorial several times, &I tried running restore ownnership.reg by Vishal Gupta, to restore ownership to TrustedInstaller. Following the process, the window says TrustedInstaller has ownership, however, I can still open, alter, rename, delete file/folder. I don't get access denied popup. I haven't figured out how to do system files yet. I looking forward to reading a post by NoelDP to learn how it's done.

Both the SURT and SFCFix.exe tools automatically take and restore ownership. Great programs.

I'm in training on another forum for Windows Update issues, & haven't been there yet.

NoelDP · 05 Nov 2015

The SFC scan effectively crashed, with the following error...

Code:

2015-10-29 22:00:56, Error                 CSI    00000223 (F) STATUS_OBJECT_NAME_NOT_FOUND #5133934# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xf3ca60->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[99]"\??\C:\Windows\WinSxS\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xf3ca40, 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-29 22:00:56, Error                 CSI    00000224@2015/10/30:04:00:56.933 (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-29 22:00:57, Error                 CSI    00000225 (F) STATUS_OBJECT_NAME_NOT_FOUND #5133933# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2015-10-29 22:00:57, Error                 CSI    00000226 (F) STATUS_OBJECT_NAME_NOT_FOUND #5133932# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xf3d358->SIL_OBJECT_ATTRIBUTES {s:40; on:"msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d"; 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]

This agrees nicely with the CheckSUR results - I'll post a fix protocol for the errors when I can get to it (I have to run for the bus!)

AirPower4ever · 05 Nov 2015

Thanks everyone, helping me out here. I'll stay put till NoelDP gets back.

Again, thanks everyone

NoelDP · 06 Nov 2015

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

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

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