Author Topic: Windows update cannot currently check for updates  (Read 25685 times)

0 Members and 1 Guest are viewing this topic.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Windows update cannot currently check for updates
« on: February 18, 2016, 11:41:40 AM »
Hi

Using Windows 7 Home Premium x64,yesterday it dawned on me i had not seen any windows updates in quiet some time and also my AV Eset had not indicated updates were available either.When attempting to check updates via control panel it hung for quiet some time with a blue spinning circle then eventually took me to the check for updates screen which is red.After clicking the update button i received the dreaded notice"Windows cannot currently check for updates because the service is not running",after readiing up on the problem i have tried the various Microsoft fixes that state they have fixed various problems but still cant update,i have tried stopping the update service and deleting the software folder and restarting the update service but still nothing.
At a guess i think the last updates i did was the November ones which finished with a some updates failed to install properly.
I have also downloaded the System Update Readiness tool for my x64 windows but when running the program i get an error message-Installer encountered an error:0xc8000426,ran SFC scan which came back clean.Finally i had read a couple of sites recommend the All In One repair tool from here and people had reported it had cured the problem,upon running the problem i did a chk disc scan which reported errors so a full scan was completed then the repair tool was run,sadly it has not cured the problem for me so i have joined up to see if anyone can help me further.

Many thanks.


Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #1 on: February 18, 2016, 02:04:52 PM »
chkdsk in read-only mode can give a false report if the HDD is being written to at the time of the scan.

Were you able to read the chkdsk /f report ?

To view it, go Start - type eventvwr and press enter.

When Event Viewer has read the data, expand Windows Logs then click on the name Application - Action - Find then type chkdsk or wininit into the Find box and press enter.

Cancel the Find box and read the report in the scrollable window.

In Windows Repair did you run the Pre-Scan in Option 2 to see if it found any errors ?

I once had Check for updates in red and the Pre-Scan found problems with the Environment Variables and after running the repair options for those in Option 2, found that fixed the problem.

Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #2 on: February 19, 2016, 02:37:03 AM »
Hi Boggin thanks for the reply,reading the chkdsk report it seems it was performed in read only mode,

Log Name:      Application
Source:        Chkdsk
Date:          18/02/2016 21:25:40
Event ID:      26213
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Dave-PC
Description:
Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run. 

Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  294400 file records processed.                                         

File verification completed.
  883 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  44 reparse records processed.                                     

CHKDSK is verifying indexes (stage 2 of 3)...
  351520 index entries processed.                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered.                                     

CHKDSK is verifying security descriptors (stage 3 of 3)...
  294400 file SDs/SIDs processed.                                       

Cleaning up 2627 unused index entries from index $SII of file 0x9.
Cleaning up 2627 unused index entries from index $SDH of file 0x9.
Cleaning up 2627 unused security descriptors.
Security descriptor verification completed.
  28561 data files processed.                                           

CHKDSK is verifying Usn Journal...
  35789576 USN bytes processed.                                           

Usn Journal verification completed.
Windows has checked the file system and found no problems.

 210006015 KB total disk space.
  69805624 KB in 104089 files.
    151972 KB in 28562 indexes.
         0 KB in bad sectors.
    405923 KB in use by the system.
     65536 KB occupied by the log file.
 139642496 KB available on disk.

      4096 bytes in each allocation unit.
  52501503 total allocation units on disk.
  34910624 allocation units available on disk.

On the second point i didnt run a pre scan so did it this morning,there was thousands of reparse points errors and a environmental variable problem with ATI Technologies,however when i tried to save the report it caused the program to stop responding and i had to shut it down and run the pre scan again so not sure if the report saved.Going to try the environmental variable repair first the report back.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #3 on: February 19, 2016, 03:09:40 AM »
Ok repaired the environmental variable,rebooted and checked that windows update was running using services then tried to check for updates and received the usual message.I reran the pre scan to repair the reparse points faults and something caught my eye in the scanning windows package files,of the 2,726 package files that are possibly corrupt i see the following-
C:\Windows\servicing\Packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-AdmComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-CoreComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
C:\Windows\servicing\Packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~amd64~~7.6.7600.320.mum

