[Breaking News] WinRE update "KB5067040" released! Just 8 days after the previous update KB5070762, why?

Ads

January 2025, 10 January 2026, 1

Recently, a serious issue where the mouse and keyboard would not work in the Windows Recovery Environment (WinRE) was resolved by the out-of-band update KB5070773 (KB5070762 was applied internally as a WinRE update). However, Microsoft has already released a new WinRE update,KB5067040' has been released.

[Solved] Mouse and keyboard not working issue in WinRE fixed with KB5070773

This is an exceptionally fast release, just eight days after the previous fix. What's behind this? Read on for more details.

This new WinRE update (KB5067040) is compatible with the latest cumulative update (KB5067036) released on October 28, 2025, and any later cumulative update (KB10).~~Before~~) Windows Update at the same time,Install automaticallyWill be

Users do not need to download and apply the updates separately; simply by running Windows Update, the recovery environment (winre.wim) will be updated at the same time as the PC's OS.

Addendum: Subsequent testing has confirmed that installing updates from Windows Update that were released before the release date of KB5067040 will not install KB5067040.

In other words, since KB5067040 was released on October 28, 2025, it will be installed at the same time as cumulative update KB5067036 and subsequent updates released on that date.

table of contents

Consideration: Why was the new version released in just 8 days?

Previous WinRE update (KB5070762, build.6901) was just released on October 20, 2025, so why did Microsoft release the next update (KB5067040) so soon?

Officially, the reason has not been announced.

However, updating in such a short period of timeThere were some issues left to be addressed in the previous KB5070762.This strongly suggests the possibility.

KB5070762 was meant to fix the USB issue in WinRE, but maybeProblem persisted on some hardware configurationsorThis caused another problem in WinRE.(These are my speculations.)

This time, KB5067040 isIssues that occurred after applying KB5070762I suspect it was released to address another new issue.

Update contents: USB related drivers are also being updated.

When I analyzed the contents of the KB5067040 package, I found that, like the previous KB5070762, it contained a USB-related driver (which was the root cause of the problem).USBHUB3.SYSI have verified that all the components listed above are updated to newer versions.

The fact that Microsoft continues to tinker with USB-related drivers shows how deep-rooted this problem was and how it affected the entire system.

Summary

If you are using Windows 11 (24H2/25H2), when you apply the latest cumulative update (such as KB5067036) through Windows Update, it is a good idea to check whether your WinRE version has also been updated.

How to check the version of a Windows RE image and a simple tool to check it

After KB5067040 is applied, the WinRE version10.0.26100.7014It should have been updated to.

We hope that this new update will truly "completely resolve" the series of WinRE issues. If you have any changes in your environment, please share them in the comments section.

If you found this article helpful, please share it on social media.

I copied the URL!

Person who wrote this article

wenbang

Driven by questions arising from my daily PC use and the desire to "do more," I have been pursuing self-study in Windows since around 2008. I am sharing the "aha!" techniques and solutions I discovered through trial and error with the sole purpose of helping you in your PC life.

View profile

Comment:

Comment list (14)

Body Than:

2025 year 10 month 31 Date 6: 15 AM

Thank you very much for your help with the KB issue.
In my environment, this update was a different one called "Preview Update (KB5067036) (26200.7019)".
However, when I used the WinRE image version check, I was able to confirm that WinRE was the latest version (10.0.26100.7014).

Also, on a separate note, depending on the environment, it seems that in Windows 11 25H2 Explorer options, all folder options will be displayed in English.
It's on the MS website (https://learn.microsoft.com/ja-jp/answers/questions/5602101/windows11), but it's very likely that this is due to the recent KB update.

Reply
- wenbang Than:
  
  2025 year 10 month 31 Date 10: 17 AM
  
  Thank you for your comment, Mi-san.
  
  The WinRE update "KB5067040" was released at the same time as the preview update (KB5067036) (26200.7019), and if you install "KB5067036" through Windows Update, "KB5067040" will also be applied.
  
  General folder options in Explorer options are displayed in English
  Thank you for the information. I haven't confirmed this issue yet, but the additional testing I added to the page below also revealed a bug in Windows Explorer. Since KB5067036 seems to contain a variety of issues, I personally recommend uninstalling it.
  
  Win11 KB5067036 bug: "Processes remain even after closing Task Manager"
  https://windows-waza.com/win11-kb5067036-bug-processes-remain-even-after-closing-task-manager/
  
  Reply
Celi Than:

2025 year 10 month 31 Date 1: 14 AM

Dear administrator, thank you for your kind reply in the previous article. It was very helpful.

Currently, I understand that there are two WinRe-related programs: KB5070773 (optional?) and KB5067040 (automatic application). However, when I upgraded the OS and ran Windows updates,
・Select KB5070773 as an option and update
If there is a cumulative update after October 28th, KB5067040 will also be automatically distributed.
Is that correct?

After reading the comments, it seems that even if you don't select KB5070773, if you run Windows Update immediately after upgrading, the latest cumulative update (after 10/28) will be downloaded, and KB5067040 will also be included, so the WinRe version will be upgraded.

