I had a properly running Advanced Restart WIN 11 Pro IFW 4.07C: drive recovery partition.
IFW 4.07 and working USB mouse input.
After 2025-10 MS updates Advanced Restart WINRE boot not responding to mouse/keyboard input.
Installed KB5070773, rebooted.
Checked OS build: 26100.6901
C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre\WinRE_Backup
Renamed winre.wim to winre.old
IFW 4.07 Utilities "Create/Update TBWinRE WIM used for Reboot"
Did not change options.
Have new wimre.wim with todays date and time.
10/24/2025 01:26 PM 830,014,876 winre.wim.
IFW 4.07 Utilities "Create Image for Windows Boot Media"
Burned USB Memory stick.
Rebooted from Memory Stick.
Ditto for the installed Windows Recovery Environment.
Still no USB mouse working in recovery.
What did I do wrong??
I know I can boot off memory stick - but have become used to speed and the ease of use of Advanced Restart.
I had a properly running Advanced Restart WIN 11 Pro IFW 4.07 recovery environment
-
TeraByte Support(PP)
- Posts: 1756
- Joined: Fri Aug 12, 2011 12:51 am
Re: I had a properly running Advanced Restart WIN 11 Pro IFL 4.07 recovery environment
I assume when you say IFL you meant IFW. IFL is Image for Linux. IFW is in TBWinPE/RE builds.
Is it a standard/plain USB mouse? Some mice that are more "advanced" or require drivers don't work properly in WinPE/RE. Support may vary between WIM versions as Microsoft changes drivers.
If it's an issue with a WinRE update, which seem to be much more common in Windows 11 (especially the latest versions), you could try building from an older WinRE WIM file and see if it works better. To try this, run TBWinPE/RE Builder, go into Settings, Program Paths tab. In the WinRE Source section select the "Use selected WinRE WIM file" option, then click the down-arrow on the Browse... button and select the WinRE_Backup item. The backups are named with the version. You should be able to select the previous version that worked. Click Open to select and close the file selection dialog. Also enable the "Allow user selected WIM to replace installed WinRE" option since you're using that mode. Click OK to save the settings changes. Then recreate your builds (or at least one of them to test it).
If TBWinRE boots up but seems to hang on initializing the network, you could try a build without adding drivers and with the network disabled. To do this, run TBWinPE/RE Builder, go into Settings and change the following settings and then create new builds:
Build Options tab:
--Disable “Add drivers from ‘Drivers’ folder”
--Disable “Add installed storage drivers”
--Disable “Add installed network drivers”
TBLauncher tab:
--Disable “Run WinPE initialization”
--Disable “Run network initialization”
--Also disable “Run Wi-Fi initialization” if it’s being used
IFW WinRE tab:
--Disable “Add installed storage drivers”
--Disable “Add installed network drivers”
--Disable “Run WinPE initialization”
--Disable “Run network initialization”
---------
If you want more control over the build you boot to, you could also setup a custom folder for TBWinRE (e.g. C:\TBWinRE) and using the BootWIM method to boot the build. This can work better in some cases than using the Advanced Startup menu and the installed WinRE.
Is it a standard/plain USB mouse? Some mice that are more "advanced" or require drivers don't work properly in WinPE/RE. Support may vary between WIM versions as Microsoft changes drivers.
If it's an issue with a WinRE update, which seem to be much more common in Windows 11 (especially the latest versions), you could try building from an older WinRE WIM file and see if it works better. To try this, run TBWinPE/RE Builder, go into Settings, Program Paths tab. In the WinRE Source section select the "Use selected WinRE WIM file" option, then click the down-arrow on the Browse... button and select the WinRE_Backup item. The backups are named with the version. You should be able to select the previous version that worked. Click Open to select and close the file selection dialog. Also enable the "Allow user selected WIM to replace installed WinRE" option since you're using that mode. Click OK to save the settings changes. Then recreate your builds (or at least one of them to test it).
If TBWinRE boots up but seems to hang on initializing the network, you could try a build without adding drivers and with the network disabled. To do this, run TBWinPE/RE Builder, go into Settings and change the following settings and then create new builds:
Build Options tab:
--Disable “Add drivers from ‘Drivers’ folder”
--Disable “Add installed storage drivers”
--Disable “Add installed network drivers”
TBLauncher tab:
--Disable “Run WinPE initialization”
--Disable “Run network initialization”
--Also disable “Run Wi-Fi initialization” if it’s being used
IFW WinRE tab:
--Disable “Add installed storage drivers”
--Disable “Add installed network drivers”
--Disable “Run WinPE initialization”
--Disable “Run network initialization”
---------
If you want more control over the build you boot to, you could also setup a custom folder for TBWinRE (e.g. C:\TBWinRE) and using the BootWIM method to boot the build. This can work better in some cases than using the Advanced Startup menu and the installed WinRE.
Re: I had a properly running Advanced Restart WIN 11 Pro IFW 4.07 recovery environment
I finally got USB mouse input working in WIN11 Pro 24H2 recovery. But not the way it should have happened.
After installing the 2025-10 MS updates in both PCs they had no mouse input when Advanced Restart booted into recovery. These updates were done around Oct 20th, and I knew that the USB problem would occur. I also "assumed" that update KB5070773 would be offered in Windows Update and would fix the problem - but KB5070773 was never offered.
I tried to fix the issue manually. I downloaded and installed KB5070773. Still, no mouse support in Advanced Restart recovery. Things went into failure mode from there. I researched and tried whatever I could find to fix winre.wim and get the recovery partition fixed. After working almost three days I concluded it was beyond my abilities and level of knowledge.
I had taken an IFW full C: IFW backup prior to the 2025-10 MS updates (I always backup before the monthly MS updates.) I then blew away C: and installed a clean copy of WIN11 Pro. During that install MS Update offered KB5070773 and mouse input in recovery was working. Installed IFW 4.07, created a new recovery partition with 4.07, and took a full C: backup. Advanced Recovery booted and I used 4.07 to restore my "normal" pre-update partitions - except I kept the new recovery partition.
Strange thing - today, the 28th, MS Update on the second PC suddenly offered KB5070773. My PC has never offered that update.
"Better late than never" was not appreciated.
After installing the 2025-10 MS updates in both PCs they had no mouse input when Advanced Restart booted into recovery. These updates were done around Oct 20th, and I knew that the USB problem would occur. I also "assumed" that update KB5070773 would be offered in Windows Update and would fix the problem - but KB5070773 was never offered.
I tried to fix the issue manually. I downloaded and installed KB5070773. Still, no mouse support in Advanced Restart recovery. Things went into failure mode from there. I researched and tried whatever I could find to fix winre.wim and get the recovery partition fixed. After working almost three days I concluded it was beyond my abilities and level of knowledge.
I had taken an IFW full C: IFW backup prior to the 2025-10 MS updates (I always backup before the monthly MS updates.) I then blew away C: and installed a clean copy of WIN11 Pro. During that install MS Update offered KB5070773 and mouse input in recovery was working. Installed IFW 4.07, created a new recovery partition with 4.07, and took a full C: backup. Advanced Recovery booted and I used 4.07 to restore my "normal" pre-update partitions - except I kept the new recovery partition.
Strange thing - today, the 28th, MS Update on the second PC suddenly offered KB5070773. My PC has never offered that update.
"Better late than never" was not appreciated.