[SOLVED] 24 Failed Windows Updates- Help!

D

dks328

Member
Joined
Sep 11, 2014
Posts
23
Windows update has 24 updates that are failing to run. I've ready many Win7 blogs trying to fix this without luck. Additionally, I am occasionally getting blue screens of death. Help!

Here are the error codes WU is returning:

Code 80070308
Code 9C59
Code 2

And here are the logs from running the SURT:

C:\Windows\Logs\CBS\CheckSUR.log


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-11 23:01

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 525
No errors detected
(w) Unable to read Event Log 0x0000001F System



C:\Windows\Logs\CBS\CheckSUR.persist.log


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-07-28 07:39

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 469
No errors detected
(w) Unable to read Event Log 0x0000001F System


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-07-28 07:52

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-07-28 21:39

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 500
No errors detected
(w) Unable to read Event Log 0x0000001F System


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-07-30 07:44

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 425
No errors detected
(w) Unable to read Event Log 0x0000001F System


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-09-11 23:01

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 525
No errors detected
(w) Unable to read Event Log 0x0000001F System



I also ran the SFCFix:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-11 23:14:25.073
Not using a script file.




AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-11 23:23:55.988
----------------------EOF-----------------------
 
Hello dks328 and welcome to Sysnative :)

SURT didn't identify any corrupt files here. Lets see if SFC picks up any.

SFC /SCANNOW

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button. Inside the search box type in CMD
  2. Right click on CMD => Choose Run as Administrator
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with the rest of the steps.

Convert CBS.log to CBS.txt

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button => Inside the search box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  2. Press Enter
  3. Once this has completed please upload CBS.txt to your next post


Please Note:: if the file is too big to upload to you next please post please upload via Dropbox or ge.tt



As for the BSOD please follow the steps Here and post the zip file to your text post.
 
I ran the SFC tool. After Verification 100% Complete it says:
Windows Resource Protection did not find any integrity violations.

I then copied and pasted the text you gave me into the Win search box. A pop up window opened for a second but no cbs.txt file was copied to my desktop. When I search the Windows search box for cbs.txt no files come up. I can see cbs.log but when I try to open it, it says access denied.
 
