MENU
Solve your Windows problems. Support a comfortable PC life.

Mouse and keyboard not responding in Windows Recovery Environment (WinRE)? The cause is KB5067039

Ads
This article has 40 comments.

[For English Readers]

This article explains a bug where the mouse and keyboard do not work in the Windows Recovery Environment (WinRE) after a Windows Update. We provide a fully automated batch file (.bat) to fix this issue by extracting and replacing the winre.wim file from a Windows 11 ISO. Please use your browser's translation feature to read the full guide.

[Resolved] KB5070773 has fixed the WinRE issue! (Updated 10/21/2025)

The issue of mouse and keyboard not responding in the Windows Recovery Environment (WinRE) explained in this article was fixed by the Windows Recovery Environment (WinRE) released by Microsoft on October 20, 2025.Fixed completely by out-of-band (OOB) update "KB5070773".

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

▼ Microsoft official information

Windows Update screenIf you check for updates from and apply KB5070773, WinRE will work properly (WinRE version will be updated to 10.0.26100.6901).

As a result of testing in my environment,Even in environments where "winre.wim" was previously replaced using the automated batch file on this site, applying KB5070773 will fix the issue without any problems.It has been confirmed.

As a result, the "winre.wim" replacement work using the batch file introduced in this article can be done as follows:Basically it's no longer needed.(However, we will continue to keep this article up as a technical guide on how to manually update a WinRE image.)

[Regarding minor issues] During my testing, I occasionally found that when I selected "Continue" from the modified WinRE environment and restarted Windows, the keyboard would sometimes stop responding on the sign-in screen.Unplug and plug in the USB keyboard.This solved the problem. This problem did not occur when restarting normally.

We would like to express our sincere gratitude to Microsoft for their prompt response to the fix and to our readers who provided information and cooperated in verifying the issue.

【2025/10/21 postscript】According to valuable reports from readers, there are cases where, even after installing KB5070773 via Windows Update, the WinRE version remains old (10.0.26100.6891), and the mouse and keyboard unresponsiveness issue persists.

I have also observed a similar phenomenon in some environments.

[Troubleshooting] If the WinRE version does not change even after applying KB5070773

For those of you using Windows 11 version 24H2 and 25H2, have you recently been experiencing problems with your PC, such as your mouse and keyboard suddenly becoming unresponsive in the Windows Recovery Environment (blue screen) that you use when you encounter problems?

Recently, we received an inquiry from a user of our website about exactly this issue: "The mouse won't work in the recovery environment." After investigating, we discovered that a specific update was the cause.

This is a very troublesome issue where the computer works fine in normal mode but the recovery environment is not available. We will explain in detail the cause and how to deal with this issue.

Background to this article: A reader's report

Our investigation into this issue began on the evening of October 15, 2025 (17:50) when we received an inquiry from an avid reader of our site reporting that "the mouse doesn't work in the recovery environment."

I immediately started investigating and determined that this was not a problem with my personal environment, but a serious problem caused by Windows Update.The next morning (October 16, 2025, 4:14 AM)There are hidden updates that don't appear in the update history."KB5067039" is the direct cause of the problemWe have identified the issue and responded to the user who reported it.

(Further investigation has since identified the root culprit as a driver file called "USBHUB3.SYS" included in this update.)

This article summarizes the results of our investigation and has been published urgently to help more people solve this problem.

[Updated 10/19/2025] Microsoft has officially acknowledged this issue.

On October 17, 2025, Microsoft officially acknowledged the WinRE issue and announced that they are currently working on a fix, which is expected to be released soon.

▼ Microsoft's official announcement page
https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2#3696msgdesc

In the meantime, if you urgently need to operate the recovery environment, please consider the solutions described in this article.

table of contents

Problem summary: Mouse and keyboard don't work in recovery environment!

  • Symptoms:
    • On a Windows 11 version 24H2/25H2 PC, when you select "System" > "Recovery" and then select Advanced Startup (to start the recovery environment) or restart while holding down the Shift key, a blue screen (Windows Recovery Environment) will be displayed.
    • On this screen, the USB-connected mouse and keyboard become completely unresponsive and cannot be operated.
    • The mouse and keyboard work fine in normal mode, safe mode, and the BIOS/UEFI settings screen.
  • Affected PC:
    • Running Windows 11 versions 24H2 and 25H2device.

If the mouse and keyboard become unresponsive in the recovery environment, press and hold the power button to shut down the system. This will not affect the system as Windows has not yet started.

  • Recovery environment is a separate system: The Windows Recovery Environment (WinRE) runs on a lightweight, independent OS (based on Windows PE) that is separate from the Windows we normally use.
  • Less impact on system filesIn the recovery environment, no important processes such as writing to normal Windows system files are performed unless you select special operations such as system restore or repair.

Therefore, even if you force quit when it freezes in the recovery environment,It is highly unlikely that normal Windows startup or data will be affected..

postscript:Furthermore, according to valuable information from users, the USB mouse and USB HDD will also not be recognized if the system is started using rescue media (such as a USB memory stick) created using various backup software.

This is because many rescue media creation tools use the WinRE currently installed on your PC as a base, so if the WinRE on your PC itself is affected, the problem will be inherited by the rescue media created from it.

This issue is caused by a specific update

After some investigation, we discovered that the cause of this annoying issue was a specific update, KB5067039, quietly released by Microsoft.

  • Update Name: KB5067039: Secure OS Dynamic Updates for Windows 11 Versions 24H2 and 25H2 and Windows Server 2025: October 14, 2025
  • The tricky part:
    • This update does not appear in the Reliability Monitor or Windows Update Update History, making it difficult for users to determine when it was installed.
    • This is a type of update that is applied automatically to your system.

[Supplementary Information] How to check if WinRE has been updated using Event Viewer

You can see traces of this "silent update" in the Event Viewer.

  1. Press Windows Key + R to open Run, type "<your name>" and press Enter to launch the Event Viewer.
  2. From the tree on the left, select "Windows Logs" > "System".
  3. Click "Filter Current Log" from the actions menu on the right.
  4. Find "WinREAgent" in the "Event Source" drop-down menu and check it.
  5. In the field that says "<All Event IDs>", enter "4501" and click OK.
Filter the current log
Filter the current log

This will only show logs when WinRE is updated. If you find a log with Event ID 4501, it means your PC's WinRE has been updated automatically.

Event viewer
Event viewer

Relationship between WinRE version and bugs

