Solved Error code 80070002, sfc/ scannow command not working

[SteelFighting]

Hello everyone!
After my first failed attempt to post my problem (since I posted on another person's thread... sorry about that ), here I am again.
I have been having a "Configuring Windows Update 32% complete" and shortly afterwards the "Welcome" messages on startup and the "Preparing to configure Windows Update.." followed by "Shutting down" on shutdown for quite some time. Of course, Windows Update isn't working and the "sfc /scannow" command always comes up with the "There is a sytem repair pending which requires reboot to complete. Restart Windows and run sfc again". As you might have guessed already, restarting doesn't help and I am stuck on this endless circle.
So, as requested on the instructions, I have followed the required steps and here are my comments:
1) SURT installed succesfully and quite fast.
2) Commands "sfc /scannow" and "sfc/ verifyonly" come up with the message mentioned above so I moved on to option three, only to find a .txt file of 0 bytes and empty inside. So I guess this step didn't proceed as planned...
3) I have removed the older CBSPersist cab files and I will post them right afterwards, since the CBS.zip file including them is about 37MB.
Without further ado, please find attached the .zip file.
Thanks in advance for your time.

 

[SteelFighting]

Following with 2 out of 5 of the older CBSPersist cab files, compressed. 3 to go.

 

[SteelFighting]

Again, 2 out of 5 of the older CBSPersist cab files, compressed. I can't seem to get the 5th and last of the older files under 8MB, compressed. The original size is 24,2MB(!) and the compressed gets to 23,5MB. If you've got a problem without it, could you please give me an advice on how to get it under 8MB? Thank you.
P.S.: I used Zamzar online to convert the files from .cab to .zip since WinRar can't compress .cab files to .rar. At least, I don't know how...

 

[carwiz]

I didn't download the second pair. They shouldn't be that large. The first one is full of error messages so the other two probably are too.

Start Regedit and provide the values found in the following two locations. Do NOT change anything.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

 

[SteelFighting]

I'm afraid that I'm gonna disappoint you...
Those locations you mention don't exist, nor UpdateExeVolatile neither PendingFileRenameOperations.

 

[NoelDP]

The CAB files are already compressed - which is why they don't compress further.

 

[SteelFighting]

Oh, ok then. So, you won't be needing the 5th and final CAB file?

 

[NoelDP]

I don't think it's necessary - the current CBS log goes back to the beginning of May anyhow.

I'll have a good look at it later, after work O)

 

[SteelFighting]

Thank you very much for your time, I really appreciate it.
Looking forward to your reply

 

[NoelDP]

It looks to me as if perhaps either the machine crashed in the middle of an update, or the temporary files used in updating were deleted by mistake before they could properly be placed by the update process.

There are a number of errors such as this one...

2014-07-03 00:23:36, Info                  CBS    Appl: Evaluating package applicability for package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256, applicable state: Installed
2014-07-03 00:23:36, Info                  CSI    0000001f Transaction merge required, do-not-merge flag passed.
2014-07-03 00:23:36, Info                  CSI    [EMAIL="00000020@2014/7/2:21:23:36.617"]00000020@2014/7/2:21:23:36.617[/EMAIL] CSI Transaction @0x355c90 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [26]"TI5.30381627_3801869610:1/"
2014-07-03 00:23:36, Error                 CSI    00000021 (F) STATUS_OBJECT_NAME_NOT_FOUND #106013# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xd6c930->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[110]"\??\C:\windows\WinSxS\Temp\PendingRenames\e2b37a974317cf01040e00008814e40e.$$_syswow64_21ffbdd2a2dd92e0.cdf-ms"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xd6c910, 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]
2014-07-03 00:23:36, Error                 CSI    [EMAIL="00000022@2014/7/2:21:23:36.783"]00000022@2014/7/2:21:23:36.783[/EMAIL] (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]
2014-07-03 00:23:37, Error                 CSI    00000023 (F) STATUS_OBJECT_NAME_NOT_FOUND #106012# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (ReplaceIfExists|OpenForBackupIntent), op = [4]"Move", odir = @0x1e2b0f8, oname = [l:136{68}]"e2b37a974317cf01040e00008814e40e.$$_syswow64_21ffbdd2a2dd92e0.cdf-ms", ndir = @0x17e7718, nname = [l:70{35}]"$$_syswow64_21ffbdd2a2dd92e0.cdf-ms", disp = Unmapped disposition: 0)
[gle=0xd0000034]
2014-07-03 00:23:37, Error                 CSI    00000024 (F) STATUS_OBJECT_NAME_NOT_FOUND #105975# from RtlRunPrimitiveOperationsFromCallbacksAgainstSil(...)[gle=0xd0000034]
2014-07-03 00:23:37, Error                 CSI    00000025 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #105570# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80070002]
2014-07-03 00:23:37, Error                 CSI    00000026 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #105568# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_Analyze(Flags = 1, riid = {f4d9decb-0250-4ad4-9500-85c7f2f281ec}, ppUnk = NULL, disp = 0)[gle=0x80070002]
2014-07-03 00:23:37, Info                  CBS    Failed to get transaction analysis. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-03 00:23:37, Info                  CBS    Failed to get inventory. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-03 00:23:37, Info                  CSI    [EMAIL="00000027@2014/7/2:21:23:37.287"]00000027@2014/7/2:21:23:37.287[/EMAIL] CSI Transaction @0x355c90 destroyed