Thank you for your careful verification as always. I look forward to your future articles.

Reply
- wenbang Than:
  
  2025 year 10 month 31 Date 8: 47 AM
  
  Thank you for your comment, Celi.
  
  Thank you for your detailed analysis and questions. I really admire how you've taken the time to read the comments section and sort out the situation yourself.
  
  "Even if you don't select KB5070773, if you run Windows Update immediately after upgrading, the latest cumulative update (after October 28th) will be downloaded, and KB5067040 will also be included, so it seems that the WinRe version will be upgraded."
  That is exactly what you think.
  
  -KB5067040 will be automatically applied if you install KB5067036, released on October 28, 2025, or any subsequent cumulative update from Windows Update.
  
  Windows Update always tries to apply the latest version at that time. When Celi's PC connected to Windows Update immediately after upgrading from 23H2 to 24H2, the system skipped the old WinRE patch (KB5070773 / KB5070762) and
  
  Install the latest cumulative update (e.g. KB5067036) directly, and the latest WinRE update (currently KB5067040) will be automatically downloaded and installed along with the latest cumulative update.
  By simply running Windows Update once immediately after upgrading, any WinRE issues will be resolved with the latest version right from the start.
  
  *KB5070773 (OS Builds 26200.6901 and 26100.6901) out-of-band is no longer listed as a Windows Update option when KB5067036 (OS Builds 26200.7019 and 26100.7019) preview is released.
  
  Reply
elenore Than:

2025 year 10 month 30 Date 9: 59 PM

Good evening. Thank you for the quick information.
I don't understand very well so please ask questions

-Does this mean that KB5067040 is an update only for the recovery environment?
This update can also be downloaded from the MS Update Catalog and manually installed.
　If you do not install it, please download the preview patch KB5067036.
　Will it be installed at the same time when you apply it?
　There's an explanation...

> The latest cumulative update (KB5067036) or later (or earlier)
It will be installed automatically along with Windows Update.

　This will be updated at the same time as the monthly update 2025-10 KB5066835
　WinRE update, KB5067039. Or, if you apply KB5070773
　Does this replace the WinRE update KB5070762?
　In other words, install the 2025-10 monthly update or the out-of-band KB5070773.
　If I do this, will KB5067040 be installed?

Reply
- wenbang Than:
  
  2025 year 10 month 31 Date 12: 05 AM
  
  Thank you Eleanor for your comment.
  
  I will answer your questions in order.
  
  1.KB5067040 is an update for WinRE.
  2. KB5067040 will be automatically installed from Windows Update along with KB5067036 and any subsequent Windows Updates. If you download and install it manually from the Microsoft Update Catalog, KB5067040 will not be installed at the same time.
  3. When KB5067040 is installed, it replaces the previous version KB5070762.
  4. "So if I install the 2025-10 monthly update or the out-of-band update KB5070773, does that mean KB5067040 will also be installed?"
  
  There were some errors in the article, which have been corrected.
  
  > The latest cumulative update (KB5067036) or later (previous) → > The latest cumulative update (KB5067036) or later (previous)~~Before~~)of
  
  Subsequent testing has confirmed that installing updates from Windows Update that were released before KB5067040 will not install KB5067040.
  In other words, since KB5067040 was released on October 28, 2025, it will be installed at the same time as cumulative update KB5067036 and subsequent updates released on that date.
  
  Therefore, even if you install the 2025-10 monthly update or the out-of-band update KB5070773, KB5067040 will not be installed.
  
  Reply
  - elenore Than:
    
    2025 year 10 month 31 Date 1: 49 AM
    
    Thank you for the answer and verification
    I also tested and confirmed this in a virtual environment (VirtualBox).
    
    As of October 31, 2025, in a clean installation of Win11 24H2
    To ensure that the recovery environment is updated, please update it from Windows Update.
    Other than applying the preview patch KB5067036, there is no need to update the recovery environment.
    It seems to fail.
    Immediately after a clean install, using the standalone installer for KB5067036
    When applied, the recovery environment update fails as usual (10.0.26100.1710)
    
    I will hope (in vain?) that this will be fixed in the 2025-11 monthly update.
    
    Reply
    - wenbang Than:
      
      2025 year 10 month 31 Date 8: 58 AM
      
      Dear Elenore,
      
      I see you conducted detailed testing yourself using a virtual environment (VirtualBox). Thank you very much for your valuable and important report.
      
      The fact that "even the latest preview patch KB5067036 fails to update WinRE when installed standalone (manually) and only succeeds via Windows Update" is conclusive evidence of how deep-rooted this problem is.
      
      I will hope (in vain?) that this will be fixed in the 2025-11 monthly update.
      
      You're absolutely right. Microsoft'sManual installation does not update WinREI feel like this specification will remain the same. However, I recognize that this is a major problem. I have also proposed an improvement in the Feedback Hub, and I sincerely hope that the problem will be resolved in the future.
      
      Feedback from readers like you is our greatest asset.
      
      [Added 2025/10/31] We have proposed an improvement to this specification to Microsoft.
      
      Reply
      - elenore Than:
        
        2025 year 11 month 12 Date 7: 44 AM
        
        Today (2025/11/12), monthly patch 2025-11 KB5068861 was released.
        I immediately installed Win11 24H2 in VirtualBox.
        I tried applying it, but the result was the same and the recovery environment update failed.
        It seems that the recovery environment update is a different patch.
        What could be the cause? Will it ever be fixed?
      - wenbang Than:
        
        2025 year 11 month 12 Date 9: 00 AM
        
        Thank you Elenore for reporting this.
        
        When I install KB5068861 from Windows Update KB5070186 (WinRE update) has been applied and the WinRE version has been updated to 10.0.26100.7149.
        
        KB5068861 downloaded from the Microsoft Update Catalog does not include KB5070186, so you will need to download and manually apply KB5070186 after installing KB5068861.
        
        I have also suggested improvements through the Feedback Hub, but there has been no response from Microsoft. I think if enough users request improvements, Microsoft will respond.
