FYI Had an issue while trying to install KB5071546

[lordkilliam-dot]

Please confirm these before moving forward

• I have searched for my issue and have not found a similiar in the Open or Closed issues.
• I have tested that this issue has not been fixed in the latest (beta or stable) release.
• I have checked the Discussions section for solutions.
• This issue is about a bug (if it is not, please use the correct template).

Winhance Version

Not sure just updated. Last update in 2025 was installed.

Windows version, edition, and architecture

Windows 10 LTSC 21H2

Describe your issue

This is not a Winhance issue I think. Just want to let users know that while trying to install Windows Update KB5071546 At 92% complete I get error We couldn't complete the updates. Undoing changes. Don't turn off your Computer.

Tried a lot of suggestion on the internet and nothing worked. I had removed Edge with Winhance. I reinstalled Edge and rebooted. The update then installed. Then I removed Edge again.
Is there a way for Winhance to detect an issue like this? If this is not a Winhance issue can you add a warning so people will know this could be an issue. Keep up the awesome job and thank for a great Util.

Steps to reproduce the issue

Install Windows update KB5071546 While Edge is removed by Winhance

Expected behavior

Not sure

Actual behavior

Block update.

Screenshots or Logs (if applicable)

No response

Additional context

I know that you have away to block thing being reinstalled. Could this have blocked the update? If so can the removal be delayed and remove after the up?

[memstechtips]

Hey there and thanks for reporting this.

This might be a niche case that not a lot of people will suffer from, it might not even be related to Winhance. There won't really be any way for Winhance to detect this and then fix it.

You mentioned that reinstalling Edge made a difference and you could then install the update, but the thing is, most users know that Edge is a core component, so weird issues like that can happen.

Anyway, I'm not going to treat this as a Winhance bug that can be fixed, might just be the way Windows works.

Thanks for reporting it though :)