Boot into Win PE is extremly slow.

Have you considered that it might be a problem with the recovery media and not your OS. When you build Hasleo's recovery media, it gives you two options, either to build with media from files already on your PC, i.e WinRE based media, or it gives you the option of downloading WinPE components from the internet, in which case it will build a recovery media from WinPE instead. WinRE based media is built with whatever the version of Windows you have installed at the moment, but WinPE media is built with the standard WinPE files on Microsoft's servers that Hasleo has decided to use to build its recovery media. They are both not the same and if you are having issues with one then perhaps using the other might be a good idea. I am not sure whether it will correct your issue but it is just a thought. Here is a link to a discussion going on here at Wilders about this issue.

https://www.wilderssecurity.com/threads/hasleo-backup-suite.449122/page-24#post-3162306

 

Hm, the 2 options one has, is to download WinPE from Ms or to use a offline WinPE. No mentioning of WinRE.

 

The offline one has to be WinRE. You can ask at the Hasleo's thread. People there use Hasleo as a daily driver and will confirm it.

 

I took it for granted that that was PE on the pc created by self, maybe it is RE. I will ask, thank you.

 

The OffLine Hasleo image is WinPE based and may be downloaded from Hasleo HERE. It is not RE-based in any way and allows you the option of keeping it resident on your System and using it (to avoid long downloads) to create their Emergency Disk.

 

Thanks for the clarification. I do not use Hasleo so I was going by the discussion you guys were having here. I know that discussion is dated, but I assumed they were still using WinRE for the offline media creation.

 

In the past, WinRE started to give them fits as far as compatibility was concerned... they decided to stick with WinPE (both on-line <from MS> and off-line <with their OPE>) and have users add whatever extra drivers they needed when they do the build.

 

A while ago, I was having trouble with WinRE being slow to load with TeraByte Image For Windows boot media, so I switched to WinPE and found it to be much faster. I have stuck with it.

 

Is there any difference between the 2, in any way - at all?

 

I don't believe there is. When they download from MicroSloth, they download the W10 latest WinPE <v2004> even if you're building from a W11 System (W11 WinPE a little too early for them to trust). Their OPE version is also a baseline of WinPE v2004.

 

About 10 months ago, I had problems with WinPE media. It was after the Windows 11 24H2 update.
I fixed my issues by installing the latest Windows ADK and Windows PE Add-on for Windows ADK.

 

@pb1, it just occurred to me what could cause a slow WinPE boot. Check and make sure there is no SD card in your SD card reader slot. A bad SD card can cause a slow boot. This is usually for a general slow booting PC, but maybe this is what is causing your WinPE to load slowly as well.

 

Thank you for your input.
No nothing is connected to it when i have tested this problem in different ways. This will stay a mystery since i will not pursue this anymore. I will go back to Acronis TI with its Try&Decide tool instead even though it costs.

 

Thanks again Raza,

I just did this with a DUMP site ISO. My Win11 partition gained 12 GB of Free Space. I had intended to restore an image to get back to my previous Win11 but I'll leave it as is. DISM is now working again.

My new backup image (after the upgrade) is 10 GB smaller than yesterday's image.

 

I've been using UUP Dump for years. It's very good.
There is a great tutorial here, but you probably already know all about it.

 

Hadron,

Thanks. I'm just about the run the DUMP ISO (UFD) on my main computer. I'll report back.

 

Only gained 0.7 GB of Free Space on that computer.

 

You are welcome Brian! Since Microsoft only releases one ISO per version per year, so the benefits of UUP dump increase as you go farther away from the MS October ISO date. If you were to do a fresh install 10-11 months after Oct ISO, there is an even bigger difference between the Windows install sizes.

 

I updated my wife's desktop computer today with last weeks Win11 UUP Dump ISO (UFD). No problems. The computer is a MBR system, no TPM and has a second generation Intel CPU.

A few years ago it was running Win10 and couldn't be upgraded to Win11. It showed an error with every attempt. An image of the OS partition was created and was restored to a GPT disk in my UEFI system (recent hardware) and some TeraByte Unlimited magic enabled it to boot. Then it could be upgraded to Win11. An image was created of the new Win11 OS partition and then restored to my wife's MBR computer. Some TeraByte Unlimited magic enabled it to boot. Win11 has run fine for a few years on the MBR system and updates automatically every month. It is certainly "incompatible" hardware.

 

A mate tried to upgrade his Win10 laptop to Win11 yesterday. He was using a UUP Dump Rufus UFD with the appropriate exclusions and he received an Incompatible Hardware error message. The laptop has a 6th generation Intel CPU.
I won't see him until September and I'll transfer his OS to my computer, do the upgrade and transfer the OS back to his laptop.

 

Ask him to upgrade Windows 10 to an older version of Windows 11, and then update to the latest Windows 11 (23H2). This 6th gen block has been added recently with 24H2. There is an instruction set called POPCNT and any CPU lacking it will not be able to boot Windows 11 24H2.

Edit: It appears 6th gen Intel CPUs have the POPCNT instruction set, so they may be able to update to 24H2 after upgrading Windows 10 to an older version of Windows 11.

 

Thanks, I'll get him to try Win11 21H2.

 

I assume the UUP Dump Win11 21H2 is OK?

 

@Brian K, it should be OK. Just make sure during ISO creation the option to "Include updates" is unchecked, just in case.

 

Raza, he tried 21H2 and 22H2. He saw this when running Rufus. Both ISOs. Suggestions? I'm out of my depth.