Windows 7 64 bit unable to update because "service not started"

[HAPPIKANGAROO]

Windows 7 64 bit unable to update because "service not started"

Just like it says on the tin. The error message is "Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer. I've gone through several other posts and tried the fixes suggested there but the problem still persists. I have also recently restored my computer to factory settings. I've checked if the services were running and all of the required ones i've found are both started and set to automatic start.

 

[NoelDP]

Open an Elevated Command Prompt window, and run teh following commands

NET Start BFE
NET START BITS
NET START WUAUSERV
NET START TRUSTEDINSTALLER

post the results
Then

Open Windows Update
Click on Change Settings
Select 'Never Update...'
Click OK
exit Windows Update
Now open Windows update again
Click on Change Settings
Select 'Update automatically'
Click OK
exit Windows Update
Open Windows Update, and do a manual Check for Updates.


also follow the instructions here, and post the results.
http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

 

[HAPPIKANGAROO]

I've done the command prompt commands and those have had no effect.

The making windows never update and then update automatically resulted in my windows updater refreshing the window every time i click the button.

When I try to run SURT, it just gives me the error code "Installer encountered an error:0xc8000247"

I'll attach a screenshot of the sfc /scannow.

Windows update does not list any error codes besides the fact that it cannot start because of the service not running.

I've attached the CBS log.

 

[NoelDP]

The commands were not designed to 'have an effect' - they were designed to produce information, which is why I asked for teh results.

I'll review the CBS.log file later.

 

[HAPPIKANGAROO]

Oh. Alright. Thanks for your help.

 

[NoelDP]

I've never seen a system with so many POQ entries - 500+ - the normal number is around 200-250 for an x64 machine.
There are problems there as well.
1) The system says it's cleaning out data older than 10 days - but there's data there from July
2) You appear to have started three SFC scans - two completed (one with 114 POQs and one with 579 POQs), while the latest appears not to have completed (it breaks of at the end at POQ 68)
From what's there, it couldn't find any problems, but this type of inconsistency is worrying.

Please run an offline SFC as follows, and then follow with another online SFC....


Your best option in that case is to run the CHKDSK and SFC in offline mode from a Recovery Environment boot.

Reboot the computer, and tap the F8 key until you get the advanced boot menu up - one option should be 'Repair your computer'. Pick that one.

Log into your normal account.
You'll get a set of options - pick the Command Prompt one.
At the command prompt, type DIR C:\
- if we're lucky this will bring up a listing of your normal C: drive contents, including the Program Files folder(s) and the Windows folder.
If not, try D:\ or E:\ (etc. until you get the right letter)
then type the following command


sfc /scannow /OFFBOOTDIR=<drive>:\ /OFFWINDIR=<drive>:\Windows

where <drive> is the letter you found above.

Wait for the command to complete. (make a note of the response!).

Once it has, type EXIT and the pick the option to reboot.

 

[HAPPIKANGAROO]

So i've done the offline and online scans. I'll attach the cbs again. The offline scan said that there were no issues.

Also, I don't know if this is worth mentioning, but my C drive is the one where all my files are, but when i did the offline scan, my files were listed as in the D drive.

 

[NoelDP]

The change in drive letter is perfectly normal - that's why I phrase the instructions the way I do

The SFC scan found no problems with the file system - and had a much more reasonable 114 POQ entries! (actually, that's possibly a little low, for x64 Windows!)


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and attach it to your reply

 

[HAPPIKANGAROO]

When I try to run the installer, I get the following error: "Installer encountered an error: 0xc8000247".

 

[HAPPIKANGAROO]

So my issue just kind of fixed itself. I have no idea what changed but for some odd reason, i can now install windows updates. Thanks for all your help though. I really appreciate the amount of time and effort you put into helping.

 

[NoelDP]

Sorry I didn't come back to you - you should have shouted earlier !

Glad it seems sorted now - Good luck.

 

[HAPPIKANGAROO]

I assumed it was because of the holidays. Wouldn't have wanted to interrupt anything important like that.

 

[NoelDP]

I was on duty as usual on Xmas day and at New Year

Good luck.