Emergency Media Creation

[Epictetus]

Thanks Froggie - very informative posts. I knew about the deleting winpe.iso from the bin folder but not the rest.

As I said earlier, I seem to get the best result so far by using the download from MS, so I think I'll stick with that. Now that I know there are some problems, I'll be even more sure to check that all my Emergency Disks do really work.

[CDC9762]

I have 2 Emergency Disks, the latest and the one before which I rotate with a new version. I always have one that I knew worked in case the latest is not the greatest.

[admin]

Here is the link on the Microsoft website regarding this Windows Recovery Environment issue:
https://learn.microsoft.com/en-us/window...696msgdesc

Windows 11, version 25H2 known issues and notifications | Microsoft Learn
View announcements and review known issues and fixes for Windows 11, version 25H2

[al3x]

MS released KB5070773 now to fix this issue 

October 20, 2025—KB5070773 (OS Builds 26200.6901 and 26100.6901) Out-of-b…
Related topics × Windows 11, version 25H2 Windows 11, version 25H2 October 20…

[Froggie]

Some early adopters say the OOB 20Oct update hasn't solved the entire issue...

[admin]

MS released KB5070773 now to fix this issue 

We will test it.

[admin]

MS released KB5070773 now to fix this issue 

We will test it.

The update fixed the problem on my test machine.

[hader]

@hader - If you have already created a BOOT media of any kind with your latest installation, having the current OPE file doesn't do anything for you.  You need to go to C:\Program Files\Hasleo\Hasleo Backup Suite\bin and delete the file called winpe.iso.  While in the bin folder,  go to the following folder... WADK\Windows Preinstallation Environment and delete the AMD64 folder (the previously downloaded Microsoft files).  You can eliminate these steps by re-installing your current HBS version which will do all this cleanup for you.

Now, when you start a new Emergency Disk build, Hasleo will ask whether to download winpe components once again... CHECK the box and say NEXT.  At the next window you will see an Offline WinPE Package button, SELECT that button.  A DropDown will appear allowing you to drill to the location of your recently downloaded OPE file.  SELECT your file and CLICK Next.  The download and build will commence but instead of downloading, a few seconds later the build will begin.  The rest is as you expect.

I was in the mean time aware of the KB5066835 (updates your system to 26200/26100.6899 25H2/24H2) bug introduced by Microsoft that it does not initialize the USB keyboard/mouse in all WinRE environments. I applied the OOB update that came out yesterday/today. Installed it and made a new Emergency disk but it has still the same problem.

Reading your post I realized Hasleo still used the old components that came with with the previous version of the Emergency Disk (including stuff from that bugged 26200.6899 Build) The update advances Windows to Build 26200.6901
I indeed needed to delete that old-bugged WinPE stuff that Hasleo kept in it's directory's. I followed your steps.

- Deleted the WinPE.ISO inside that hasleo bin directory.
- Deleted the amd64 directory inside that WADK\Windows Preinstallation Environment directory (was empty)

Followed you next instructions for making a new and current WinPE environment.
- Checked the WinPE components.
- Checked the Offline WinPE Package
- Pointed to the recent downloaded Win10/11 *.OPE file. (Downloaded with Hasleo's WinPEDownloader)
- Made a new Emergency Disk.
- Booted form it. Now: A lightblue (Was black in the faulty one) background and the Hasleo Window. Keyboard and mouse were initialized and I could take actions. Solved!!

Real thanks for your clear and understandable instructions. I know now a bit more about the Hasleo's WinPE capability's and what to do with that OPE file. (in hindsight very understandable) 👍👍👌

You saved me some time for debugging and searching what was the problem now....  Great! Thank you!!!!