I presume this is related the windows update ?.
Anyway will run the reparse points repair and wait for some advice here,to add an extra point the pre scan showed clear on environmental variables on the re scan.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #4 on: February 19, 2016, 03:54:43 AM »
I think it's better to run the lower chkdsk option in the program on the off chance that it does give a false report as the warning says and that will initiate a chkdsk /f - although in this case, the read-only has come back clean.

Hopefully the Reparse repair will repair those, but I'll move your thread to the CAT and MUM File Request section for Julian's attention.
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #5 on: February 19, 2016, 04:10:55 AM »
Thanks Boggin,sorry how do i run the lower chkdsk option,in step 3 i see check and open check disc at next boot,will this option appear on the reboot.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #6 on: February 19, 2016, 04:25:34 AM »
Yes, when you reboot you'll get a message that a chkdsk has been scheduled and I think you have about 10 seconds to abort it.

You can run it manually yourself from a cmd prompt by going Start - type cmd then right click on cmd and select Run as administrator - accept the UAC then enter chkdsk /f

You will be prompted to type and enter y for it to run on the next restart - then enter shutdown /r /t 00 which will effect an immediate reboot and then just wait for it to do its thing.

You can then read the report in Event Viewer as I've previously described.

How did the Reparse repair go ?
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #7 on: February 19, 2016, 04:33:45 AM »
Thank you Boggins for the clear instructions,i have to out for an hour so will run the chkdsk then.I performed the reparse repairs then rebooted,then using windows repair tool rebooted into safe mode and ran another scan,this found around 8 reparse faults this time so i ran the repair again.Not done a prescan again yet but will do one when i get back and let you know the results.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #8 on: February 19, 2016, 04:51:44 AM »
If there are any outstanding, then post the list as you did before and Julian will sort those for you.
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #9 on: February 19, 2016, 06:35:32 AM »
This is the report from the chkdsk ran this morning.

Log Name:      Application
Source:        Chkdsk
Date:          19/02/2016 12:27:53
Event ID:      26213
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Dave-PC
Description:
Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run. 

Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  294400 file records processed.                                         

File verification completed.
  883 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  92 reparse records processed.                                     

CHKDSK is verifying indexes (stage 2 of 3)...
  351772 index entries processed.                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered.                                     

CHKDSK is verifying security descriptors (stage 3 of 3)...
  294400 file SDs/SIDs processed.                                       

Cleaning up 2635 unused index entries from index $SII of file 0x9.
Cleaning up 2635 unused index entries from index $SDH of file 0x9.
Cleaning up 2635 unused security descriptors.
Security descriptor verification completed.
  28687 data files processed.                                           

CHKDSK is verifying Usn Journal...
  35818440 USN bytes processed.                                           

Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

 210006015 KB total disk space.
  70102120 KB in 105995 files.
    153060 KB in 28688 indexes.
         0 KB in bad sectors.
    406059 KB in use by the system.
     65536 KB occupied by the log file.
 139344776 KB available on disk.

      4096 bytes in each allocation unit.
  52501503 total allocation units on disk.
  34836194 allocation units available on disk.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26213</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-02-19T12:27:53.000000000Z" />
    <EventRecordID>139690</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Dave-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  294400 file records processed.                                         

File verification completed.
  883 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  92 reparse records processed.                                     

CHKDSK is verifying indexes (stage 2 of 3)...
  351772 index entries processed.                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered.                                     

CHKDSK is verifying security descriptors (stage 3 of 3)...
  294400 file SDs/SIDs processed.                                       

