How to fix this Event Viewer Crash showing up in my Application Log?

Question

How to fix this Event Viewer Crash showing up in my Application Log?

Charles High 5

I am not receiving any popup errors or software not working with this error but it seems the error exits "behind the scene". I noticed in the Event Viewer the "Error" or "crash" noted and happens every day. This is an example from EVENT VIEWER.

Level: Error 2/27/26 6:30: 19 PM Windows App Runtime Event ID 22 Task Category: None

From what I can see, the software is trying to find a Bootstrapper software version 1.6 (MSIX package version - 6000.424.1611.0 which does not exist and is causing an error. I believe this will need to be corrected on Microsoft's side (the programmers) and send out a correction on this software. Hope to see a correction very soon. I am sure others are having this same problem. Thank you.

User's image

0 comments

Answer recommended by moderator

0 additional answers

Your answer

Answer 1

Jack Dang (WICLOUD CORPORATION) 16,040 Microsoft External Staff Moderator

Hi @Charles High ,

Thanks for reaching out.

I took a look at the Event Viewer error you’re seeing:

Windows App Runtime
ERROR 0x80670016: Bootstrapper initialization failed while looking for version 1.6 (MSIX package version >= 6000.424.1611.0)

It doesn’t impact your apps or system functionality, which is why you haven’t noticed any popups or crashes. Essentially, your computer is just quietly logging that it couldn’t find that package.

If you’d like to address it, I suggest a few approaches:

Update Windows and apps - Sometimes missing MSIX packages are included in updates. Installing the latest updates may resolve the log error.
Repair Windows App Runtime - You can go to Settings -> Apps -> Installed apps -> Windows App Runtime -> Modify/Repair.
Ignore the log - Since it’s not causing any visible problems, it’s safe to leave it. Event Viewer is designed to log even small issues that don’t impact system functionality.

Optionally, if the repeated messages are cluttering your logs, you can filter or create a custom view in Event Viewer to hide this specific error ID (22) without changing anything on your system.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Michael Le (WICLOUD CORPORATION) 11,085 Reputation points Microsoft External Staff Moderator

2026-03-05T09:56:24.8566667+00:00

Hello @Charles High , if you have any questions, feel free to reach out anytime it suits you.
Charles High 5 Reputation points

2026-03-07T19:40:02.25+00:00

Thank you so much for your response! (#1) I always perform updates when they are released, update drivers, and other software. (#2) I did perform the Window App Runtime repair as stated; not sure if this will correct the issue. It is more of a Micrsoft programming error. I will have to do your final suggestion is to hide the error so it is not noticable. It is just annoying to see these errors.

I have another problem with Microsoft Office error coming up in Event Viewer with Kernelbase.dll. Microsoft Office Push Notification Utility 16.0.19826.20002. Not ure if you are familar with this as well or if it shows up in your Event Viewer. I wish Microsoft would fix these errors rather then us having to work around them.

Faulting application name: opushutil.exe, version: 16.0.19826.20002,

Faulting module name: KERNELBASE.dll, version: 10.0.26100.7920,

Exception code: 0xc06d007f

Fault offset: 0x00163184

Faulting process id: 0x3CF8

I have state this in another comment left in this community log.
Jack Dang (WICLOUD CORPORATION) 16,040 Reputation points Microsoft External Staff Moderator

2026-03-09T07:01:52.4166667+00:00
Hi @Charles High ,

Thanks for sharing the details.

The opushutil.exe / KERNELBASE.dll error is usually a minor Office background issue and typically doesn’t affect functionality. You can try repairing Office (Quick or Online Repair) and ensure it’s fully updated.

If the log entries are distracting, you can filter them in Event Viewer.

Since this can be a Microsoft-level issue, you can also send feedback via the Feedback Hub:

Press Win + F (or search for “Feedback Hub”).

Click Report a problem.

Describe the issue and include the Event Viewer details.

Submit so Microsoft can investigate and prioritize a fix.

If my explanation was helpful so far, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

Share via

How to fix this Event Viewer Crash showing up in my Application Log?

0 additional answers

Your answer