locked
Security Updates failed to install

    Question

  • Iam running he Windows 8 Developer Preview and on checking my Windows Update history I see that a couple of security updates failed. When I check for Windows Updates it doesn't relist the failed items. They are as follows:

     

    Security Update for Windows Developer Preview (KB2619339)

    Installation date: ‎14/‎12/‎2011 15:07

    Installation status: Failed

    Error details: Code 80240FFF

    Update type: Important

     


    Security Update for Windows Developer Preview (KB2639417)

    Installation date: ‎14/‎12/‎2011 15:07

    Installation status: Failed

    Error details: Code 80240FFF

    Update type: Important

    How do I resolve this?


    Thursday, December 15, 2011 1:01 PM

Answers

  • 2011-12-15	12:39:19:647	 960	 bc	DtaStor	WARNING: CSusEseSession | RemoveTimer failed, error 0x80248007<br/>2011-12-15	12:39:19:647	 960	 bc	AU	WARNING: CPersistentTimeoutScheduler | RemoveTimer, failed, error = 0x80248007<br/><br/>//
    // MessageId: WU_E_DS_NODATA
    //
    // MessageText:
    //
    // The information requested is not in the data store.
    //
    #define WU_E_DS_NODATA                   _HRESULT_TYPEDEF_(0x80248007L)
    

    So it looks like an error with the Softwaredistribution folder. Stop the Windows update service, rename the folder C:\Windows\SoftwareDistribution to C:\Windows\SoftwareDistribution_OLD, start the Update service again and search again for updates.
    "A programmer is just a tool which converts caffeine into code"

    Thursday, December 15, 2011 2:57 PM
  • They failed the first time because of an error with the distribution folder. Renaming the folder fixed it.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, December 18, 2011 1:21 PM