since Than:

2025 year 10 month 30 Date 2: 50 PM

I followed this procedure, but errors occurred the last time and the time before that (the regular October meeting).

Regarding the tendency to get stuck at 62.3%,
I think StartComponentCleanup → RestoreHealth would be fine, but I'm not sure.

A repair install will solve the problem, but doing it every time puts a strain on the SSD.
Apparently KB5067040 causes Task Manager to proliferate? Apparently, there's a bug. I've heard it from someone else, so I'm not sure.

Reply
- wenbang Than:
  
  2025 year 10 month 30 Date 5: 12 PM
  
  Dear Siden,
  
  Thank you for the details. There may be a hidden bug in the DISM command.
  I have also confirmed the issue of Task Manager multiplication in KB5067040 in my environment, and am currently investigating it. I am not sure whether this is a bug or a feature.
  
  Reply
since Than:

2025 year 10 month 29 Date 7: 49 PM

This time, no particular errors occurred, the update went smoothly, and the WinRE version was updated to 10.0.26100.7014.
When I used a tool called MiniTool Partition Wizard to check the capacity of the recovery partition, I found that the amount of space used by the recovery partition had increased after using the patch file compared to the amount used before the update. This suggests that some remnants of the recovery partition were present. However, with this update, the amount of space used by the recovery partition has decreased even further compared to before the patch file update, so perhaps some cleanup was done. Disk Management doesn't really tell me how the recovery partition is being used.

After updating with KB5067040, I ran dism.exe /online /Cleanup-Image /StartComponentCleanup → (after rebooting) sfc /scannow, which seemed to repair the problem, so I rebooted.
After that, it said that running DISM.exe /Online /Cleanup-image /Scanhealth would allow for repairs, so I ran DISM.EXE /online /cleanup-image /restorehealth, restarted the computer, and then ran sfc /scannow and DISM.exe /Online /Cleanup-image /Scanhealth again, and there seemed to be no problem.
The steps up to this point are common, so it depends on next month's regular meeting, but I hope that next month will also go smoothly.
Maybe it's a habit from 24H2, but if I don't follow these steps, DISM.EXE /online /cleanup-image /restorehealth tends to stop at 62.3%. If I do, it will go up to 62.3%, then after about 20 minutes it will reach 100% and finish normally.
If I can update without any errors next month, I'd like to create a recovery drive for 25H2 soon.

Reply
- wenbang Than:
  
  2025 year 10 month 30 Date 8: 41 AM
  
  Thank you for your comment, Siden.
  
  Thank you very much for the very detailed and excellent test results. I'm very pleased to hear that you were able to update WinRE to the latest version (10.0.26100.7014) without any errors.
  
  How to check the recovery partition capacity
  
  This is very useful information, as Disk Management does not show what is inside the partition.
  
  1. The size of the patch file (KB5070762) on this site increased (residual files were generated)
  2. The capacity of this KB5067040 (.7014) is smaller than before the update.
  
  Based on this observation, it seems very likely that, as you say, the new KB5067040 update contained some sort of cleanup functionality to tidy up old components.
  
  Post-update maintenance procedures
  
  You performed a very careful maintenance procedure: StartComponentCleanup → sfc (repair) → ScanHealth (repair required) → RestoreHealth (repair) → recheck (no problems).
  And the information about the "quirks" of DISM /RestoreHealth in the 24H2/25H2 environment (it tends to hang at 62.3%, but if you follow certain cleanup steps it will finish normally after 20 minutes) is valuable knowledge for me and other readers. It may also be a great hint for those who are having trouble with error 0x800f0983.
  
  If I can update without any errors next month, I'd like to create a recovery drive for 25H2 soon.
  
  You're absolutely right. If I can keep my system this clean, next month's regular update should go smoothly. I hope the day comes soon when I can create the latest recovery drive with peace of mind.
  
  Thank you very much for sharing your detailed testing and valuable information (such as DISM quirks) that you can't get anywhere else.
  
  Reply