Hi all!
dks328, you can try that command (without cmd /c) from an elevated command prompt:
Code: 
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
To run an elevated command prompt (in case you don't know how to do it), you can use one of these three methods:
- click start, all programs, accessories, right-click the command prompt in the list and click run as administrator, click yes on the user account control window that should appear
- click start, type cmd in the searchbox, right-click the cmd in the list of results and click run as administrator, click yes on the user account control window that should appear
- click start, type cmd in the searchbox, press and keep pressed ctrl + shift Keys on your keyboard, then press enter, click yes on the user account control window that should appear
 
Thanks xilolee for posting that.

If the file is still not appearing on your desktop please do the following.

SFCFix Collect CBS
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFix.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles to our server.
  6. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

If all goes well, you should see that your logfiles have now been added to your thread.
 
Re: Logfile submission from dks328

Thanks, Go The Power. The log files have now been posted. Here is the data from SFCFix.txt:

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-14 18:24:16.381
Using .txt script file at C:\Users\Danielle\Desktop\SFCFixScript.txt [0]




Collect:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-14 18:25:40.513
----------------------EOF-----------------------
 
Thank you.

Code: 
Search "(f)" (5 hits in 1 file)
  E:\Downloads\Firefox\1590\CBS\CBS.log (5 hits)
	Line 144: 2014-09-14 17:57:47, Error                 CSI    00000017 (F) A previous transaction requested a reboot, so you cannot commit any transactions until you reboot.
	Line 146: 2014-09-14 17:57:47, Error                 CSI    00000018 (F) STATUS_REQUEST_OUT_OF_SEQUENCE #5163# from Windows::COM::CComponentStore::ApplyTransactionNow(...)[gle=0xd000042a]
	Line 147: 2014-09-14 17:57:47, Error                 CSI    00000019@2014/9/14:22:57:47.871 (F) d:\win7sp1_gdr\base\wcp\componentstore\com\store_transaction.cpp(1841): Error STATUS_REQUEST_OUT_OF_SEQUENCE originated in function Windows::COM::CComponentStore::ApplyTransactionNow expression: (null)
	Line 149: 2014-09-14 17:57:49, Error                 CSI    0000001a (F) HRESULT_FROM_WIN32(ERROR_REQUEST_OUT_OF_SEQUENCE) #5024# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Apply(...)[gle=0x80070308]
	Line 150: 2014-09-14 17:57:49, Error                 CSI    0000001b (F) HRESULT_FROM_WIN32(ERROR_REQUEST_OUT_OF_SEQUENCE) #4239# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 1, a = @0x843300, fn = @0x843700, fp = @0x843b00, disp = 0, op = 0)[gle=0x80070308]

These are the errors which are appearing. From what I can see the reason for this is that Windows thinks that there is another pending transaction that is running and it will not try commit another one until this one is ran.

Please navigate to C:\Windows\winsxs and copy any files with a similar name to pending.xml (e.g. pending.xml, pending.xml.bad, pending.xml_dfsadf78 etc.) to your folder on the Desktop [there may not be any, just if there are]. Add all these files into a zip file and attach to your next post.

SFCFix Collect COMPONENTS
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles to our server.
  6. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


If all goes well, you should see that your logfiles have now been added to your thread.
 
Re: Logfile submission from dks328

Thanks, Go The Power.

I checked C:\Windows\winsxs and there are no files in that directory that start with pending or have pending in them. There are many many directories there, and searching the whole winsxs location for "pending" files pulled up one file, pending.grl, which is attached. There are 2 directories in C:\Windows\winsxs\Temp called PendingRenames and PendingDeletes. Do you want the files from that location as well?
 

Attachments

I finally successfully completed the BSOD posting instructions. Had some trouble with my antivirus software (webroot) allowing the BSOD jcgriff2 file collection .exe to run. Anyway, here are the zipped files for the perfmon (html) and jcgriff2.
Thanks!
 

Attachments

Hi dks328

Did you follow the steps with SFCFix and SFCScript? The file doesn't appear to be upload to the server.

There are 2 directories in C:\Windows\winsxs\Temp called PendingRenames and PendingDeletes
Click to expand...

That should be ok for now, thanks.
 
Code: 
ceab797c 82a48aa8 00000000 f3dfffe4 00000000 [COLOR="#FF0000"]nt!MmAccessFault+0x104[/COLOR]
ceab797c 82aa6dda 00000000 f3dfffe4 00000000 [COLOR="#FF0000"]nt!KiTrap0E+0xdc[/COLOR]
ceab7af8 82aa7632 02f20002 03307fff 867f9768 [COLOR="#800080"]nt!MiDeleteVirtualAddresses+0x194[/COLOR]
ceab7bc8 82aa72e7 867f9768 86b36e10 87c2a898 [COLOR="#800080"]nt!MiRemoveMappedView+0x325[/COLOR]
ceab7bf0 82c4f506 87c2a898 00000000 00000000 [COLOR="#800080"]nt!MiRemoveVadAndView+0xe5[/COLOR]
ceab7c50 82c7e97a 867f9768 02f20000 00000000 [COLOR="#800080"]nt!MiUnmapViewOfSection+0x265[/COLOR]
ceab7c64 98374dd7 867f9768 02f20000 fdd922c0 [COLOR="#800080"]nt!MmUnmapViewOfSection+0x12[/COLOR]
ceab7c8c 98376f82 ceab7ce8 fe321728 ceab7cf8 [COLOR="#FF8C00"]win32k!SURFACE::Map+0xae[/COLOR]
ceab7cac 98374fb1 fdd5e318 ceab7ce8 ceab7d04 [COLOR="#FF8C00"]win32k!DEVLOCKOBJ::bMapTrgSurfaceView+0x30[/COLOR]
ceab7cc0 98375ce2 ceab7d04 c2010b4c 0025b888 [COLOR="#FF8C00"]win32k!DEVLOCKOBJ::bPrepareTrgDco+0x79[/COLOR]
ceab7cd8 983ca74c ffb8c748 00000001 00000000 [COLOR="#FF8C00"]win32k!DEVLOCKOBJ::bLock+0x332[/COLOR]
ceab7d20 82a458c6 c2010b4c 00000003 00000010 [COLOR="#FF8C00"]win32k!GreSetICMMode+0x3d[/COLOR]
ceab7d20 779270f4 c2010b4c 00000003 00000010 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0025b88c 00000000 00000000 00000000 00000000 0x779270f4

So to me this is either bad RAM or a driver referencing invalid memory.
If it is a driver I'd say it's the display driver as win32k.sys is the Windows Subsystem device driver, one of the most important functions is to create a display because it contains the windows manager, the graphics device interface and wrappers for DirectX the 3rd party device driver for your graphics card relies heavily on this.

Code: 
[COLOR="#FF0000"]igdkmd32[/COLOR]	90a23000	90f2c000	[COLOR="#FF0000"]Wed Sep 23 20:18:09 2009[/COLOR] (4aba7471)	004a45d4		igdkmd32.sys

And with all that in mind your Intel display driver is nearly 5 years old.
You need to update it.
 
Sorry, I didn't realize last night I needed to run those (SFCFix and Script) again. I just did it now.

Here's the code:

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-09-16 22:33:08.959
Using .txt script file at C:\Users\Danielle\Desktop\SFCFixScript.txt [0]




Collect:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-09-16 22:35:43.532
----------------------EOF-----------------------
 
Thanks Jared. I used the Windows Device Manager to check for driver updates to the display driver, and it said my driver was current. I didn't believe this so I checked the Intel website for driver updates to my display (Intel® GM965) and it also says the driver is current, even though it is 5 years old. Hard to believe. Any suggestions for other drivers to check? Or you think it's bad RAM?
 
Hello,

Windows updates is currently thinking that your machine has not been reboot and that there are pending transactions. Which is indicated by this
Code: 
[B]Line 144: 2014-09-14 17:57:47, Error                 CSI    00000017 (F) A previous transaction requested a reboot, so you cannot commit any transactions until you reboot.
	Line 146: 2014-09-14 17:57:47, Error                 CSI    00000018 (F) STATUS_REQUEST_OUT_OF_SEQUENCE #5163# from Windows::COM::CComponentStore::ApplyTransactionNow(...)[gle=0xd000042a][/B]

Now the COMPONENTS hive that you just uploaded for me currently has a registry key PendingRequired which indicates that WU is still pending something.

I should have a fix for you soon.

Alex
 
With a very outdated system such as yours things can become problematic a lot more easily, not only this but because drivers are no longer updated they get outdated and cause problems.
Now, you have the latest drivers but because it's so old and causing problems there isn't much else we can do.

I personally suggeest it's time for a new system which isn't always easy due to money/time contraints but it's the best option in the long run.

Code: 
1: kd> !machineid
No export machineid found
1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=1982]
BiosMajorRelease = 1
BiosMinorRelease = 3
FirmwareMajorRelease = 1
FirmwareMinorRelease = 3
BiosVendor = Dell Inc.
BiosVersion = A13
[COLOR="#FF0000"]BiosReleaseDate = 06/27/2008[/COLOR]
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1525                   
SystemFamily =  
BaseBoardManufacturer = Dell Inc.
BaseBoardProduct = 0U990C
BaseBoardVersion =

