[WinServer2008] Messed up. It gives me 0x80070246 error for over a hundred updates.

[feizhou]

I have a Windows 2008 Server that gives me 0x80070246 error for over a hundred updates I have in the queue. Also, it appears that various files are not consistent. It reports having .net framework 2.0.50727.4253 installed but asp-net 2.0.50727.4257 but I appear to have 2.0.50727.7071 version of the mscorwks.dll inside a directory under winsxs directory while version .4243 mscorwks.dll is under Windows\Microsoft.Net\Frameworks\2.0.50727.

checksur reports no problems, even sfcfix.exe reports no corruption but sfc /scannow will not get pass 24% when it runs in a Windows Protection error.

CBS log entries have this:

2017-05-23 15:22:47, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
2017-05-23 15:22:57, Error CSI 00000054@2017/5/23:07:22:57.968 (F) d:\longhorn\base\lstring\lblob.cpp(2217): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffff
ffff)
[gle=0x80004005]
2017-05-23 15:24:57, Error CSI 00000055 (F) STATUS_ILLEGAL_CHARACTER #1147800# from CFileInstaller::CommitChanges(...)[gle=0xd0000161]
2017-05-23 15:24:57, Error CSI 00000056 (F) STATUS_ILLEGAL_CHARACTER #1147799# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd0000161]

Please advise.

 

[BrianDrab]

Re: Messed up Windows Server 2008

Welcome to Sysnative. Sorry for the delay. Are you still in need of assistance?

 

[feizhou]

Re: Messed up Windows Server 2008

I guess it is now a matter of interest/challenge not that its production use has been got rid of. It is no longer in real need of fixing. However, seeing whether a Windows server that somehow still manages to download pretty recent/the latest components but encounters problems in applying those due to previous issues (power cut, iscsi cut even during an update) can be fixed is a matter of interest. I am interested in learning how one identifies the illegal character that appears to be the blocker to the update process.

cheers,

Christopher

 

[BrianDrab]

Re: Messed up Windows Server 2008

OK, well let's take a look at your components hive. Usually these types of corruptions mean there is bad RAM in the machine.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.