Windows Server 2008 R2 update and SFC problem

Here's the detailed error message...

Code:

2015-04-19 12:15:56, Error                 CSI    000001a7 (F) STATUS_OBJECT_NAME_NOT_FOUND #3681212# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xddc630->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[105]"\??\C:\Windows\WinSxS\amd64_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_e7822eb53dae3c95"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xddc610, 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-04-19 12:15:56, Error                 CSI    000001a8@2015/4/19:07:45:56.652 (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-04-19 12:15:57, Error                 CSI    000001a9 (F) STATUS_OBJECT_NAME_NOT_FOUND #3681211# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2015-04-19 12:15:57, Error                 CSI    000001aa (F) STATUS_OBJECT_NAME_NOT_FOUND #3681210# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xddcf28->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_e7822eb53dae3c95"; 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]

From what little I know of 0xd0000034 errors, they tend to be mostly caused by disk corruption.


Please run a full CHKDSK and SFC scan....
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.
You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) - then run the SFC.

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
SFC /SCANNOW
and hit the Enter key
Wait for the scan to finish - make a note of any error messages - and then reboot.

Upload the CBS.log file (compressed, please!) to your reply

Hi noel
I have checked the disks.
There were no problems.
funny the cbs log gets to 120MB after system restart. I thinks that is due to the computer will to install the windows updates. (as it seems from the cbs.log)
I can't attach the file here.

Reagrds

Good - CheckSUR was able to complete this time, and ggave some sensible results...

Code:

 Line 2982: 2015-04-20 00:47:41, Info                  CSI    00000557 [SR] Repairing 1 components
 Line 2983: 2015-04-20 00:47:41, Info                  CSI    00000558 [SR] Beginning Verify and Repair transaction
 Line 2984: 2015-04-20 00:47:41, Info                  CSI    00000559 [SR] Cannot repair member file [l:20{10}]"mfc90d.dll" of Microsoft.VC90.DebugMFC, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 2985: 2015-04-20 00:47:41, Info                  CSI    0000055a [SR] Cannot repair member file [l:22{11}]"mfcm90d.dll" of Microsoft.VC90.DebugMFC, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 2986: 2015-04-20 00:47:41, Info                  CSI    0000055b [SR] Cannot repair member file [l:22{11}]"mfc90ud.dll" of Microsoft.VC90.DebugMFC, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 2987: 2015-04-20 00:47:41, Info                  CSI    0000055c [SR] Cannot repair member file [l:24{12}]"mfcm90ud.dll" of Microsoft.VC90.DebugMFC, Version = 9.0.30729.6161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 2992: 2015-04-20 00:47:41, Info                  CSI    0000055e [SR] Repair complete
 Line 2993: 2015-04-20 00:47:41, Info                  CSI    0000055f [SR] Committing transaction

I'll post a fix protocol later

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



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



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

Ah - dual boot with Linux can cause problems.
I'll see if I can find someone who knows more about Linux than me (not difficult!) to advise on the best way to set things up - or you may have continuing problems.

nimanouri said:

I had a dual boot Linux RHEL and Server 2008 R2.
............
............
I have changed the boot sequence of my hard disks and moved windows HDD to higher priority in BIOS.
Then removed the RHEL HDD and boot in the windows.

Dual booting Windows and Linux can cause issues, seriously. Specially the dual boot is configured using GRUB. It is said very often that GRUB can damage windows beyond repair.

It seems from your post that Windows and Linux are set up in different HDDs. Very nice. In that case you dont need a dual boot. Break the dual booting system: Dual Boot - Delete a OS
Use the Boot Menu key to select the drive to boot from.

(Thanks, Arc!)