Share via

Service Pack 1 for Microsoft Access Database Engine 2010 (KB2460011) 32-bit Edition Install error - 0x80070643

Matthew Mc 0 Reputation points
2026-04-27T16:06:19.76+00:00

Windows update failed. Have tried rebooting etc. Nothing seems to work.

Windows for home | Windows 11 | Windows update
0 comments No comments

2 answers

Sort by: Most helpful
  1. Lester Bernard Reyes 82,020 Reputation points Independent Advisor
    2026-04-27T16:40:38.1766667+00:00

    Hi, I'm Bernard. I'm happy to help!

    Do you still have Microsoft Access 2010? Or is it just popping up on your Windows Update page? If it's just a pop-up on your Windows Update page, and if you do not have MS Access 2010, I recommend hiding the update by using the Hide/Show update troubleshooter:

    https://www.tenforums.com/tutorials/8280-hide-show-windows-updates-windows-10-a.html

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Additional note: This is a public forum. I may respond shortly, but I apologize in advance for any delays. I am simply a fellow user trying to provide helpful insights and information.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-04-27T16:06:33.61+00:00

    Error 0x80070643 when installing an Office/Access Database Engine 2010 update is a generic Windows Installer failure that commonly occurs with Office 2010 updates.

    For Office 2010–related update failures, the documented approach is to troubleshoot using the Office update logs and, if necessary, repair or reinstall the affected Office/Access components. Use this workflow:

    1. Enable or confirm logging for the failing update
      • If the update was released after February 2009 (as with Office 2010 SP/updates), logging should already be enabled.
      • If rerunning the standalone update package manually, run it from an elevated command prompt with the /log switch to force logging, for example:
        • Save the update .exe locally.
        • Open Command Prompt as Administrator.
        • Run: full-path-to-update.exe /log
    2. Locate the update log files
      • Open the Temp folder:
        • Press Windows + R, type %temp%, press Enter.
      • Look for:
        • Opatchinstall(#).log files (where # is a number).
        • ######_MSPLOG.log files (where ###### is the update MSP name).
      • Copy these logs to a convenient folder.
    3. Analyze the logs for the failure cause
      • Open the most recent Opatchinstall(#).log and corresponding *_MSPLOG.log.
      • Search for error or the error code to identify what part of the Office/Access Database Engine 2010 installation is failing (for example, missing files, registry access problems, or detection issues).
    4. Repair or reinstall Office 2010 / Access Database Engine 2010
      • If the logs indicate corruption or failure in Office 2010 or Access Database Engine 2010, repair or reinstall those components, then retry Windows Update.
      • If Access Database Engine 2010 is installed side-by-side with other Office 2010 components (32-bit vs 64-bit), ensure the bitness is consistent. Inconsistent 32-bit/64-bit Office components can cause installation/update failures.
    5. Retry Windows Update
      • After repair/reinstall and a reboot, run Windows Update again and check if KB2460011 installs successfully.

    If the error persists, use the detailed information from the Opatchinstall and *_MSPLOG logs to determine the exact failing action and apply targeted fixes (for example, permissions or missing paths) before retrying.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.