All replies

  • The error code is not useful:

    //
    // MessageId: WU_E_UNEXPECTED
    //
    // MessageText:
    //
    // An operation failed due to reasons not covered by another error code.
    //
    #define WU_E_UNEXPECTED                  _HRESULT_TYPEDEF_(0x80240FFFL)
    

    to see the cause of Windows 7/8 update failures, we must look for error messages in the following log files.

    Please run the Windows Explorer and go to the folder "C:\Windows\Logs\CBS\" and copy all files to your document folder, also copy the setupapi.dev.log from the folder C:\Windows\Inf, the "C:\Windows\WindowsUpdate.log" and the file "C:\Windows\winsxs\poqexec.log" to your document folder (otherwise you can't upload it), zip all files into 1 ZIP and upload the zip to your SkyDrive [1] and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code"

    Thursday, December 15, 2011 1:28 PM
  • OK,here is the link to the folder "Windows 8 Log Files" on my Skydrive in Documents. I haven't zipped the files as I haven't got a zip file archiver yet in W8DP. I hope that is OK. Incidentally, when I look on my Control Panel\Programs & features\Installed Updates it shows the updates as being installed!!

     

    https://skydrive.live.com/redir.aspx?cid=aa8461ca7aad5273&resid=AA8461CA7AAD5273!207&parid=AA8461CA7AAD5273!118&authkey=!AAbjZqz-mYg8Ihg

     

    Thursday, December 15, 2011 2:31 PM
  • Also, go to control panel and action center and then troubleshoot problem and run update troubleshooter.
    Thursday, December 15, 2011 2:47 PM
  • 2011-12-15	12:39:19:647	 960	 bc	DtaStor	WARNING: CSusEseSession | RemoveTimer failed, error 0x80248007<br/>2011-12-15	12:39:19:647	 960	 bc	AU	WARNING: CPersistentTimeoutScheduler | RemoveTimer, failed, error = 0x80248007<br/><br/>//
    // MessageId: WU_E_DS_NODATA
    //
    // MessageText:
    //
    // The information requested is not in the data store.
    //
    #define WU_E_DS_NODATA                   _HRESULT_TYPEDEF_(0x80248007L)
    

    So it looks like an error with the Softwaredistribution folder. Stop the Windows update service, rename the folder C:\Windows\SoftwareDistribution to C:\Windows\SoftwareDistribution_OLD, start the Update service again and search again for updates.
    "A programmer is just a tool which converts caffeine into code"

    Thursday, December 15, 2011 2:57 PM
  • OK, I have renamed the folder as OLD and restarted the windows update service. Well, actually is was stopped already before I looked at the services and starting wouldn't start so I re-started the system and found that it was configuring updates already!

    After re-start completed I looked at the installed updates and the two files were still there. When I looked at the updates history the only updates there were the ones it installed after the re-start.


    • Edited by Silverpulser Thursday, December 15, 2011 4:05 PM
    Thursday, December 15, 2011 4:05 PM
  •  When I looked at the updates history the only updates there were the ones it installed after the re-start.


    this is ok, renaming the software distribution folder deletes the history.

    Were the 2 updates configured correctly or do you still have issues?


    "A programmer is just a tool which converts caffeine into code"

    Thursday, December 15, 2011 6:38 PM
  • You've GOT to be kidding me... ALL off these steps to fix a service that should be working in the first place? I've been a Windows user for many years and have constantly run into problems such as these. Why isn't the update service reliable as it should be? The only reason I keep using Windows is to play online games.

    I also am a user of Apple's Mac OS and have never experienced problems from their end... maybe I'm lucky, but from what i know, their updating system just works.

    Thursday, December 15, 2011 7:55 PM
  • Well, deleting the history doesn't install the updates does it? I imagined that after the folder was re-named and the Windows Update run that it would install the two failed updates. However, as Windows had already listed the updates in the Installed Updates listing I imagine it didn't now that they had also been shown as failed. Now I have no idea whether they are really installed or working. Perhaps you can instruct me how to ascertain that please. Maybe I should try uninstalling the updates and re-run the Windows Update. What do you think?
    Thursday, December 15, 2011 10:33 PM
  • Well, deleting the history doesn't install the updates does it? I imagined that after the folder was re-named and the Windows Update run that it would install the two failed updates. However, as Windows had already listed the updates in the Installed Updates listing I imagine it didn't now that they had also been shown as failed. Now I have no idea whether they are really installed or working. Perhaps you can instruct me how to ascertain that please. Maybe I should try uninstalling the updates and re-run the Windows Update. What do you think?
    Andre.Ziegler, please can you advise me.
    Saturday, December 17, 2011 11:21 AM
  • I'm not online here each day so wait a few days for my reply ;)

    You have 3 ways to check if the Updates are installed:

    1) Look in the control panel->programs & features->installed updates if the updates are installed

    2) download the updates again and try to install them:

    http://download.windowsupdate.com/msdownload/update/software/secu/2011/11/windows6.2-kb2619339-x86-m3_ee770d2cda6950fbc885fb790caad6f57ce1206d.msu

    http://download.windowsupdate.com/msdownload/update/software/secu/2011/12/windows6.2-kb2639417-x86-m3_b4bcc52b4797cb0bdaa38281c3f548aa4d7aa03b.msu

    If the updates are installed you get an message during setup that the update is already installed.

    3) run Windows-Explorer and check the file versions of the files

    kb2619339 EncDec.dll 6.2.8102.119

    kb2639417 win32k.sys 6.2.8102.128


    "A programmer is just a tool which converts caffeine into code"

    Saturday, December 17, 2011 7:52 PM
  • OK, Andre, I have checked as above and it looks like the two files are as you have shown when I look at their properties/details. Attempting to install the downloaded updates is met with a message they they are already installed.

    So, all looks OK, with the only remaining question being why did Windows history show the updates as failed?

    Sunday, December 18, 2011 12:23 PM
  • They failed the first time because of an error with the distribution folder. Renaming the folder fixed it.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, December 18, 2011 1:21 PM
  • Still somewhat confused as I only ever attempted one install; there was no second attempt, at least not by me manually.
    Monday, December 19, 2011 9:11 AM
  • I have no idea why this was so. Be happy that you got the updates installed.
    "A programmer is just a tool which converts caffeine into code"

    Wednesday, December 21, 2011 10:42 PM