Error code 0x800f081f on installing KB5023706 (KB5022913)

Anonymous

3/15/2023 update: KB5023706 (March update on patch Tuesday) still has the same issue.

Original:

Hi all,

I'm having this issue installing KB5022913. The OS version is 22621.1325 (exit the beta insider channel days ago).

For more information, my machine is ASUS ROG Flow Z13 (2022) with i9-12900H, 32GB RAM, 2TB WD SN740, and RTX 3050ti Laptop graphics card.

Here's the CBS.log:

https://1drv.ms/u/s!AjKdZTNdsbqpgsu-BvDDw8gfqwxiF0k?e=G0yj66

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

Answer accepted by question author

Anonymous

The problem has been fixed through reinstalling windows 11

There's no need to reinstall the whole OS.

Uninstall the enablement packages, delete registry key WindowsSelfHost, delete folder SoftwareDistribution, disable optional diagnostics and restart.

Then check for updates and/or optional updates.

0 comments

45 additional answers

Anonymous

2023-03-16T12:24:12+00:00
Tried and failed. Don't know what to do next. How can we make our feedbacks be noticed by the developer?

All: For you with continuing trouble, did you

start in beta or some insider build?

Go through the off-ramp process?

end up, in fact, in non-beta as shown in Windows Update settings?

Just asking becasue I've lost track of what's happened to people here.

I got through somehow, but first I when through these steps:

10 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1255) (KB5022918)

14 Feb 2023-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5022497)

17 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1325) (KB5022914)

19 Feb Update Stack Package - (Version 1023.201.1012.0)

15 Mar Windows 11, version 22H2 (no KB nor number listed, turned out to be 22621.1413 KB5023706

Note KB5022913 does not show as ever installing.

Hope that helps.

Edited to show KB5023706

Hi Captain_Eric1,

My situation is same with @Nero Lee 929. The system version is 22621.1325.

I was originally in beta build; and I applied for withdraw.

I have gone through the off-ramp process.

I ended up in non-beta in Windows Update settings.

The process I have gone through is same with you but

I got an error when updating KB5023706, pushed yesterday.

The same error code 0x800f081f as the one, which appeared when I try to update KB5022913.

Note KB5023706 takes the place of KB5022913.
Thanks Lemonade. Good to know.

So you are now on 10.0.22623.1325) (KB5022914)?

And Windows Update offered you KB5023706 22621.1413 (like me) but it would not install, right?

If yes, then I don't know what to tell you, except wait a bit. You put in a Feedback Hub post?

Sorry.
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-16T10:46:36+00:00
Tried and failed. Don't know what to do next. How can we make our feedbacks be noticed by the developer?

All: For you with continuing trouble, did you

start in beta or some insider build?

Go through the off-ramp process?

end up, in fact, in non-beta as shown in Windows Update settings?

Just asking becasue I've lost track of what's happened to people here.

I got through somehow, but first I when through these steps:

10 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1255) (KB5022918)

14 Feb 2023-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5022497)

17 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1325) (KB5022914)

19 Feb Update Stack Package - (Version 1023.201.1012.0)

15 Mar Windows 11, version 22H2 (no KB nor number listed, turned out to be 22621.1413 KB5023706

Note KB5022913 does not show as ever installing.

Hope that helps.

Edited to show KB5023706
I just read that "This month's Patch Tuesday update [22621.1413 KB5023706, issued on 15 March] also includes changes that shipped in the KB5022913 update that was released in preview on February 28, 2023."

So, the illusive 22621.1413 KB5023706 is in there.
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-16T09:51:58+00:00
Tried and failed. Don't know what to do next. How can we make our feedbacks be noticed by the developer?

All: For you with continuing trouble, did you

start in beta or some insider build?

Go through the off-ramp process?

end up, in fact, in non-beta as shown in Windows Update settings?

Just asking becasue I've lost track of what's happened to people here.

I got through somehow, but first I when through these steps:

10 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1255) (KB5022918)

14 Feb 2023-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5022497)

17 Feb Cumulative Update for Windows 11 Insider Preview (10.0.22623.1325) (KB5022914)

19 Feb Update Stack Package - (Version 1023.201.1012.0)

15 Mar Windows 11, version 22H2 (no KB nor number listed, turned out to be 22621.1413 KB5023706

Note KB5022913 does not show as ever installing.

Hope that helps.

Edited to show KB5023706
I'm confused for sure. Today,a new beta build with a build number before my "fixed and final" Moment 2 update 22621.1413 KB5023706 . Go figure. I suppose beta could now be under 22624 and stable is under 22621, but that doesn't explain the KB lag.

Windows 11 Beta build 22624.1391 (KB5023011) comes with voice access improvements
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more