System Updater won't update

Sorry - I must have lost track of the thread!

The CBS.log file cuts off in the middle of a lie of output from the last SFC scan, with a load of null characters.
The CheckSUR is apparently clear.

Looking back through the CBS.log file at previous scans.... all appear to have ended rather abruptly without the usual repair entries (were they perhaps /verifyonly scans??)

Outside the SFC scans, there is a major error set which causes concern....

Code:

2013-01-27 02:23:09, Info                  CSI    0000000a SMI Primitive Installer [done]
2013-01-27 02:23:10, Info                  CSI    00000016 ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=15 (0x0000000f)
2013-01-27 02:23:10, Info                  CSI    00000017 Creating NT transaction (seq 2), objectname [6]"(null)"
2013-01-27 02:23:10, Info                  CSI    00000018 Created NT transaction (seq 2) result 0x00000000, handle @0x2d4
2013-01-27 02:23:10, Error                 CSI    00000019 (F) STATUS_RM_NOT_ACTIVE #27363# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation|AllowTransactionalConflict|0x00000400), handle = {provider=NULL, handle=0}, da = (FILE_GENERIC_READ), oa = @0xf4e6c8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[39]"\SystemRoot\WinSxS\Temp\PendingRenames\"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xf4e750, as = (null), fa = (FILE_ATTRIBUTE_DIRECTORY), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0190005]
2013-01-27 02:23:10, Error                 CSI    0000001a@2013/1/26:15:23:10.301 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_RM_NOT_ACTIVE originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-01-27 02:23:10, Info                  CBS    Succesfully flushed NtfsLog.etl
2013-01-27 02:23:10, Info                  CBS    Succesfully added NtfsLog.etl to WER Report
2013-01-27 02:23:10, Error                 CSI    0000001b (F) STATUS_RM_NOT_ACTIVE #27362# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemDirectory(flags = (SharingViolationIsOk|TransactionalConflictIsOk|DeletePendingIsOk), da = (FILE_GENERIC_READ), dn = [ml:192{96},l:78{39}]"\SystemRoot\WinSxS\Temp\PendingRenames\", 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=0xd0190005]
2013-01-27 02:23:10, Info                  CSI    0000001c Error STATUS_RM_NOT_ACTIVE while executing operation MoveFile on [l:300{150}]"\SystemRoot\WinSxS\Temp\PendingRenames\7d96a10bd9fbcd010a000000cc157c09._0000000000000000.cdf-ms, \SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"

This appears to recur a number of times.

Please open an elevated Command Prompt window, please run the following commands, and post the results

DIR C:\Windows\Winsxs\Temp\PendingRenames
ICACLS C:\Windows\Winsxs\Temp\PendingRenames

Then run another SFC /SCANNOW and post the resulting CBS.log file.

It sounds like you may have a hardware problem with the hard drive - back up your data now, to external media.

(back tomorrow - it's bed-time!)

Have you backed up your data? - until you do that, it's all at risk, and I'm not prepared to do anything, since many of the fixes could involve hard work for the HD, ad break it completely.

First, check that the HD is actually usable!!
Find the make and model of your HD from Device Manager - then download the appropriate test utility from the HD manufacturer's site, and check it using that.

ONLY THEN, consider the next step - If the HD passes the test, then a clean install is worthwhile.