Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows update - did it hang?


  • Please log in to reply
12 replies to this topic

#1 Mithos

Mithos

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 20 November 2011 - 07:28 AM

Is there documentation for windows update? Sometimes it looks like it's hanged, but it's difficult to tell.
My Windows Update program (the thing you run when actually in the OS) is trying to install Win7 SP1, but it hangs at 75%.
If I let it complete, it says it was successful; but upon rebooting to finish the update, it says it failed.
How can I find out why it failed?
Sometimes it sits there Configuring the update or whatever, step M of N, and then fails after a few hours.
The error code is er...forgot what it was, but googling for it suggests that the Windows Update Readiness Tool will fix it (which it didn't).

Are there any logs that might shed light on the problem? If so, what kind of things am I looking for in the logs? Or should I just post a file here?

BC AdBot (Login to Remove)

 


#2 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 20 November 2011 - 07:57 AM

Any time an error occurs windows should generate an error in the event log. You can access the event log by typing eventvwr.exe into the search field located on the start menu. Once you've opened event log you'll notice several categories. Click the small arrow to the left of Windows Logs. Application log will show error's related to any application issue's. System Log will show error's related to any error's dealing with system components.

Once you've found an error with a red exclamation point the entry should give you more info about any potential problems.

Most Windows Update errors have a code associated with them such as.. 0x800B0003. Using your favorite search engine should give you details about what issue's there may be and how to resolve them.

Edited by Lefty3120, 20 November 2011 - 07:58 AM.


#3 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 20 November 2011 - 08:13 AM

Hi,
The code is 800F0826, and I've tried about five fixes from googling it.
None of them seem to work.
I have a feeling that a funny permission is set on one of the files (possibly an ATI-related driver) the updater needs to update. This installation of Windows is less than a day old though, and I haven't installd a great deal...
I'm wondering if there's a windows update log might tell me which step went wrong.
I'll take a look at the event viewer, but I think that might be too in depth, and presumably there's a lot of garbage in there that isn't related to the update process.

thanks

Just looked at the event viewer.

There are some items in there like:
The Windows Modules Installer service terminated with the following error:
The system cannot find the file specified.

Obviously it's not helpful enough to tell me which file is missing, though. A specific Windows update log might, however.

The layers of abstraction are infuriating...I wish there was an option to patch by downloading dlls appropriate to your system and pasting them in manually :(

The day that my games work on Ubuntu is the day I nuke my Windows partition, though I suspect that this might take longer than the human race will survive to happen.

Edited by Mithos, 20 November 2011 - 08:28 AM.


#4 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 20 November 2011 - 08:47 AM

First thing to do is an sfc scan.

Please follow these instructions..

1. Open an elevated command prompt. To do this, click Start, Type CMD into the search box, Right click CMD and select Run as Administrator.

2. Type the following command, and then press ENTER: sfc /scannow

**The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

To determine which files could not be repaired by the System File Checker tool, follow these steps:

3. Open an elevated command prompt. Copy the following command, and then press ENTER:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

**Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool. Type sfcdetails.txt in Search programs and files and press Enter.

Paste attach the sfcdetails.txt to your next post.

Edited by Lefty3120, 20 November 2011 - 02:23 PM.


#5 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 20 November 2011 - 11:16 AM

The list is massive, so I've attached the output file (results.txt) instead of pasting it in line.
I think it's the same list as reported by the Update Readiness tool.
Should I try and copy the files from a Windows install disc?

I'm fairly adept with Perl...I can probably make a script to do it if they're all in predictable folders, if you think that would resolve the issue.

thanks for the help btw, I appreciate it all.


Or is there a repair/re-copy missing dlls option in the windows disk that might help?

Edited by Mithos, 20 November 2011 - 11:21 AM.


#6 Nimblewill

Nimblewill

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 20 November 2011 - 11:46 AM

You might try the Microsoft Fix it Solution Center. Here is the link for Windows update problems.

#7 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 21 November 2011 - 02:53 PM

What does the fixit tool do? I seem to be missing the following two files:

(f) CSI Payload File Missing 0x00000000 jscript9.dll wow64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16437_none_01ce02fafe2b8fae
(f) CSI Payload File Corrupt 0x00000000 poqexec.exe amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f

Anyone have any ideas?

edit: Or could someone get me a copy of these files? (Amd x64)
They must have been nuked during a failed restore/update or something.

Edited by Mithos, 21 November 2011 - 03:26 PM.


#8 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 21 November 2011 - 03:27 PM

Please download.. Systemlook x64

Open the program and type the following...

:filefind
jscript9.dll
poqexec.exe


post the log when complete.

#9 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 21 November 2011 - 03:35 PM

Allow me to thank you again. Thanks :)
[edit: The files in my documents are extracted from a Windows install dvd]
Here's the log (SystemLook.txt)

SystemLook 30.07.11 by jpshortstuff
Log created at 20:31 on 21/11/2011 by jeremy
Administrator - Elevation successful

========== filefind ==========

Searching for "jscript9.dll"
C:\Windows\System32\jscript9.dll --a---- 2309120 bytes [02:45 19/11/2011] [02:45 19/11/2011] B18D9AF3DD154628415E9987799BE2D4
C:\Windows\SysWOW64\jscript9.dll --a---- 1798144 bytes [02:45 19/11/2011] [02:45 19/11/2011] 3BE120BA72475250FA6BFCB3BEE6A7F7
C:\Windows\winsxs\amd64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16437_none_f77958a8c9cacdb3\jscript9.dll --a---- 2309120 bytes [02:45 19/11/2011] [02:45 19/11/2011] B18D9AF3DD154628415E9987799BE2D4

Searching for "poqexec.exe"
C:\Users\jeremy\Documents\DELETEME\TEST\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\poqexec.exe --a---- 142336 bytes [02:55 14/07/2009] [02:55 14/07/2009] 09EB33F92B60B4B1076068987A5E3B55
C:\Users\jeremy\Documents\DELETEME\TEST\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\poqexec.exe --a---- 123904 bytes [02:43 14/07/2009] [02:43 14/07/2009] D7410A8FB32BB7C725F6D60F46FD4DC7
C:\Windows\System32\poqexec.exe --a---- 142336 bytes [01:18 19/11/2011] [06:58 09/04/2011] F28D6538F76DC6ECFABF6176DBDD2664
C:\Windows\SysWOW64\poqexec.exe --a---- 123904 bytes [01:18 19/11/2011] [05:56 09/04/2011] 20104EA66332D24D7C65BBB087C56737
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\poqexec.exe --a---- 142336 bytes [02:55 14/07/2009] [02:55 14/07/2009] 09EB33F92B60B4B1076068987A5E3B55
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\poqexec.exe --a---- 142336 bytes [02:55 14/07/2009] [02:55 14/07/2009] 09EB33F92B60B4B1076068987A5E3B55
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\poqexec.exe --a---- 142336 bytes [00:33 21/11/2011] [02:55 14/07/2009] 09EB33F92B60B4B1076068987A5E3B55
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\poqexec.exe --a---- 123904 bytes [02:43 14/07/2009] [02:43 14/07/2009] D7410A8FB32BB7C725F6D60F46FD4DC7
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f\poqexec.exe --a---- 123904 bytes [02:43 14/07/2009] [02:43 14/07/2009] D7410A8FB32BB7C725F6D60F46FD4DC7
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\poqexec.exe --a---- 123904 bytes [01:18 19/11/2011] [05:56 09/04/2011] 20104EA66332D24D7C65BBB087C56737

-= EOF =-

Edited by Mithos, 21 November 2011 - 03:41 PM.


#10 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 21 November 2011 - 03:49 PM

What does the fixit tool do? I seem to be missing the following two files:

(f) CSI Payload File Missing 0x00000000 jscript9.dll wow64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16437_none_01ce02fafe2b8fae
(f) CSI Payload File Corrupt 0x00000000 poqexec.exe amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f

Anyone have any ideas?

edit: Or could someone get me a copy of these files? (Amd x64)
They must have been nuked during a failed restore/update or something.


Can you repost the sfcdetails log.

#11 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 21 November 2011 - 03:56 PM

Looks like my files are fairly broken.
This is a recent scan.
I tried replacing some files from the Windows install dvd.

If you think I should just reformat (again) I can do that instead lol.
But I wanted to give a last ditch attempt at replacing these files first.

Or run an in-place update/repair install thing?

thanks

[edit: That log with just two files was from the System Update Readiness output]

Attached Files

  • Attached File  log.log   221.08KB   1 downloads

Edited by Mithos, 21 November 2011 - 03:57 PM.


#12 Lefty3120

Lefty3120

  • Members
  • 112 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 21 November 2011 - 04:55 PM

Looking threw the log makes me think a fresh install would be good.

#13 Mithos

Mithos
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:32 AM

Posted 21 November 2011 - 09:33 PM

Copying the Poq thing from another (identical of course) box seemed to work.
I wrote a perl script to copy the other files from the Win7 setup thing, since they existed there quite handily.

Service pack now installed.
Thanks for your help :D

Silly Windows.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users