Unfortunately, this appears to be in an update which is not available for download, and cannot be uninstalled.
I also don't know enough to be able to force an uninstall with tis type of error.

My recommendation would therefore be a repair install of Windows. - It's not as scary as it either looks or sounds!

Look here for instructions... http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[SteelFighting]

Aha... I see...
But I have already been there and there was no light at the end of the tunnel. As a matter of fact, this is the message I got when I tried to repair install:

"The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.

Windows needs to be restarted so necessary changes to system files can be made before continuing.


Upgrading Windows will affect the following features:

Any language packs that are installed will not be available after the upgrade. You’ll need to reinstall your language packs after the upgrade.


Upgrading Windows will affect the following devices and/or programs:

These devices might not work properly after the upgrade. Before upgrading, we recommend updating the drivers for these devices. Cancel the upgrade, open Control Panel and search for "update device drivers", or go to the device manufacturer's website to search for updated drivers.
Storage controllers: AUAVXLG3 IDE Controller
Network adapters: 300Mbps Wireless USB Adapter"

The rest don't matter, the first message (marked with a red X) is the one that lefts me with one and only option, to "close" the wizard.

 

[NoelDP]

I was afraid you'd get that message

I'm going to see if I can get someone to assist - don't run away!

 

[SteelFighting]

Okay! Not a chance of leaving

 

[tom982]

Hi SteelFighting,

Noel has asked me to take a look at this

Can you zip up and attach this file to your next post please?

C:\Windows\winsxs\Pending.xml

Tom

 

[NoelDP]

(Thanks, Tom!)

 

[SteelFighting]

There you go... I have also attached a screenshot of some other "pending" issues, I don't know if they could be of any help (judging just from their name) but I' ve uploaded it anyway...

 

[tom982]

Thanks, but pending.xml is all I need for now There's an awful lot of operations that are pended so we'll have a lot of problems if we skip just these. Let's try reverting them:

Can you boot into the recovery environment, and launch command prompt please: How to use the Windows 7 System Recovery Environment Command Prompt

When command prompt is launched, type in the following command and press enter:

DISM /image:C:\ /cleanup-image /revertpendingactions

Then reboot your computer, booting into Windows normally. Try to update and if it fails again, upload your CBS log and pending.xml please!

Tom

 

[SteelFighting]

I am very happy to announce that I can finally get Windows update!!! But not without any surprises... So, for the record:

I followed your instructions as prompted and the following happened:
1) After entering command prompt through the recovery environment and giving the command, I got a message telling me that the size of scratch directory is insufficient, etc etc and this:
"Error 2

An error occurred reverting the pending actions from the image. For more information, review the log file under Windows\Logs\DISM\dism.log"
You can guess how disappointed I was. But then, after rebooting, miracles happened!
2) No more
"Configuring Windows update
32% complete".
Instead I got:
"Failure configuring Windows updates
Reverting changes..."
and after a while: "Cleaning up" and "Welcome"!
3) I tried to check for updates and it was taking a really long time. I thought that I was on to something good but...
alas... I got error code 80024.... (can't remember exactly the numbers) and I was thinking I should change the title of my thread to error code 80024...something.
Disappointed as I was, I rebooted one more time and thought I should check one last time for updates.
And then all went perfect!
Except for 1 optional update, a driver for my processor-based GPU Intel HD 4000.
But I'll see what I can do later about that.
Thank you so much for your time and advice all!

FYI, CBS log up but I looked for a pending.xml file and there is none anymore! I hope that's a good thing...

 

[SteelFighting]

Just one more happy note: sfc /scannow command just worked fine with a 100% verification and without any integrity violations. Should I mark this thread as solved now?

 

[NoelDP]

So long as you're happy that your original question has been answered.... yes, please do mark the thread as solved!

Tom - thanks for the quick course in solving this error-type! I have always until now avoided anything to do with DISM, on the basis that I may do more harm than good - maybe I won't be so reticent next time it's needed!

StreetFighting - well done for following the instructions so well!.... and good luck for the future.