A BIOS update would be a great start as that's over 6 years old!

Dell Inspiron 1525 System BIOS, A17 Driver Details | Dell UK

On the dell webiste they don't actually support drivers for Windows 7 because the laptop is that old.
 
Hello,

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 the first command to enter is wmic logicaldisk get name. you will be given a similar output to:

Code: 
X:\Sources>wmic logicaldisk get name
Name
C:
D:
E:
X:

Now when you are in the RE the drive letters will often move around. start with the first letter that was provided in the list and enter in the following command (for this example we will use C:\ as it is the first one)

dir C:\
-This will display all the folders in the root drive of C

Can you see a folder called C:\Windows in list?
-If you can see C:\Windows then run the DISM command as DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

If you can not see the Windows folder move onto the next Drive letter that we obtained with wmic logicaldisk get name and type in dir <DRIVE LETTER> (replace <DRIVE LETTER> with the drive you would like to check), can you see the Windows Folder?
-If yes, enter in the following command DISM /Image:C:\ /Cleanup-Image /RevertPendingActions and changed the C to what ever Drive letter has the Windows folder

Its just a case of going through each drive letter that was produced from the first list until the Windows folder is found then run the DISM command on that drive.

Once that is done please try WU again
 
Jared- Thanks, I did the BIOS update.

Go The Power- Thanks also.
I was able to boot in Windows RE mode and follow your instructions. I saw all the drives and found the Windows folder in the D:.
I then ran your command DISM /Image:D:\ /Cleanup-Image/RevertPendingActions and I got this message:

Error: 87
The cleanup-image/revertpendingactions option is unknown.

It mentions I have access to a DISM log file. Would that be helpful?
Also the DISM version is 6.1.7601.17514.

Thanks! I feel like we're getting close!
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top