Windows 7 SP1 Update Error Code 800F081F

Anonymous
2014-10-07T17:46:09+00:00

Hi,

For a few days now I'm getting an alert in my system tray that Windows cannot automatically search for updates. Clicking on the icon leads me to a message saying that the Windows Update Agent needs an update and a button to do this update. Clicking on the button closes the window, which then opens again after a few seconds with an error message that Windows cannot search for new updates. Error message code = 800F081F.

When I looked at my update history, I see that Windows Update Agent 7.6.7600.320 has failed daily for over a month now. I've already tried several suggestions (some posted on the dutch microsoft community) e.g. clearing the update cache, system update readiness tool, a 'clean' start of Windows, MS Fix It, but to no avail. Checkdisk and System File Checker scans found nothing wrong.

I'm using Windows 7 Home Premium with SP1, 64 bit. Not sure what other information I should provide that is relevant?

Hope someone can help me with this issue. Thanks in advance!

Kind regards,

Paul

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Oldest
  1. Anonymous
    2014-11-07T10:03:17+00:00

    Paul

    Please download and run the System Update Readiness Tool -64 bit version

    http://www.microsoft.com/en-us/download/details.aspx?id=20858

    The System Update Readiness Tool creates a log file that captures any issues that the tool found or fixed. The log file is located at the following location:

    •%SYSTEMROOT%\Logs\CBS\CheckSUR.log

    •%SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log

    Please upload a copy of these logs to your Sky Drive as shared files and post a link here.

    Click on the Start button and select Control Panel, Administrative Tools, Services. Locate Intel(R) Management and Security Application Local Management Service in the list. Check that the StartUp type is Manual. If it is not set to Manual right click and select Properties, General tab. There is a box after StartUp type. The options are available on a drop down by clicking on the arrow down to the right of the box. Make the change and click on Apply and OK. Click the Start button to check that the service can be started.

    Log Name:      Application

    Source:        VSS

    Date:          06/11/2014 19:21:58

    Event ID:      12348

    Level:         Warning

    Description:

    Volume Shadow Copy Service warning: VSS was denied access to the root of volume \?\Volume{475bbd93-ffc9-11df-96ed-20cf3052d830}. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again.

    Bewerking:

       Auto-release schaduwkopieën verwijderen

       Provider laden

    Context:

       Uitvoeringscontext: System Provider

    Access the Event ID: 12348 report in the Event Viewer Application log. Open the report and click the blue link475bbd93-ffc9-11df-96ed-20cf3052d830and see where it takes you.

    Another way identify the volume is to select Start, Control Panel, Device Manager, expand Disk drives, right click, select Properties and Details. Use the scroll to the right of Property and select Device class guid. Repeat the procedure until you can match the guid **475bbd93-ffc9-11df-96ed-20cf3052d830.**Next click the Volumes tab and the Populate button. You can then see which volume or volumes occupy the Disk.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-11-09T21:45:32+00:00

    Hi Gerry,

    here are the logfiles:

    https://onedrive.live.com/redir?resid=D4EDCF2B47D2E08D%21112

    https://onedrive.live.com/redir?resid=D4EDCF2B47D2E08D%21111

    When I clicked the link in the event viewer application log, I got the message that the location cannot be accessed. I also tried the second method to identify the volume, but could not find it. Under 'disk drives' there was just one entry, but with a different guid.

    Thanks,

    Paul

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-11-10T09:15:36+00:00

    I also tried the second method to identify the volume, but could not find it. Under 'disk drives' there was just one entry, but with a different guid.

    Type Device Manager in the Search box above the Start button and press ENTER. Are there any yellow question marks in Device Manager? If yes what is the Device Error code.

    To see Hidden Devices (Non Plug and Play Drivers) you need to select View, Show Hidden Devices. It is necessary to do this every time you open Device Manager if you need to see them.

    A further complication can be Ghosted Devices –installed but not connected!

    http://www.lockergnome.com/windows/2005/04/29/display-hidden-devices-in-device-manager-xp/

    Select Start, All Programs, Accessories, right click Command Prompt, and click Run as administrator from the drop down menu.. Type *cd* and press ENTER. Type "chkdsk c: /r" without the quotes and hit ENTER. Make sure you include the spaces indicated. Enter Y when asked whether you wish to run chkdsk on restarting the computer. Type exit, press the ENTER key and restart the computer.

    Please run System File Checker and say if it cannot fix corrupted files: http://support.microsoft.com/kb/929833

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-11-10T21:12:40+00:00

    Hi Gerry,

    used the option to display hidden devices as described in the link you provided, but still could find a disk drive that matches the guid.

    Ran both checkdisk and SFC: both reported no problems.

    Regards,

    Paul

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-11-21T12:49:41+00:00

    No more suggestions? Anyone? :-)

    Regards,

    Paul

    Was this answer helpful?

    0 comments No comments