Cleaning up 2635 unused index entries from index $SII of file 0x9.
Cleaning up 2635 unused index entries from index $SDH of file 0x9.
Cleaning up 2635 unused security descriptors.
Security descriptor verification completed.
  28687 data files processed.                                           

CHKDSK is verifying Usn Journal...
  35818440 USN bytes processed.                                           

Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

 210006015 KB total disk space.
  70102120 KB in 105995 files.
    153060 KB in 28688 indexes.
         0 KB in bad sectors.
    406059 KB in use by the system.
     65536 KB occupied by the log file.
 139344776 KB available on disk.

      4096 bytes in each allocation unit.
  52501503 total allocation units on disk.
  34836194 allocation units available on disk.
</Data>
    <Binary>007E0400270E0200A1F3030000000000DA0300005C0000000000000000000000</Binary>
  </EventData>
</Event>

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #10 on: February 19, 2016, 06:59:29 AM »
Conducted another pre scan in safe mode and no reparse point errors were found this time.

I have also saved a copy of the pre scan report so all the window package files can be viewed if needed but as there are 2,726 the list is huge so wont post it unless i am requested to.
« Last Edit: February 19, 2016, 07:27:10 AM by BigBear68, Reason: Added information »

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #11 on: February 19, 2016, 08:46:03 AM »
Are you now saying there are 2,726 Package files that are reported as corrupt or missing ?
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #12 on: February 19, 2016, 08:52:16 AM »
Yes sorry i got confused and thought it was over a thousand re parse point errors but it is actually window package files,there was several re parse errors but these have been fixed now.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #13 on: February 19, 2016, 08:55:24 AM »
Is your machine Intel based ?

It has been noted that when WR reports that much corruption on an Intel based machine that downloading the chipset drivers usually resolves.
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #14 on: February 19, 2016, 08:57:06 AM »
No its a AMD based.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #15 on: February 19, 2016, 09:06:42 AM »
While AMD do have chipset drivers, my Win 7 laptops use AMD and their chipset drivers are the video drivers.

Are you using a desktop or laptop ?
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #16 on: February 19, 2016, 09:10:09 AM »
Its a laptop-Asus X53U

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #17 on: February 19, 2016, 09:15:06 AM »
See if downloading the chipset drivers from Asus has the same effect http://www.asus.com/support/Download/3/114/0/15/30/
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #18 on: February 19, 2016, 09:22:20 AM »
ok downloading the chipset driver V8.930.13.6000 from there site,when i install it should i rerun the pre scan to see if it clears the corruptions ?.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #19 on: February 19, 2016, 09:22:54 AM »
Yes.
« Last Edit: February 19, 2016, 09:26:46 AM by Boggin »
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #20 on: February 19, 2016, 09:29:40 AM »
Unzipping the chipset folder it has catalyst install manager and seems to be drivers for my graphics card,i already has the latest drivers for this ?,is this correct.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #21 on: February 19, 2016, 09:34:57 AM »
It would seem that what Asus call AMD Chipset drivers are the video drivers are as for my Toshibas.

Reinstall them anyway and opt for the Custom install and select all.
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #22 on: February 19, 2016, 10:03:12 AM »
Ok did the custom install and selected all,running a pre scan now and its still showing 2,726 combined problems in the package files.

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9251
  • Location: UK
  • Karma: 117
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #23 on: February 19, 2016, 10:04:59 AM »
I'll contact Shane for advice on this as this has never been reported for AMD before.
Tom.

Offline BigBear68

  • Newbie
  • *
  • Join Date: Feb 2016
  • Posts: 32
  • Location: Birmingham,UK
  • Karma: 0
    • View Profile
Re: Windows update cannot currently check for updates
« Reply #24 on: February 19, 2016, 10:09:00 AM »
Ok thanks for all the help i appreciate it,just a small note when i unzipped the chipset package there is a folder titled Packages-Drivers then three folders titled Display,SBDrv and WDM,these have installers and other inf files,not sure if this is relevant.