0x800703ee error upgrading to Windows 11

Anonymous
2025-06-18T05:29:59+00:00

Whether I use Windows Update or the Application Assistant, I get this same error.
Error message:
There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800703ee)

  • Antivirus and external drives disabled
  • Chkdsk returns no errors
  • There's plenty of space on C drive as well as in the EFI partititon
  • C drive has been cleaned up
  • All drivers have been updated
  • All Windows 11 requirements have been met

I'm not sure what else to try.

Windows for home | Windows 10 | Install and upgrade

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
Answer accepted by question author
Ramesh 181.9K Reputation points Volunteer Moderator
2025-06-20T10:10:58+00:00

Please run:

diskpart


select disk 2


list part


select part 2 -- This selects the EFI partition

Image


del part override


create partition efi


format fs=fat32 quick


assign letter=Y


list vol


exit

Was this answer helpful?

0 comments No comments

47 additional answers

Sort by: Oldest
  1. Anonymous
    2025-06-18T06:03:30+00:00

    Hi, I'm Ric, an independent advisor. I'm sorry you're experiencing this issue.

    The 0x800703ee error typically points to file corruption or interference from third-party software, even if antivirus is disabled.

    Please try these steps:

    1. Run DISM and SFC Tools to repair system files:

    DISM /Online /Cleanup-Image /RestoreHealth

    sfc /scannow

    Learn more here https://support.microsoft.com/en-us/topic/use-t...

    1. Perform an In-place Upgrade using the Windows 11 ISO – run the setup file and choose Keep personal files and apps. This often bypasses upgrade errors.

    https://www.microsoft.com/en-us/software-downlo...

    1. Check Windows Update Components – reset them using this guide:

    https://support.microsoft.com/en-us/windows/tro...

    If none of these work, try checking C:$WINDOWS.~BT\Sources\Panther\setuperr.log for detailed failure reasons.

    Hope this helps, otherwise, I would be happy to assist you further.

    Was this answer helpful?

    0 comments No comments
  2. Ramesh 181.9K Reputation points Volunteer Moderator
    2025-06-18T06:11:58+00:00
    1. Please run msinfo32.exe, and click System Summary. Resize the columns in the right pane to make the entries visible, and post a screenshot of that screen.
    2. Open admin Command Prompt and run:

    reagentc /info

    dir c:\windows\system32\recovery /a

    bcdedit

    diskpart

    list disk

    select disk 0

    list part

    list vol

    exit

    Post the output.

    1. Share the following setup log file on OneDrive (or any other host) and post the link here:

    C:$WINDOWS.~BT\Sources\Panther\setupact.log

    Note: "C:$WINDOWS.~BT" is a hidden folder. To access it, press Win + R, type "C:$WINDOWS.~BT" and click OK.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-06-18T07:41:48+00:00
    1. I did DISM and scannow and no issues there.

    1. I tried to do another upgrade to Windows 11 and it failed.
    2. Here's the link to setupact.log

    https://drive.google.com/file/d/12vHhXJO4jy8rOXVm7KnRpQKiOGjhEuCG/view?usp=drive_link 4) Here's the link to setuperr.log

    https://drive.google.com/file/d/1tlMApU-qeb6n6O45lMe2spTZCuuyfgWC/view?usp=drive_link

    System Summary:
    Image

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Ramesh 181.9K Reputation points Volunteer Moderator
    2025-06-18T07:49:22+00:00

    Open admin Command Prompt and run:

    reagentc /info

    dir c:\windows\system32\recovery /a

    bcdedit

    diskpart

    list disk

    select disk 0

    list part

    list vol

    exit

    Post the output.

    Attach setupact.log, as mentioned earlier. You've uploaded setuperr.log instead.

    Was this answer helpful?

    0 comments No comments