After detailed investigation, this defectThis only occurs in certain versions of Windows Recovery Environment (WinRE).I have confirmed that.

  • Affected WinRE versions:10.0.26100.6891
    • When this version is installed on a device, the mouse and keyboard will become unresponsive in the recovery environment.
  • WinRE versions that do not exhibit the issue:
    • 10.0.26100.6713 (previous version)
    • 10.0.26100.5059 (at the moment Windows 11 25H2 ISO (The version included in
    • The mouse and keyboard work fine on these versions.

By applying KB5067039, the version of WinRE is 10.0.26100.6891 was updated toAccording to the official page for this update, the USB driver has also been updated.この Inconsistent or missing USB driversHowever, this may be causing the mouse and keyboard to malfunction.

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

The Windows Recovery Environment (WinRE) is an important feature that can be considered the "last resort" for repairing your system when a serious problem occurs, such as your PC not starting up.

However, if the mouse and keyboard stop working in the recovery environment, how can users repair their PC? Even though important options for emergencies such as "System Restore" and "Startup Repair" are right in front of them, they are left in a hopeless situation where they cannot select anything.

It's understandable that users would be concerned that a bug affecting such important functionality would be automatically updated without their knowledge.

How to fix this issue

Currently, there are two possible ways to fundamentally resolve this issue:

Solution 1: Revert Windows RE Image (winre.wim) to a Previous Version

This method allows you to restore the WinRE image file to a previous version (10.0.26100.6713 or sending us a message on 10.0.26100.5059) to be manually replaced.

【important point】

This operation directly handles system files, so it is not recommended for those who are not familiar with PC operation. Incorrect operation may cause the system to become unstable or unable to boot. If you choose to perform this operation, please proceed with caution and at your own risk.

The specific steps are as follows:

  1. Previous version of the Windows RE image (winre.wim) file,Windows 11 25H2 ISO Get it from.
  2. Open a command prompt with administrator privileges and disable WinRE.reagentc /disable
  3. Current winre.wim Replace the file with the previous version you have obtained (usually C:\Windows\System32\Recovery folder)
    • Disabling WinREC:\Windows\System32\Recovery In the folderwinre.wimappears. (隠しファイル）
  4. Re-enable WinRE.reagentc /enable
    • When you enable WinRE,C:\Windows\System32\Recovery In the folderwinre.wimwill disappear.
  5. Reboot your PC and check if the mouse and keyboard work in the recovery environment.

[Additional Note] Automated batch file to easily replace winre.wim

Solution 2: Wait for Microsoft to release an official patch

Since this issue is caused by a Microsoft update, it's likely that Microsoft will acknowledge the issue and release a fix in the future.

  • If you don't have an urgent need to interact with the recovery environment, the safest course of action is to continue using your PC as normal and wait for an official fix to be made available through Windows Update.
  • Microsoft typically tends to release fixes quickly for critical bugs like this.

10/17/2025: Microsoft acknowledged the issue and said they are working on releasing a solution to resolve the issue soon.

postscript:Workaround: Use a PS/2 keyboard, mouse, or touchpad

This is also very useful information received from our users.

Because this issue is caused by a USB-related driver, older keyboards and mice connected via PS/2 connectors, as well as laptop touchpads, may not be affected and may work normally.

If you have a PS/2 keyboard and mouse at home, you can use them to temporarily operate the recovery environment.

If you want to enter safe mode

If you need to enter Safe Mode for some reason, you can do so by enabling the "Advanced Boot Options" described on the next page.

[Bring back the old F8 key] Steps to start Safe Mode in Win11/Win10

Summary

The issue of the mouse and keyboard freezing in the Windows Recovery Environment is a known issue caused by a specific Windows Update program.

If you urgently need to operate the recovery environment, you may need to manually downgrade the WinRE image, but the safest option is to wait for an official fix from Microsoft.

If you encounter this problem and are unsure, do not try to operate it yourself, but consult someone knowledgeable about PCs or an expert.

This issue has been reported to Microsoft

We reported this mouse and keyboard issue in the Windows Recovery Environment to Microsoft's Feedback Hub on October 16, 2025. We hope that Microsoft will investigate the issue and release a fix as soon as possible.

[Additional Note] When and how will KB5067039 be applied?

When exactly will this "quiet update" be applied? Our testing revealed that "KB5067039" will be automatically applied when installing a cumulative update (e.g., "KB5066835") from October 14, 2025 onward.

Specifically, we verified the following:

  1. First, uninstall "KB5066835" in a test environment.
  2. Next, update the version of the Windows RE image (winre.wim) to a previous version that does not have the problem. 10.0.26100.6713 Manually return it to
  3. In this state, install "KB5066835" again.
  4. As a result, the version of the Windows RE image is:The problem occurs again 10.0.26100.6891 It has been updated to.

This shows that "KB5067039" is being forcibly applied in the background during the process of applying monthly updates such as "KB5066835."

According to official information from Microsoft, this update will be automatically synchronized through WSUS (Windows Server Update Services) if configured as follows, and this appears to be how it will be applied at the same time as cumulative updates.

Category: NEW

For Windows 11 versions 24H2 and 25H2

product: Windows 11

Category: NEW

For Windows Server 2025

product: Microsoft Server Operating Systems – 24H2

Uninstalling KB5066835 will not restore the version of your Windows RE image (winre.wim). Microsoft states on its official website that "Once this update has been applied to a Windows image, it cannot be removed."

Solution 1: Revert Windows RE Image (winre.wim) to a Previous Version

【postscript】Automated batch file to easily replace winre.wim

To resolve this recovery environment issue more easily and safely, we created a batch file that semi-automatically extracts "winre.wim" from the Windows 11 ISO file and replaces it with the file on the system.

This tool is

  • Automatically back up the current "winre.wim"
  • Extract the correct "winre.wim" from the ISO file
  • Safely overwrite system protected files

This automates the above steps, which may be a little difficult for those who are not familiar with command operations. I have actually tested it in my environment and confirmed that it works without any problems.

【重要】 This batch file modifies important system files. To prevent unexpected problems,Please be sure to read the steps in the article carefully and follow them at your own risk.

What is a batch file? How to create and run a batch file

Advance preparation

What you will need (please prepare in advance):

⚠️ Notes for environments with BitLocker/Device Encryption enabled

If your PC's C drive is protected by BitLocker or device encryption, the last step in the batch file, "Re-enable WinRE (reagentc /enable)" may result in an error.

The surest way to prevent this is toBefore running the batch file, temporarily disable (decrypt) BitLocker (or device encryption) completely.It is that.

[Important] Points to note when completely decrypting

After running the batch file,When you re-enable BitLocker, a new recovery key will be generated. Be sure to back up the new recovery key in a safe location.please.

  1. Download the Windows 11 ISO file.20GB or more free spaceSave it in any folder.
  2. Download and install 7-zip.
  3. Place the batch file in the same location as the Windows 11 ISO file.

During the process, this batch file temporarily extracts a large file of several GB called a Windows installation image (e.g., "install.wim").

Therefore, on the drive where you placed the batch fileAt least 20GB of free spaceIf there is not enough free space, the process may fail midway.

What's taking up space? How to find the culprit in Windows 11 Storage Settings

Download the batch file

* Regarding use of the software (please read carefully)

Target file: "WinRE image extraction and application tool.bat"
ハッシュ値(SHA256):89549edc14838c362828a93670f0260b540ad1773a3718d735de0909e5e7926f

WinRE image extraction and application tool.zip

Once you download the batch fileUnzipThen place the "WinRE Image Extraction and Application Tool.bat" file in the same location as the Windows 11 ISO file.

English version:

Target file: "WinRE_Repair.bat"
ハッシュ値(SHA256):acd9d6c7b3e9a7661e97fe472caec2f0f3c008a540f01317531143c77afa2c6b

WinRE_Repair.zip

Please change the following part of the batch file to suit your environment.

:: =============================================================================
:: 2. 設定値 (ここをあなたの環境に合わせて変更してください)
:: =============================================================================
SET "ISO_FILENAME=Win11_25H2_Japanese_x64.iso"
SET "SEVENZIP_PATH="

Win11_25H2_Japanese_x64.iso is the name of the ISO file.

You don't usually need to modify the SET "SEVENZIP_PATH=" part. Modify it only if you have saved "7z.exe" in an unusual location.

Contents of the batch file and how to use it

1. Double-click the batch file to start it.

2.The "User Account Control" message will appear, so click "Yes".

ユーザーアカウント制御
ユーザーアカウント制御

3. A command prompt will appear and the settings will be displayed.

  • ISO files: ISO ファイル名
  • Working folder: バッチファイルが置かれているパス
  • 7-Zip execution path: C:\Program Files\7-Zip\7z.exe
command prompt
command prompt

Pressing Enter here will perform the following actions:

4.step 1: Mount the ISO and display the Windows edition information as shown below.

インデックス: 1
名前: Windows 11 Home
説明: Windows 11 Home
サイズ: 22,689,601,389 バイト

インデックス: 2
名前: Windows 11 Education
説明: Windows 11 Education
サイズ: 23,636,557,841 バイト

インデックス: 3
名前: Windows 11 Pro
説明: Windows 11 Pro
サイズ: 23,659,047,210 バイト

5.step 2:抽出したいWindowsエディションのインデックス番号を入力してください:This will prompt you to enter the index number of the edition you are using and press Enter.

command prompt
command prompt
If you don't know which edition you have:

1. Right-click on the Start button and click "Terminal".

2. Type the following command and press Enter:

(Get-CimInstance -ClassName Win32_OperatingSystem).Caption

This will show you the current edition.

Windows PowerShell
Windows PowerShell

6.Step 3 ~ Step 4:This will automatically begin extracting the Windows image from the ISO file using 7-zip.

*"install.wim (or install.esd)" and "Winre.wim" will be extracted.

7.step 5:When the extraction is complete,抽出したwinre.wimを現在のシステムに適用しますか？ (自己責任で実行してください) [Y,N]?So I was asked,To replace, enter "y","n" if you don't want to replace itPlease enter

8. If you do not want to replacestep 6:Delete the unnecessary temporary file "install.wim (or install.esd)".

To replace it, do the following:

  1. Disable WinRE.
  2. Create a "Backup" folder and back up the current version of "Winre.wim".
  3. Overwrite the current "Winre.wim" with the extracted "winre.wim".
  4. Re-enable WinRE.
  5. step 6:Delete the unnecessary temporary file "install.wim (or install.esd)".

▼This video is a demonstration video showing how the batch file actually works.

[Updated 10/20/2025] The root cause has been discovered! The culprit was "USBHUB3.SYS"

I have been investigating this issue for a while now, and I have finally found the cause of the mouse and keyboard not working in this recovery environment.Root causeWe have identified the following.

The cause was the "USBHUB3.SYSIt was a single driver file called ".

When KB5067039 is applied, this "USBHUB3.SYS" is replaced with a new version (10.0.26100.6891) that contains a bug, which is the direct cause of disabling the mouse and keyboard.

USBHUB3.SYS Properties
USBHUB3.SYS Properties

Verification: Reverting USBHUB3.SYS to an older version works fine

To prove this hypothesis, we manually replaced only "USBHUB3.SYS" in the WinRE image with the older version (10.0.26100.1) that was working properly, using the following steps:

  1. Disable WinRE: reagentc /disable to disable the current recovery environment.
  2. Mounting the WinRE image: Use the DISM command:C:\Windows\System32\RecoveryMount (extract) "Winre.wim" in the location to a temporary folder.
  3. Replacing "USBHUB3.SYS": In the mounted folder Windows\System32\drivers The problematic "USBHUB3.SYS (version 10.0.26100.6891)"Overwrite with the correct old version (10.0.26100.1) file international success.
  4. Unmount the WinRE image: Save (commit) the changes and unmount "Winre.wim".
  5. Enabling WinRE: reagentc /enable to re-enable the repaired recovery environment.

As a result, when I started the recovery environment,I have confirmed that the mouse and keyboard work fine.

This verification reveals that"USBHUB3.SYS" is the direct cause of the problemIt has been confirmed.

The automated batch file provided on this website will replace the entire "Winre.wim" with a correct one, which is a fundamental solution to this issue. It is likely that the official fix from Microsoft will also involve modifying "USBHUB3.SYS."

What is USBHUB3.SYS?

The root cause of this issue is "USBHUB3.SYS." Microsoft's official documentation describes its role as follows:

USB hub driver (Usbhub3.sys)

The new hub driver, in the USB driver stack for 3.0 devices, uses the KMDF driver model. The hub driver primarily performs these tasks:

  • Manages USB hubs and their ports.
  • Enumerates devices and other hubs attached to their downstream ports.
  • Creates physical device objects (PDOs) for the enumerated devices and hubs.

Windows loads the hub driver as the FDO in the hub device stack. Device enumeration and hub management in the new driver are implemented through a set of state machines. The hub driver relies on KMDF for power management and PnP functions. In addition to hub management, the hub driver also performs preliminary checks and processing of certain requests sent by the USB client driver layer. For instance, the hub driver parses a select-configuration request to determine which endpoints will be configured by the request. After parsing the information, the driver hub submits the request to the USB host controller extension or further processing.

https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-3-0-driver-stack-architecture

To put it simply, "USBHUB3.SYS" plays an extremely important role, like a "manager" or "traffic controller" for all USB 3.0 ports.

Main task of USBHUB3.SYS

According to Microsoft, the main duties of this "Manager" are as follows:

Job Description (Microsoft explanation)An easy-to-understand example (the manager's job)
Manage USB hubs and their portsManages the building floors (hubs) and the doors (ports) for each room.
Enumerate devices connected to a portWhen a new guest (USB device) arrives, the identity is confirmed and the guest name is registered (listed) in the guest list. The system is notified that "Mr. Keyboard, you have arrived."
Create a PDO for the enumerated deviceA room key (ID called PDO) is issued to each registered guest (USB device), allowing the system to recognize the guest as an individual and to communicate with them.
Processes and forwards requests from client driversReceives requests from customers (such as mouse drivers) such as "I want hot water," checks the details, and gives precise instructions to the person in charge in the boiler room (controller driver).
What if there is a problem with this "manager"?

The problem this time was caused by a serious bug in the "Manager (USBHUB3.SYS)" itself.

  • Unable to register guests (enumeration failure): The manager is dysfunctional, so when a new guest (mouse or keyboard) arrives, he is unaware of their presence and is unable to register (enumerate) them on the guest register.
  • Unable to issue a room key (Failed to create PDO): Since you cannot be registered in the list, naturally the room key (PDO) will not be issued.

As a result, to the system (Windows), the mouse and keyboard were considered "guests who don't exist in this building." So no matter what I plugged into the USB port, the cursor wouldn't move and no keystrokes were accepted.

As you can see, "USBHUB3.SYS" is not just one of the components, but is the software that enables the system to recognize USB devices.The first hurdleThis is the most important role. If this manager were to malfunction, it would naturally result in the halt of all USB communication beyond that point.

Reporting this to Microsoft and what you can do to expedite the fix

We have officially reported this Windows Recovery Environment issue to Microsoft's Feedback Hub, along with detailed verification results.

Initially, I tried to post a shared link to ask for upvotes, but in my environment, the link was generated exclusively for Windows Insider Program participants, and I found that many people were unable to access it.

We apologize for any inconvenience caused.

The report itself has been received by the relevant Microsoft team, so please wait for an official fix in the future.

2025/10/21[Important Note] Repairing from installation media and the "traps" that lurk there

Many readers have said,media creation toolWe have received reports that "if you boot from the USB memory created in the above, you can use the recovery environment without any problems."This is completely correct and is a valid workaround.

Why can it be used by booting from USB media?

The reason is that there are two types of "recovery environments" that your PC can boot into.

  1. PC recovery environment: It is located on the PC's HDD/SSD and uses "winre.wim". This is installed by Windows Update.It's contaminated with a broken version.
  2. Installation media recovery environment: It is stored on the USB memory and uses a different image called "boot.wim".

When you boot your PC from USB (USB boot), the corrupted recovery environment (winre.wim) on the PC itself is not used at all, and instead an independent small repair OS (boot.wim) on the USB memory stick is started. This is why the mouse and keyboard work normally.

[Warning] Media Creation ToolIn the USB created byDo not use the winre.wim included in

But there's a very important catch here.

The author actuallymedia creation toolWhen we checked the ISO file downloaded, we found that the version of "winre.wim" contained in it was 10.0.26100.6891, which is a problematic version.

In other words, this USB media is "bootable and usable"There is no problem for a moment, but if you try toIf you try to copy it and use it to repair your PC, you will end up installing the same bug on your PC.

*The "winre.wim" included in the ISO file downloaded directly from the official page is fine.

How to download Windows 11 ISO files

10/29/2025: The Windows 11 Media Creation Tool was updated to the new version 10.0.26100.7019 on 10/28/2025, but we have confirmed that the version of "winre.wim" included in the ISO file remains the problematic 10.0.26100.6891.

Summary

way to executeImages usedResult
USBブート"Repair your computer""boot.wim"OK 👍
Copy "winre.wim" from the ISO to your PC"winre.wim"NG 👎 (Bug)

Therefore, until the official patch is released by Microsoft, to fundamentally repair the recovery environment of the PC itself, please use the method explained in this article.Automation Batch FileThe most reliable method at present is to use the "winre.wim" command to apply a version of "winre.wim" that is confirmed to work properly.

Windows Windows Bug Information troubleshooting Development and Software System Issues Software / Homemade software Device Issues Programming / Batch files Security
If you found this article helpful, please share it on social media.

Person who wrote this article

wenbang's avatar 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 (40)

  • Thank you for your help.
    Being a computer novice, I didn't know what to do so I searched and ended up here.

    I used my computer last Friday and shut it down, and when I turned it on Sunday, the Bitlocker message popped up. I had the same thing happen last year, so I have the recovery key written down, but when I try to enter it, neither the Bluetooth keyboard nor the mouse work.

    The next day, I spoke to the support chat (operator) of the F manufacturer I use, but the problem was not resolved. I was told that I needed a recovery drive and that I would have to purchase a recovery USB for a fee, and that if I could not provide either, they would have to take it to the factory. If I use the method recommended by the manufacturer, all my data will be lost, right?

    By the way, I was able to check the operation while chatting, and the diagnostic results showed no mechanical problems. The BIOS screen was displayed and keyboard operation was possible, but when I shut down and restarted the computer, the Bitlocker message appeared. Also, although I was able to get to the option selection screen in the Windows recovery environment, the keyboard and other components were inoperable. I also tried using a wired keyboard and mouse, but they were inoperable.

    I'm afraid that if things stay like this, it will become unusable and all of my data will be lost because it's not managed in the cloud.

    Reply

    • Thank you Mint for your comment.

      It's a really difficult situation. You say you're a "computer novice," but suddenly the BitLocker screen pops up, and your keyboard and mouse won't work... I understand all too well how scared you are that all your data will be lost.
      First of all, please rest assured that your PC is not physically damaged, and there is still a chance that we can restore your PC without losing any data.

      What's happening now?
      What Mint is experiencing is two problems that have come together at the worst possible time.

      1. Problem A (BitLocker): For some reason, your PC is asking you to enter your BitLocker recovery key.
      2. Problem B (WinRE bug): However, on the screen where you enter the recovery key (which is also a type of recovery environment), the keyboard and mouse stopped working.

      In order to protect your data, you will need to try the only way to repair your PC by bypassing the broken system on the PC itself, by using the Windows 11 installation media (USB memory) from an external device.

      [Procedure summary]

      [Most Important] Creating installation media:
      (If you already have Windows 11 installation media (USB memory), there is no need to create installation media.)

      We apologize for the inconvenience, but this procedure requires another working PC (a PC with administrator privileges belonging to a family member or friend).

      On another PC, download the media creation tool from the official Microsoft website and create a "Windows 11 installation USB memory stick" on a USB memory stick with at least 8GB of free space.

      (Detailed instructions are provided in another article on this website.)https://windows-waza.com/win11-media-creation-tool-mediacreationtool_win11_23h2/

      Boot your PC from the USB stick:

      Connect the created USB memory to the PC in question.
      Turn on your PC and immediately press a specific key (e.g. F12, ESC, F2, etc.) to bring up the boot menu and boot from the USB flash drive.

      Reference: Booting the PC from the installation media
      https://windows-waza.com/how-to-perform-a-clean-install-or-overwrite-install-repair-of-windows-11/#index_id7

      Select "Repair your computer":

      You will (probably) be asked to enter your BitLocker recovery key (48 digits), so enter the recovery key you have on hand on your keyboard to unlock the drive.

      1. When the Windows 11 setup screen (language selection) appears, click "Next".
      2. Click "Next" on the keyboard selection screen in the same way.
      3. On the Setup Options screen, click Repair your PC.
      4. Select "Microsoft IME" as the keyboard layout.

      Run the repair option:

      This will boot into the normal recovery environment (WinRE) on the USB flash drive. Since it's not the corrupted WinRE on the PC, you should be able to use the mouse and keyboard.
      On the blue "Choose an option" screen, go to "Troubleshoot" -> "Advanced options" and try running "Startup Repair" first.

      If Startup Repair fails, try System Restore next.

      Reference: How to create, restore, and delete a system restore point (select a restore point from a time shortly before the problem occurred)
      https://windows-waza.com/systemrestore/

      Since you say you're a "computer novice," I understand that these steps are very difficult and may seem intimidating. If you're unsure about doing it yourself, I strongly recommend that you don't force yourself, and instead ask a friend or family member who knows a lot about computers to help you by showing them this reply (or the steps in this article).

      The manufacturer's "factory reset" is a last resort that will erase all your data. Before that happens, we sincerely hope that this "system restore using installation media" will help you save your PC and your important data.

      If you are able to recover the data, we recommend that you repair your system files by referring to the following page.

      Repairing system files in Win10/Win11 with "System File Checker"
      https://windows-waza.com/windows-10-sfc-scannow/

      Reply

      • Thank you for your reply.
        I never expected two of the worst situations to come together.

        I'm sorry for asking again.
        When I purchased my computer, the store asked me to create a recovery system USB, so I did, but since it's 2021, I think it's probably Windows 10. Since the installation media you suggested is for Windows 11, does that mean I can't use the media I have, and if I don't have it, I'll have to ask someone with a different PC to create it for me?

        Taking it to the factory is the last resort, so I'll try my best using the method you taught me.

        Reply

      • Thank you for your quick reply.
        I never expected that two of the worst things would happen at the same time.

        Please let me ask the question again.
        When I purchased the computer, I was asked to create a recovery USB drive at the store, so I probably have the Windows 10 version. Will I need to use it this time?

        Would it be best to create a Windows 11 installation USB as instructed? I don't have any friends with personal computers at the moment, so this will likely take a lot of time.

        Reply

        • Dear Mint,

          Thank you for your reply. I will do my best to support you, Mint, who is looking forward and saying, "I want to do my best" in a truly difficult situation where "two of the worst things have happened at once."

          [Question] Should I not use the recovery USB (probably Windows 10) that was created when I purchased the computer?

          Yes, that question is very important. The answer is, do not use that USB memory for this repair.

          [Reason] The "Recovery System USB" created by the store when Mint purchased his PC is likely intended to restore his PC to its factory settings (at the time of purchase). If he were to use it, it could result in his greatest fear: losing all of his data.

          Also, the media is for Windows 10. To safely repair your current Windows 11 system (using System Restore, etc.), the safest option is to use the Windows 11 repair function that matches your OS version.

          [Question] Would it be best to create an installation USB with Windows 11 as instructed?

          Yes, that's correct. This is the only and best way to boot into a working recovery environment with keyboard access and preserve your Mint data. (You can also create an installation USB on a Windows 10 PC.)

          I don't have any friends who have personal computers at the moment, so this is where I'll probably spend most of my time.

          I understand how you feel all too well... The biggest challenge with this problem is "how to prepare another PC."
          If you can't ask a friend, it must be really difficult. If possible, please try using your work PC (with permission from your IT administrator), or
          Alternatively, if you can, you could ask your local PC repair shop if they could just create a Windows 11 USB stick using the media creation tool, and inquire about the cost.

          Reply

          • Thank you for your help.
            Thank you for your second comment.

            Yesterday I was lucky enough to be able to create installation media from my husband's PC when he's at home.
            I followed your instructions today, but step 1 of booting the PC from the USB memory (installation media)
            I'm having trouble with booting from a USB drive. I set the USB drive to be first in the boot order in the BIOS settings. After restarting, I get the message "Your device ran into a problem and needs to start.0% complete."
            It showed 100% for a moment, then it showed "Automatic repair in progress" for a moment, but it didn't say "Press any key to boot from CD or DVD..." Then it showed "BitLockr".

            The keyboard and mouse that came with the PC still don't respond, so the wired keyboard doesn't respond either.
            The hub has three ports, so I changed all of them and tried connecting a USB memory stick and a wired keyboard, but nothing worked.

            By the way, even when I start the computer without inserting a USB flash drive, the message "Automatic Repair" appears for a moment and the "BitLocker" message appears. In other words, the same thing happens whether I insert the flash drive or not. Is it because the USB port is not responding?

            Could it be that the BIOS settings are different? (My PC is a Fujitsu.)
            Boot Device Priority
            Startup menu [Use]
            Boot from removable media [Use] ← This time I set this to [Use].
            Numlock setting at startup [Use]
            Error stop at startup [Use]
            IPu4 Network Startup [Use]
            IPu6 Network Startup [Use]
            TPM (security chip) settings
            Event Log Settings

            Sorry for the long message.
            I am unable to do this using the above method, so I would appreciate it if you could give me instructions again.

          • Thank you for your detailed report, Mint. I appreciate your hard work creating the installation media. It can be frustrating when you get stuck on the first step.

            I have read the information you provided. The important point is that the same reaction (automatic repair → BitLocker) occurs whether or not the USB memory is inserted.

            This indicates that the PC is not recognizing the USB memory as a boot device and is trying to boot from the internal hard disk (SSD) as usual. However, because Windows on the internal hard disk (SSD) is corrupted, an error message appears saying "Your device ran into a problem...", and the PC attempts automatic repair, eventually stopping at the BitLocker screen.

            The reason why "Press any key to boot from..." is not displayed is because the PC has not even attempted to boot from the USB memory.
            The most likely cause is that the BIOS settings are not complete or the "Boot Menu" is not operational.

            We will suggest the easiest and most reliable method.

            Call the Boot Menu directly (F12 key)

            BIOS settings (changing the boot order) are complicated, and even if the settings are correct, they may not work properly. First, try using the "Boot Menu," which allows you to select "which device to boot from" only once at startup.
            For Fujitsu PCs, this is often the F12 key.

            1. Make sure your PC is completely turned off.
            2. Plug the wired keyboard and the USB installation media you created directly into the USB port on your PC (do not use a hub).
            3. Turn on your PC.
            4. Immediately after turning on the power, press the "F12" key repeatedly (keep pressing it repeatedly) while the Fujitsu logo (FUJITSU) is displayed.
            5. If this is successful, you will see a screen titled "Boot Menu" or "Select Boot Device".
            6.The name of the inserted USB memory stick (e.g., "USB HDD: [Manufacturer Name]" or "Removable Device") should be in the list.
            7. Use the arrow keys (↑↓) on the wired keyboard to select the USB memory and press Enter.

            If this is successful, it will start booting from the USB memory stick and you should see the message "Press any key to boot from..."

            If not successful

            What can be considered is

            1. The installation media (USB memory) you created is damaged
            2. (More likely) Your PC hardware (SSD, HDD, or motherboard) is physically failing.

            のどちらかです。

            In case 1, you can solve the problem by recreating the file, but in case 2, unfortunately, it is difficult to solve.

            In this situation (even USB booting fails), we recommend that you stop immediately, as continuing to operate the device yourself carries a very high risk of losing all your data.

            Two options left (both involve hiring an expert):

            Mint-sama has a very tough choice to make, but there are only two options left.

            Option 1: Request repair from the manufacturer (Fujitsu)

            Content: As the operator previously said, it will be "kept at the factory."

            merit: Your PC will be repaired and ready to use again.
            Disadvantages (very important): The manufacturer's standard repair method is to initialize (factory reset) the PC. As Mint fears, all data on the PC (that has not been backed up) will almost certainly be erased.

            Option 2: Hire a data recovery specialist (if your data is more important than your PC)

            Details: This company does not repair PCs, but specializes in retrieving data from them.

            merit: It may be possible to retrieve data even from a PC that the manufacturer has told you will lose all data during repairs.
            Demerit: It is very expensive (it can cost tens of thousands to hundreds of thousands of yen).

            After the data has been extracted, the PC itself will need to be repaired separately (such as by requesting the manufacturer).

            My suggestion

            If the data that was not stored in the cloud is so important that you are determined to get it back even if it means damaging your PC, we recommend that you do not send it in for repairs from the manufacturer, but rather consult a nearby data recovery specialist.
            If you are willing to give up on your data and just want to get your PC back to a usable state, the only option is to request repairs from the manufacturer (Fujitsu).

            This is a very difficult situation, but we sincerely hope that Mint will be able to make the best decision.

  • Thank you for your help.

    I'm having trouble understanding computers at all.

    I was searching around for something about this and ended up here.

    There was an update a few days ago, just before I turned off my PC, so the next day after the update, I was taken to a screen that looked like the initial settings, signed in, synced, pressed start, and when I started, my email (Outlook) and picture images were gone.I was able to recover the email by finding it in another location, but I couldn't figure out where the pictures had gone, so I panicked and pressed the go back button in system recovery to go back to before the update.

    Then, after rebooting, I got the message "Device could not be automatically repaired" repeatedly. I can't use the mouse or keyboard.

    I have a wireless mouse and wireless keyboard, and it's not urgent, so would it be okay to wait for an official fix?

    Reply

    • Thank you for your comment, Sui.

      And it's a really, really difficult situation. You don't know anything about PCs, your files disappear after an update, and when you try to repair it, it goes into a boot loop, and on top of that, you can't use the mouse or keyboard... I know all too well how you must have panicked.

      Let me explain in order what happened on SUI's PC.

      Issues after Windows Update:After the update, you were signed in with a "default screen." This is likely because Windows started up with a temporary profile. This is why you can no longer see the usual "Pictures" folder, etc. (The data itself is likely still on your PC.)
      Recovery operations and boot loops:You panicked and clicked the "System Recovery" button because your data was lost. This was the right decision. However, it seems that the recovery process failed for some reason, and your PC is stuck in a boot loop with the message "Automatic Repair Failed."
      WinRE inoperable (fatal):And due to the bug in KB5067039 (the update that was updated at the same time as KB5066835) that is explained in this article, my wireless (via USB dongle) mouse and keyboard stopped responding on the repair screen (WinRE)...

      It's truly a checkmate situation, with multiple misfortunes coming together.

      [Question] Is it okay if I wait for an official fix?

      This is the most important point. SUI says that it is not urgent, but I am sorry to say this, but this time it is highly unlikely that the problem will be resolved by simply waiting.

      • [Reason] Microsoft has already released a patch (KB5070773) to fix this WinRE issue, but the patch must be installed through Windows Update on a system that runs Windows normally.

      SUI's PC is currently in a state where Windows will not start (automatic repair loop), so he is unable to connect to the Internet to receive the patch.

      [Important] The only solution to this situation

      There is only one way to escape this vicious cycle: to use the Windows 11 installation media (USB memory) externally to bypass the broken system on the PC itself and repair it.

      [Procedure summary]

      [Most Important] Creating installation media:
      (If you already have Windows 11 installation media (USB memory), there is no need to create installation media.)

      We apologize for the inconvenience, but this procedure requires another working PC (a PC with administrator privileges belonging to a family member or friend).

      On another PC, download the media creation tool from the official Microsoft website and create a "Windows 11 installation USB memory stick" on a USB memory stick with at least 8GB of free space.

      (Detailed instructions are provided in another article on this website.)https://windows-waza.com/win11-media-creation-tool-mediacreationtool_win11_23h2/

      Boot your PC from the USB stick:

      Connect the created USB memory to the PC in question.
      Turn on your PC and immediately press a specific key (e.g. F12, ESC, F2, etc.) to bring up the boot menu and boot from the USB flash drive.

      Reference: Booting the PC from the installation media
      https://windows-waza.com/how-to-perform-a-clean-install-or-overwrite-install-repair-of-windows-11/#index_id7

      Select "Repair your computer":

      1. When the Windows 11 setup screen (language selection) appears, click "Next".
      2. Click "Next" on the keyboard selection screen in the same way.
      3. On the Setup Options screen, click Repair your PC.
      4. Select "Microsoft IME" as the keyboard layout.

      Run the repair option:

      This will boot into the normal recovery environment (WinRE) on the USB flash drive. Since it's not the corrupted WinRE on the PC, you should be able to use the mouse and keyboard.
      On the blue "Choose an option" screen, go to "Troubleshoot" -> "Advanced options" and try running "Startup Repair" first.

      If Startup Repair fails, try System Restore next.

      If the repair is successful and Windows starts up, the "Pictures" folder that you thought was missing may have returned to normal. (Please check the folder with your account name in C:\Users\.)
      If your PC won't boot and you can't even access the recovery environment, it can be a really hopeless situation. However, booting from this installation media will always give you a solution.

      It will be a difficult task, but please don't give up and keep trying to get your PC and important data back.

      If you're not comfortable doing it yourself, we strongly recommend that you don't push yourself and instead ask a computer-savvy friend or family member nearby to help you by showing them this reply (or the new steps we've added to this article).

      Reply

      • thank you for your reply.

        Thank you for the careful and detailed explanation.

        That was a really big help.

        On the first day, I thought it had broken down and it was a huge shock.

        I'll do my best and fix it.

        I'm really thankful to you.

        Reply

  • Good evening. I learned about KB5070773 through an article on another website, and after a while I encountered a "Blue Screen of Death" error with the message "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED AscFileControl.sys." I did some research, and just as your website suggested, I uninstalled KB5070773, then reinstalled it automatically. I then tried to enter safe mode using a certain app (one that can enter safe mode in one go), but the previous selection resulted in my USB keyboard and mouse not working. By the way, my WinRE version is 10.0.26100.6891.
    So I will install KB5070773 again and check if there is any change in behavior.

    By the way, it seems that the problem with the "Blue Screen SYSTEM_THREAD_EXCEPTION_NOT_HANDLED AscFileControl.sys" was caused by a file in the care software.

    Reply

    • Thank you for your comment, Mi-san.

      Thank you for using this article as a reference. I understand that you identified the cause of the blue screen (AscFileControl.sys) as being in the care software yourself. I'm glad that the problem has been resolved.

      Regarding WinRE, I understand that even after reinstalling KB5070773, the WinRE version remains at 10.0.26100.6891. This version number is the old version that had the issue, and indicates that the update to WinRE with KB5070773 was not completed successfully.

      As you say, installing KB5070773 again should solve the problem, but if the WinRE version still doesn't change, it's possible that the essential "WinRE update KB5070762 (update package)" hasn't been applied.
      Please refer to the article below for more details on the causes and solutions.

      [Added 2025/10/22] Verification: WinRE is not updated when manually applied from the catalog?
      https://windows-waza.com/solved-mouse-and-keyboard-not-working-issue-in-winre-fixed-with-kb5070773/#index_id9

      Thank you for sharing the details of your situation. I hope you can resolve the issue.

      Reply

    • Hello Jean,

      Merci beaucoup pour votre commentaire et pour avoir pris le temps de tester et de partager votre résultat! J'apprécie également la capture d'écran.

      Votre expérience confirme exactement ce qui est mentionné dans la section d'avertissement de l'article : démarrer à partir du support d'installation (DVD ou USB) créé avec l'outil Media Creation Tool fonctionne correctement car il utilise son propre environnement de démarrage (boot.wim).

      C'est une excellente démonstration pratique de cette partie de l'avertissement!

      Je tiens à rappeler (comme vous l'avez probablement lu) que le danger réside dans le fichier winre.wim contenu dans l'ISO téléchargé par l'outil Media Creation Tool.

      Votre confirmation que le démarrage direct fonctionne est une information très précieuse pour les autres lecteurs cherchant une solution temporaire.

      Merci encore pour ce partage utile et cette validation importante! Au plaisir, Wenbang.

      Reply

    • Thank you for your comment, Sagat

      Thank you for checking.

      Yes, I understand that the issue was resolved with KB5070773 and that winre.wim was updated to .6901. I'm glad that it was a quick fix.
      Thank you for reporting this.

      Reply

    • Hello
      effectively
      2025-10 Mise à jour cumulative pour Windows 11 Version 24H2 pour les systèmes x64 (KB5070773) (26100.6901) ce matin (au Maroc)
      En tout cas Mr Wenbang est la seule personne sur internet à expliquer
      ce problème qui semble se manifester régulièrement depuis des années selon les mises à jour déployées.
      C'est quand même grave de la part de Microsoft.
      Captcha en japonais……très difficile pour moi 😉

      Reply

      • Hello Jean,

        Merci beaucoup pour votre commentaire! Je vous remercie également pour votre message en français et pour avoir bravé le Captcha en japonais 😉

        Merci de confirmer que la mise à jour KB5070773 a également été distribuée ce matin au Maroc.

        Comme vous le dites, je trouve également très regrettable de la part de Microsoft que des problèmes affectant une fonction aussi importante que l'environnement de récupération (WinRE) Se produisent de manière répétée.

        Je fais mes recherches et publie mes articles dans l'espoir d'aider les personnes qui se trouvent dans cette situation difficile.

        Merci encore pour vos aimables paroles d'encouragement venues de si loin. Au plaisir, wenbang.

        Reply

  • Today, I received the Windows Update option "2025-10 Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5070773) (26200.6901)."
    I was able to successfully enter WINRE using the keyboard and mouse.
    The WINRE version has changed to 10.0.26.100.6901.
    I'm having trouble getting into safe mode.

    Reply

    • Thank you Transcend for your comment.

      Thank you very much for your confirmation and detailed report.

      I'm really glad to hear that KB5070773 was successfully applied and that you can now use your keyboard and mouse in WinRE. The specific information that your WinRE version has been updated to 10.0.26100.6901 is also solid evidence that the fix has been applied.
      You're absolutely right, not being able to enter Safe Mode is extremely frustrating, and we're relieved that Microsoft fixed it so quickly.

      This information is very useful for other readers. Thank you for sharing this valuable information.

      Reply

    • Hi Jean,

      Thank you so much for your repeated comments and for sharing your successful experience! I sincerely apologize for the delay in my response.

      It's fantastic to hear that using the latest Media Creation Tool solved the issue for you and that everything is working well! Your report is incredibly valuable and truly helps others who are facing the same problem.

      You are absolutely right that using a USB created with the Media Creation Tool is an effective workaround.

      My subsequent in-depth verification revealed a slightly complex background to this phenomenon:

      When booting from a USB installation media, your PC uses an independent recovery environment (boot.wim) from the media itself, bypassing the corrupted winre.wim on your PC's main drive. This is precisely why your method worked perfectly.

      However, my tests confirmed that the winre.wim file contained within the latest Media Creation Tool's ISO still includes the faulty driver.

      This suggests that your PC's specific hardware configuration might have fortunately not been affected by the bug in that driver. While this is great news for you, it unfortunately might not be a universal solution for everyone.

      Your valuable feedback has greatly helped us understand the full scope of this issue. If anyone needs to permanently fix the WinRE on their PC's main drive, regardless of hardware, the batch file introduced in my article remains the most reliable method.

      Thank you again for sharing your success. Your comments have contributed significantly to clarifying the full picture of this problem!

      Reply

  • Hello, Mr. Wenbang

    I am french and was particularly interested by your
    awesome thread.
    You are the only one to give an explanation.
    So, i have just downloaded the last MediaCreationTool.exe from
    Microsoft Website and done an USB Flash Recovery Disk with it.
    And eveything, keyboard and mouse is working.
    Thanks a lot

    Reply

    • Thank you for your comment, Sherry.

      As you say, that is a very effective and reliable way to avoid this. That perspective is very important, and I agree.

      The repair function booting from Windows installation media works without issue because it uses the clean recovery environment in the media, rather than the affected WinRE installed on the PC itself.
      For those who have installation media prepared just in case, this may be the easiest and safest method.

      The batch file introduced on this site is provided as a solution for those who cannot wait for an official fix from Microsoft or who do not have installation media on hand and would like to directly repair the recovery function of their PC.
      It's really great to see multiple solutions and workarounds being shared with the community like this. Thank you for sharing your valuable information.

      Reply

  • Fortunately, I
    - Because it is a laptop, you can use the keyboard, touchpad, and trackpoint in the recovery environment.
    I have two types of partition backup software: Macrium Reflect and Hasleo Backup Suite. The only software for which I updated the bootable media after KB5067039 was Hasleo Backup Suite, which was recently updated. Macrium Reflect bootable media has not been updated after KB5067039, so it can be used without any problems.
    Therefore, I will not take the risky step of replacing winre.wim, but will wait for the official patch to be released.

    Reply

    • Thank you for your comment, Arom.

      Thank you so much for sharing this valuable information.

      The fact that the laptop's keyboard and touchpad are working, and that the Macrium Reflect media is working fine before the update, are both very useful pieces of information that get to the heart of the issue.

      In particular, examples of different behavior between bootable media before and after an update will provide reassurance to many readers that "it's not just their environment" and will be a great help in understanding the cause.
      Also, I think that your decision to "avoid the risky winre.wim replacement process and wait for the official patch to be released" after securing an alternative solution is the safest and most prudent choice.

      Your comment, Arom, is very helpful and wonderful information for those who use similar laptops or have old rescue media. Thank you very much.

      Reply

      • Even after applying the patch, the WinRE version remains at 6891 and doesn't change to 6901...
        The bug of not recognizing USB devices has not been fixed.

        Reply

        • Thank you for your comment, Arom.

          I also confirmed this issue when I tested it a while ago. In my case, I was able to resolve the issue by uninstalling KB5070773 and then re-applying it, so please try that.
          If you are unable to resolve the issue, please contact us again.

          Reply

  • I noticed this issue around yesterday, and while I was gathering information, I found a related video on YouTube.
    https://www.youtube.com/watch?v=dcynjxylbbI
    I found this and then searched online and came across this.
    I was searching for a way to repair the "EFI system partition" and had started backing up my data in preparation for the worst case scenario of reinstalling Windows 11, but this information and YouTube video helped me out.
    Thank you all!

    Reply

    • Thank you for your comment, Iyokan-san.

      I see you came to our website after watching a YouTube video. You searched for "repairing the EFI system partition" and even started backing up your data, preparing to reinstall Windows 11. I can imagine that you were in a very difficult situation. I'm truly happy that the information on our website, along with the YouTube video, was helpful to you.

      This issue is extremely troublesome, causing confusion for many users and even leading them to consider reinstalling the app. Iyokan's valuable report will be of great help to those in the same situation, helping them find the right information.
      Thank you very much for your valuable report. If you have any comments or suggestions, please feel free to leave a comment.

      Reply

  • Dear Wenbang,
    After updating Windows, the cursor started behaving strangely and I was at a loss as I couldn't operate it even in recovery mode, so I came across this site.
    Thank you for clearly explaining why uninstalling KB5066835 does not restore the system and how to deal with the issue.
    I'm a beginner when it comes to computers, so I'll wait for an official fix from Microsoft.

    Thank you all!

    Reply

    • Thank you for your comment, Mayu.

      It can be really frustrating when your cursor starts acting strangely and you can't even operate it in recovery mode.
      I'm really glad this article was helpful.

      "I'm a beginner at computers, so I'd like to wait for an official fix from Microsoft." I think that's a very wise and safe choice. There's no need to go through complicated operations.
      As soon as a fix is ​​provided by Microsoft, we will update this website with the information, so please check back again.

      Thank you very much for this valuable report.

      Reply

  • When I tried to enter WINRE with this month's Windows update, the "Please wait" screen appeared and the keyboard, mouse, and USB-related functions were disabled, preventing me from proceeding further. Even changing to a different keyboard and mouse did not work.
    I tried a clean install of the OS on 25H2, and was able to enter WINRE normally immediately after the clean install, but after the subsequent Windows update was completed, I was no longer able to enter WINRE again.
    It wasn't my environment that was the problem.
    Thank you for teaching.
    If you only want safe mode, it seems you can enter safe mode by starting up with safe boot in the boot options of the system configuration.

    Reply

    • Thank you for your comment, Transylvania.

      Thank you very much for your detailed report and for sharing such valuable information.

      It must have been really tough for you to even try a clean install of the OS. Your experience of "it worked fine right after the clean install, but the problem recurred after a subsequent Windows Update" is very important evidence that this problem is caused by a Microsoft update.

      We would be very happy if the articles on this website helped you to find the cause of your problem.
      Also, I would like to express my sincere thanks for sharing the very practical workaround of safe boot from System Configuration (msconfig), which will be very helpful and informative for others who read this article.

      As a site operator, receiving specific feedback like this from our readers is the greatest encouragement we can receive. If you have any comments or suggestions, please feel free to leave them in the comments section.

      Reply

  • Dear Author,
    Today, when I tried to change the BIOS, I went to the recovery screen and realized that the keyboard that I had always used wouldn't work. I investigated the cause myself and was thinking about going out and buying a USB wired keyboard just to try it out, when I came across your article.
    It was very refreshing and helpful.
    Using the Event Viewer, I was also able to confirm that WinREAgent 4501 was present as of 10/15.
    Wait for the release of a fix patch.
    thank you very much.

    Reply

    • Thank you for your comment, Suzuki-san.

      You try to change the BIOS and enter the recovery environment, only to find that the keyboard you've always used no longer works... It's really frustrating, and it's no wonder you start to suspect a hardware failure.
      I was just about to go buy a new keyboard, so I'm very happy that the article on this site helped me find the cause of the problem just before I had to do that.

      I hope it will be fixed soon. If you have any comments or suggestions, please feel free to leave a comment.

      Reply

To comment

[About submissions]
We welcome any questions or information regarding the content of the article.
However, please note that content unrelated to the purpose of the article, criticism of specific individuals or organizations, offensive language,Inappropriate wordsComments containing the above may be deleted or made private without notice at the discretion of the administrator.
Please note that spam may be automatically deleted by anti-spam measures.

CAPTCHA


table of contents