Advice Request COMODO blocks Windows Updates with error 0x80070005

[cruelsister]

The issue with this thread is really the Title- instead of " COMODO blocks Windows Updates with error 0x80070005" (an incorrect assumption), it should have been titled "Why can't Update 0x80070005 install on my system".

It would have saved on oodles of Assumptional analyses.

 

[Antig]

@cruelsister
I owe you oodles of thanks for advice and now for learning a never heard before word: oodles.

 

[Andy Ful]

It would have saved on oodles of Assumptional analyses.

It would not, I am afraid (however, the title can be incorrect). The thread is not for blaming something, but for solving the concrete problem (0x80070005 error) encountered by the Comodo user(s).
The author did not experience this problem with Comodo uninstalled.
Comodo Firewall is a third-party and restrictive addition (with a difficult history), so it should initially be considered the prime suspect.
However, the investigation revealed that there are more suspects.
It is also possible that all of them are guilty.

 

[TheMalwareMaster]

It would not, I am afraid (however, the title can be incorrect). The thread is not for blaming something, but for solving the concrete problem (0x80070005 error) encountered by the Comodo user(s).
The author did not experience this problem with Comodo uninstalled.
Comodo Firewall is a third-party and restrictive addition (with a difficult history), so it should initially be considered the prime suspect.
However, the investigation revealed that there are more suspects.
It is also possible that all of them are guilty.

Correct. I also want to say that update problems started with Windows 11 24H2. Before, no issue whatsoever

 

[Andy Ful]

Correct. I also want to say that update problems started with Windows 11 24H2. Before, no issue whatsoever

The same is true for my VM testing machine, but with Windows 25H2 (upgraded directly from 23H2, which updated without errors).
It is possible that Microsoft changed something in Microsoft Defender, so Windows Updates may fail on some machines with CF + MD.
On cumulative updates, the issue disappears when I apply a tweak related to %WinDir% on CF or on MD (%WinDir% path exclusion).

 

[TheMalwareMaster]

The same is true for my VM testing machine, but with Windows 25H2 (upgraded directly from 23H2, which updated without errors).
It is possible that Microsoft changed something in Microsoft Defender, so Windows Updates may fail on some machines with CF + MD.
On cumulative updates, the issue disappears when I apply a tweak related to %WinDir% on CF or on MD (%WinDir% path exclusion).

Do you confirm this is the correct place where to remove the windir?

Is there any impact in terms of security? I guess no since Containment will be also in place, and it does not use the HIPS rules

 

[Andy Ful]

Do you confirm this is the correct place where to remove the windir?

Yes, however, do not do it in your current config. Export your current config, save, import under a different name, activate temporarily, and finally remove the rule. Use this temporary config to update.

Is there any impact in terms of security? I guess no since Containment will be also in place, and it does not use the HIPS rules

This is a question for Comodo staff or Comodo forum moderators.

 

[TheMalwareMaster]

Yes, however, do not do it in your current config. Export your current config, save, import under a different name, activate temporarily, and finally remove the rule. Use this temporary config to update.

Ok, but why? Hoping for the future to be fixed? Since I am going to remove the rule anyway, I don't understand what would change

 

[Andy Ful]

Since I am going to remove the rule anyway, I don't understand what would change

If you are going to remove the rule with a pipe, you will not be able to add it manually (the rule editor does not accept creating rules with pipes).

 

[TheMalwareMaster]

If you are going to remove the rule with a pipe, you will not be able to add it manually (the rule editor does not accept creating rules with pipes).

It's such a pain to update manually. If the bug comes back in, I will remove that rule... I am confident reinstalling and configuring comodo from scratch if needed...

 

[Andy Ful]

It's such a pain to update manually. If the bug comes back in, I will remove that rule... I am confident reinstalling and configuring comodo from scratch if needed...

Although removing that rule helped some people, you should not consider it as 100% solution. It has not been thoroughly tested yet.
Also, it has not been discussed with the Comodo staff.

 

[nickstar1]

Comodo security products feel less like “cybersecurity” and more like an ongoing beta test that never ends. Every release seems to introduce a fresh collection of bugs, broken features, and half-working components, as if stability is an optional add-on rather than a core requirement. Using Comodo isn’t about peace of mind—it’s about wondering which function will fail next and whether today’s update will quietly undo yesterday’s fix. The real irony is that many of these problems aren’t new, obscure, or hard to reproduce. Users have been reporting the same issues for years: random crashes, false positives that block legitimate software, clunky interfaces, and features that sound great on paper but barely function in practice. Instead of refinement and polish, we get more complexity piled on top of an already shaky foundation, creating a product that feels increasingly bloated and unreliable.

What makes this situation even more frustrating is the near-total silence from the people in charge. User feedback, bug reports, and reasonable requests for improvement seem to disappear into a black hole. The developers appear either unwilling or unable to address long-standing issues, while leadership yes, including the CEO seems completely detached from the day-to-day experience of actual users. It’s hard to believe anyone responsible for this product actively uses it. At times, it feels like Comodo is more interested in marketing buzzwords and grand promises than delivering a stable, usable security solution. New features are announced as if they’re revolutionary, yet basic functionality remains unreliable. Instead of listening to their user base, the company seems content to ignore criticism and pretend everything is fine, leaving customers to troubleshoot problems that should never have existed in the first place.

In the end, Comodo security products are a masterclass in how not to manage software development or customer trust. When bugs are constant, feedback is ignored, and leadership shows no urgency to improve, frustration is inevitable. Security software should inspire confidence not sarcasm, anger, and the strong urge to uninstall and move on to something that actually works.

 

[the1stbazza]

Well, for the first time in quite a while, this month's (Jan 2026) patch Tuesday went through without a hitch on all 3 of my PCs without resorting hacking Comodo settings.

I'm not suggesting that anything has been fixed, so just an observation at this time.

Has anyone had an issue with this month's Windows Updates?

 

[TheMalwareMaster]

Well, for the first time in quite a while, this month's (Jan 2026) patch Tuesday went through without a hitch on all 3 of my PCs without resorting hacking Comodo settings.

I'm not suggesting that anything has been fixed, so just an observation at this time.

Has anyone had an issue with this month's Windows Updates?

January update succeeded on 2 machines with no issues

 

[TheMalwareMaster]

Error came back on 1 machine

 

[TheMalwareMaster]

Run the update again without any folder cleaning and it succeeded... Very strange

 

[Andy Ful]

The last update installed with no problems.

 

[TheMalwareMaster]

The last update installed with no problems.

I really hope everything is solved now...