Independent technical referenceOfficial site
  • Software and systems
  • Operating system

0x80070005

0x80070005 in Windows Update: access denied (E_ACCESSDENIED)

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 3 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

The update could not access files, folders or registry keys it needs: it is a permissions problem. Check you are using an administrator account and run the Windows Update troubleshooter.

Safety first

Stop and check this first

  • Before changing permissions on system folders, Microsoft says to back up the system disk. Do not run icacls or change owners unless you know how to undo it.

Safe checks you can perform

  • Administrator account
  • Windows Update troubleshooter
  • Third-party antivirus
  • Device managed by an organisation

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Find the blocked object in the logs
  • Do not attempt this professional task: Reset permissions and repair the component store
  • Do not attempt this professional task: Review third-party filter drivers

What a technician must be able to justify

A technician is coming

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Find the blocked object in the logs

    What they doThe technician opens the latest CBS.log in %Windir%\logs\CBS, searches for ", error" at the time of the failure and generates the Windows Update log with Get-WindowsUpdateLog.

    They must show youthe log line with HRESULT 0x80070005 and the affected object.

    In writingwhich object had wrong permissions and how it was fixed.

  2. Reset permissions and repair the component store

    What they doWith a backup of the system disk, they reset WinSxS and SoftwareDistribution permissions with icacls, return WinSxS ownership to TrustedInstaller, reset Windows Update components and run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow.

    They must show youthe output of each command and the update retry.

    In writingwhich steps were applied and which one fixed the error.

  3. Review third-party filter drivers

    What they doThey list file system filter drivers with fltmc and temporarily unload non-Microsoft ones to retry the install.

    They must show youthe filter list and which one was unloaded.

    In writingwhether the filter was the cause and which program installed it.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Checks and evidence, step by step

Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. 1

    Administrator account

    No special tools

    Procedure

    Who:
    you.
    How:
    in Settings, Accounts, check your account is an administrator and run Windows Update again from it.
    Result that matters:
    whether the update installs from an administrator account.
    If it installs:
    the account lacked the right.
    If 0x80070005 remains:
    the block is in the system, not your account.
    Evidence to keep:
    the update name (KB) and date of the attempt.

    Evidence: Microsoft Windows Update troubleshooting

  2. 2

    Windows Update troubleshooter

    No special tools

    Procedure

    Who:
    you.
    How:
    on Windows 11 go to Settings, System, Troubleshoot, Other troubleshooters, Windows Update; on Windows 10, Settings, Update & Security, Troubleshoot. Then restart and try again.
    Result that matters:
    whether the troubleshooter applies fixes and the update completes.
    If it completes:
    a Windows Update state was the problem and the troubleshooter fixed it.
    If the same code returns:
    move on to antivirus or IT support.
    Evidence to keep:
    screenshot of the troubleshooter summary.

    Evidence: Microsoft Windows Update troubleshooting

  3. 3

    Third-party antivirus

    No special tools

    Procedure

    Who:
    you.
    How:
    if you use an antivirus other than Windows Security, temporarily turn off its real-time protection and retry the update.
    Result that matters:
    whether the update installs without it.
    If it installs:
    the antivirus was locking files; turn it back on and ask its maker for an update.
    If not:
    turn it back on straight away; it was not the cause.
    Evidence to keep:
    antivirus version and result of the attempt.

    Turn the antivirus back on right after the test.

    Evidence: Troubleshoot Windows Update error 0x80070005

  4. 4

    Device managed by an organisation

    No special tools

    Procedure

    Who:
    you.
    How:
    if the PC belongs to work or school, do not change permissions: report the code and KB to the IT department.
    Result that matters:
    whether your organisation manages the device.
    If it does:
    a policy may be restricting access; IT resolves it.
    If it is personal:
    hand it to a technician to review the CBS log.
    Evidence to keep:
    screenshot of the error with KB and time.

    Evidence: Troubleshoot Windows Update error 0x80070005

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and systems
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • error 0x80070005
  • 0x80070005 E_ACCESSDENIED
  • 80070005
  • E_ACCESSDENIED
  • Windows 0x80070005
  • Windows Update 0x80070005

What it means

Microsoft describes 0x80070005 (E_ACCESSDENIED) as the error raised when the update process cannot access required files, folders or registry entries. It usually means a permissions problem on the component store (WinSxS), the SoftwareDistribution folder or the Component Based Servicing key, a third-party antivirus locking files, or a policy or management agent restricting writes. The code does not say which object is blocked: that comes from the CBS log.

Warnings and stop conditions

  • Mediumsource verified

    Before changing permissions on system folders, Microsoft says to back up the system disk. Do not run icacls or change owners unless you know how to undo it.

    Evidence: Troubleshoot Windows Update error 0x80070005

Symptoms and causes

Probable causes · in order

  • No administrator rightsPossible

    Some updates need administrator access. You can tell because the install proceeds from an administrator account.

    Evidence: Microsoft Windows Update troubleshooting

  • Third-party antivirus locking update filesPossible

    Microsoft lists it among the causes. Suspected if you use an antivirus other than Windows Security.

    Evidence: Troubleshoot Windows Update error 0x80070005

  • Changed permissions on WinSxS, SoftwareDistribution or the registryPossible

    If TrustedInstaller or SYSTEM lost permissions, the servicing stack has no access. Only the CBS log shows which object fails.

    Evidence: Common Windows Update errors · Troubleshoot Windows Update error 0x80070005

  • Group Policy or management agentPossible

    On work or school devices a policy can restrict writes to system folders; the IT department resolves it.

    Evidence: Troubleshoot Windows Update error 0x80070005

Virtual technician

Does 0x80070005 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Sources and technical references

  1. 1

    Common Windows Update errors

    Microsoft · 2026 · official_doc

  2. 2

    Troubleshoot Windows Update error 0x80070005

    Microsoft · 2026 · official_doc

  3. 3

    Microsoft Windows Update troubleshooting

    Microsoft · 2026 · official_doc

Sources: Common Windows Update errors · Troubleshoot Windows Update error 0x80070005 · Microsoft Windows Update troubleshootingreviewed 2026-10-03 · verified

Was this entry useful?