Boot into Win PE is extremly slow.

On W11 it was 24H2 now it is 22H2, so far, even though i update and update. Come to think of it, the one time i mentioned earlier in the thread when it worked ok with the loading of files, was when i was on W11 22H2. So maybe this now will vanish when the pc has updated to 23H2 or 24H2.

Tomorrow will show what. That is the day i will try EasyBCD. Now it is way past my bedtime here in Sweden. Thank you guys, a whole bunch for your support and ideas.

Oh, i must say, W10 is so much smoother then W11. It is and feels just so. No micro lag and speedy.

 

I fresh installed W11 today and the problem was back. Sigh.

On that fresh install i did the E-BCD setup which was easy but it did not work. When booting to the recovery environment, i got a black screen with small white text saying that it could not boot due to a machine change etc etc. Looked like in the old days on W7.

 

I have never seen that error with EasyBCD, but if Windows 10 resolves your issue then you do not need to mess with the EasyBCD option.

I do not know why Windows 11 causes this issue while Windows 10 does not. The only thing I can think of is that there may be something wrong with your Windows 11 installation media. If you have time try building a new Windows 11 24H2 installation media with the latest March Patch from the UUP dump site and see if the issue is still there.

 

Me too.

Also I believe this is going to be the solution.

 

The thing is that i have done the recovery media anew many many times and fresh installing since this began. About 1 1/2 - 2 years ago. So that can not be it. But i will try UUP dump.

I have asked before, and do it again, IF, this could be a hardware issue, what could it be? Guess wildly!

 

This is not a hardware issue, your own test has proved it! If it was a hardware issue, just installing Windows 10 would not have resolved it. It is clearly a software issue, something is missing in your Windows 11 that is present in Windows 10.

As I mentioned earlier I cannot figure out what could be causing this issue, as Windows 11 and 10 share the same set of built-in drivers, and in any case your laptop should be more compatible with Windows 11, as that is the OS it was designed for......Maybe someone else here can suggest something.

 

Earlier today i tried to install W11 from an earlier image a had to C: partition, only, on the W10 installation. It could not even boot. It was an attempt to get it to function with W10 loader according to your and Froggies suggestions about drivers in the same.

I am thinking i shall order recovery media from Lenovo, even though there aint any specifically for this pc model since i ordered it without Os. It is an desperate attempt to maybe get that that is missing via their factory installation that that media does.

 

@pb1, the Win 11 booting issue could have been easily fixed by using the "startup repair" from a Windows installation media, or a similar option on Hasleo's recovery media.

You do not need the Lenovo recovery media, just download all the drivers for your laptop from Lenovo's website and then reinstall a fresh copy of Windows 11 24H2 with March patch from UUP dump site and install all the drivers one by one. That is all you need. Let me know if you need help creating the UUP dump Windows media.

Here is what I recommend doing. Make a complete backup of your current working system using Hasleo. Copy everything important off the laptop. Boot through the Windows 11 24H2 (March 2025) installation media. Choose a clean install option. When you reach the screen asking you where to install Windows, delete all your current partitions on your HDD. Create one partition and format it as NTFS. Now proceed with installation. Windows will recreate EFI, MSR, C and Recovery partitions for you and install itself on C. Boot into Windows, install Hasleo and check and see if your issue is resolved. I am sure this will resolve your issue. You can then install the downloaded drivers from Lenovo.

 

Raza, thanks for posting the Dump site address. I made an ISO of the latest Win11 Pro and installed it as a test. Interesting. I didn't know you could make an ISO from last week's Windows release.

Building the ISO took 45 minutes and the install of Win11 was about 10 minutes faster then usual. I assume because it didn't need to get recent updates.

 

Yes please. Help me with the converting.

 

Easilty repaired you say, i do not think it ever has succeded with anything for me. But, i tried it this morning on that mixed image, and it did not work. The repair ran for a very short while and then stopped.

Pity since it was a good idea. The functioning loader for W10 together with W11. There may be some severe problem with the recovery/loading with this pc, since HBS restoring do not work sometimes (interprocess failure) and repairing can not work. Not even a Ms Windows system image could load ok. Or maybe it was a coincidence and flawed HBS that still has its bugs and limitations.

 

It is actually quite simple.

Just go to this link UUP Dump and click the second option "Windows 11, version 24H2 (26100.3476) amd64"

Choose your language and hit Next.

Choose your edition. I prefer to choose only one that I want to install (Windows Pro for me). I don't like multi edition install media, but you may choose as you wish. Hit Next.

On this screen the required options are already checked.
Download method "Download and convert to ISO" and
Conversion options "Include updates" (this is important otherwise you will end up with the base Win 11 24H2 from October 2024)

I also like to check the
"Run component cleanup" and "Use solid ESD conversion". They will reduce the size of the resultant ISO, but add to the time it takes to create the ISO. They are optional.

Hit create download package.

Unzip the contents into a folder and then right click on the "uup_download_windows.cmd" script and choose "Run as Administrator".

Thats it. It will take between 60-90 minutes. The files are directly downloaded from Microsoft servers and the script compiles them into an ISO. When you get the ISO, you can then use the Rufus utility to make a Windows installation UFD. Do a clean Windows install, wiping everything and all partitions on your HDD.

Hopefully this will resolve your issue. I am traveling today so will not be able to respond until very late tonight.

 

You are welcome Brian. I have been using the UUP dump site for a few years now without issues. All the files are directly downloaded from Microsoft servers, and the good thing is if you install from the updated media, the resultant windows installation is a lot smaller then if you install the base ISO from Microsoft and run a Windows update.

 

So now i know how to use UUP Dump, may be interesting for the future. But regarding the issue, it did not help anything. Same as before. Actually even slower loading. I used the UFD with the burnt ISO to format C: on the W10 installation and install Windows there.

I suppose the above action means that it leaves the system partition - as is - and ONLY installs W11 on the partition where W10 is. Right? Since that is what i choose. If so, mysteriously enough, it works ok with that W10 system partition, but with W11 it do not. W11 works with neither its own or W10:s system partition when restoring.

I talked to Lenovo support again today and they have withdrawn the recovery media option for consumers so that is undoable. And they still had no clue about this problem. I will probably send the pc to czechien for service but with small hope. It only costs about 40usd to examine the pc, before any repair action. Therefore it could be worth a try.

 

I am now running 21H2 without any problems with the restoring. As i mentioned earlier some build of 22H2 also went fine. So someplace during 22H2, some build makes the function flawed. Because from then on the problem occurs. And i am running 21 with all other partions based on W10. Also, W11 24H2 did not work ok with same mentioned partitions. So, a now certain fact is, that from a specific build of 22H2 and forward up to the latest 24H2, the restoring is flawed - on this pc.

Why is that?
It can not be the Os, so it must be the pc. A still think it is hardware. Some hardware can not cope, on this pc.

 

I am going to let this installation update itself until it stops and see if the problem occurs, which it should according to experience so far.

 

The idea was to start fresh with a clean Windows 11 24H2 installation. That means deleting all the partitions required by Windows i.e System (EFI), Reserved (MSR), Windows (C) and the Recovery partition. Win 11 24H2 will recreate these partitions again with fresh clean data and hopefully resolve the problem you are encountering. What you have done here is the same thing you did in Post#52 which clearly did not resolve the issue.

Since Windows 10 and Win 11 21H2 are working fine for you, so there is a "software/incompatible driver/corrupt data" based conflict somewhere, and a clean wipe of your entire HDD and re-installation from scratch is indicated.

However, if Windows 10 is working for you then please stick with it, as it is still being actively supported by Microsoft, and is still the OS of choice for a vast majority of business customers.

 

I knew you would say that. Why did i not do that then, well, todays dump, is tomorrows W.update delivery, and since i have done dozen of fresh installs wiping everything since this began i am hard to see the difference with this one. But, that is next on my agenda.

W11 have changed a lot over the years and mostly in security in the basic construction, so i think it is hardware that can not cope with it. That which talks against it is that Lenovo support has no reports about this and the net is blank on info. That also talks for a software issue. I can hardly be alone about this. So therefore i think it is a few pc:s that has this problem and therefore the lack of info.

Since i want W11 i am going to send it for repair, i do not want to continue using a flawed pc, and see to it that Lenovo pays for this since it obviously is a fabrication error. Either directly, or indirectly. Both ways meaning that it is not compatible with W11.

So, what change during the 22H2 cycle could have caused this?
There is where the solution lays!

 

@Raza0007

Here is a odd and surprising turn of event. The 21H2 installation i did and said i should update via W.update up to 24H2, works. But i am now on 23H2. The loading of the bar is done as it should be done. So so far, it works. But the final prof is if it works on 24H2.

So all these fresh installs i have done on 23H2 and even on 24H2 was in vain. This action worked. But as said - so far.
I have done a copy of all the drivers installed on 21H2 since they seems to be worth gold. Even if this works up to 24H2, i will do a totally fresh install with the dump ISO to see how that goes. And if it does not, as usual, i will implement the backed up drivers on that image to see what happens.

But as said, this was a really surprising turn of event.

 

So i totally erased the disc and did a fresh install with the dump ISO and got the latest 24H2. Installed HBS, created a boot menu and did a backup, then i restored it. The problem arised as expected. Uninstalled HBS and its boot menu. Installed the drivers that i had backed up from the 21H2 image, the image where the restore worked. Installed HBS and did a boot menu and backed up the Os. Tried a restore, and surprisingly enough the problem was still there.

So the drivers from the functioning image did not help neither did the dump ISO, only a fresh install of 21H2 which are being updated to present time. Very, VERY mysteriously. As i mentioned before, sometime under the 22H2 cycle the problem starts, so something is not present after that, which is present before it.

If it is a software problem, which it must be, i wonder what in the Os/ISO it is that is missing after 22H2 that makes this pc malfunction when it comes to restores.
So for now it looks like whenever i want to install anew, i have to install old W11 and update the Os to real time, as a new version do not work as expected.

The back up of the drivers i did with Double Driver and i backed up, and restored, ALL present drivers on the Os.
Since the drivers did not solve this, do you have any idea what this might be? Think wildly.

 

As I mentioned earlier, your situation is quite bizarre! It is clearly a driver or software that is causing this problem, but without the computer in front of me I am not sure I can diagnose the issue. If a particular version of Windows is working fine for you, I recommend you stick with it.

 

Microsoft released 23H2 to install AI CO Pilot on users computers.

Maybe your laptop is choking on copilot install.

Daniel

• 
  
• Windows 11 23H2 and version 22H2 are identical operating systems.
• They both include the same set of features, improvements, and fixes.
• The only difference is the end of support date.

The short answer is that Windows 11 23H2 and version 22H2 are technically identical. On October 31, 2023, Microsoft officially began the rollout of version 23H2 (also known as the Windows 11 2023 Update) for compatible devices, but there has been a lot of confusion with this release regarding features, changes, and differences with version 22H2.

Windows 11 23H2 is based on the core system of version 22H2, meaning that both operating systems share the same system files. As a result, the updates for version 23H2 will always contain the new features and improvements for both versions, but version 22H2 will only include the changes for this version. However, many of the improvements for version 22H2 will always align with those available for version 23H2.

The only real difference is that version 23H2, as the newer release, will be supported until November 1, 2025, while version 22H2 is expected to reach the end of support on October 8, 2024.

Windows 11 23H2 original plan
Originally, Microsoft was supported to release Windows 11 23H2 as a completely new version of the operating system with a bunch of new features and improvements. However, the company then decided to roll out all the innovations as a cumulative update for version 22H2.

The reasoning behind this approach was to get the new scope of features (primarily Copilot AI) to as many people as possible quickly because, as a cumulative update, Microsoft can make the update mandatory. If the company had made it available as an optional feature update, users would have the choice to skip the new version.

The update containing the new features is the KB5031455, which became available on October 26 as a non-security update (preview), then again on October 31, and again on November 14, but now as the security update KB5032190 for version 22H2. (The update is also available for version 23H2)

Also, since the update is cumulative, it means that the package installs as any regular monthly update, and complete reinstallation is not necessary for devices running version 22H2. The benefit of this approach is that it minimizes disruption to the end user and reduces the number of installation problems.

Windows 11 22H2 to 23H2 upgrade
Since both versions of the operating system are identical, a device running version 22H2 needs to install the update KB5032190 to add new features, improvements, and security fixes. After this installation, the “Windows Update” settings page will display the option to download the “Windows 11, version 23H2,” which is simply an enablement package (KB5027397) that changes the version number from 22H2 to 23H2 and resets the support cycle to 24 months for the Home and Pro editions and 36 months for the Enterprise and Education editions. The package may also enable any remaining features as necessary.

Windows 11 23H2 vs. 22H2: What’s the difference?
If you're wondering the differences between Windows 11 22H2 and 23H2, here's the explanation.

• Windows 11 23H2 and version 22H2 are identical operating systems.
• They both include the same set of features, improvements, and fixes.
• The only difference is the end of support date.

The short answer is that Windows 11 23H2 and version 22H2 are technically identical. On October 31, 2023, Microsoft officially began the rollout of version 23H2 (also known as the Windows 11 2023 Update) for compatible devices, but there has been a lot of confusion with this release regarding features, changes, and differences with version 22H2.

Windows 11 23H2 is based on the core system of version 22H2, meaning that both operating systems share the same system files. As a result, the updates for version 23H2 will always contain the new features and improvements for both versions, but version 22H2 will only include the changes for this version. However, many of the improvements for version 22H2 will always align with those available for version 23H2.

The only real difference is that version 23H2, as the newer release, will be supported until November 1, 2025, while version 22H2 is expected to reach the end of support on October 8, 2024.

Windows 11 23H2 original plan
Originally, Microsoft was supported to release Windows 11 23H2 as a completely new version of the operating system with a bunch of new features and improvements. However, the company then decided to roll out all the innovations as a cumulative update for version 22H2.

The reasoning behind this approach was to get the new scope of features (primarily Copilot AI) to as many people as possible quickly because, as a cumulative update, Microsoft can make the update mandatory. If the company had made it available as an optional feature update, users would have the choice to skip the new version.

The update containing the new features is the KB5031455, which became available on October 26 as a non-security update (preview), then again on October 31, and again on November 14, but now as the security update KB5032190 for version 22H2. (The update is also available for version 23H2)

Also, since the update is cumulative, it means that the package installs as any regular monthly update, and complete reinstallation is not necessary for devices running version 22H2. The benefit of this approach is that it minimizes disruption to the end user and reduces the number of installation problems.

Windows 11 22H2 to 23H2 upgrade
Since both versions of the operating system are identical, a device running version 22H2 needs to install the update KB5032190 to add new features, improvements, and security fixes. After this installation, the “Windows Update” settings page will display the option to download the “Windows 11, version 23H2,” which is simply an enablement package (KB5027397) that changes the version number from 22H2 to 23H2 and resets the support cycle to 24 months for the Home and Pro editions and 36 months for the Enterprise and Education editions. The package may also enable any remaining features as necessary.

Microsoft made it impossible to rollback
Although Windows 11 23H2 is an optional install, it doesn’t really make a difference because the innovations are already available for version 22H2. For instance, if you don’t want to use Copilot, removing version 23H2 won’t remove it or any of the new features. You could uninstall the KB5027397 package and update KB5032190 (or KB5031455), but in the following monthly update, the features will be installed again.

As for the new features and changes, this update introduces Copilot, the new digital assistant powered by AI that replaces Cortana. You get an updated version of File Explorer with new visual designs, a new Gallery page, an updated Details pane, native support for RAR, 7z, GZ, and TAR file formats, and changes to Nearby Sharing. The update also supports controlling RGB lighting with dynamic lighting and passkeys and changes to the Taskbar and Start menu. In addition, Windows 11 23H2 introduces a new Windows Backup app, a redesigned Outlook email client application, and updates for Paint, Photos, Snipping Tool, Clipchamp, Notepad, and more.

 

This can not apply to my pc since it works ok if i first install 21H2 and let it update all the way to 24H2, instead of using an ISO and do a fresh install and get 24H2 directly, where the problem is present.

 

My guess is that Ms has removed or inactivated something in Windows in the specific 22H2 build where the problem first occurs, that is not tampered with before that build. That is why a fresh install of 23/24H2 do not work but with a fresh install of 21H2 it does.

I shall ask Dino Nuhagic, the developer of NTLite, if he has a clue.

 

Today it updated from 23H2, which was without the "problem" to 24H2, and the issue was back. Mysteriously indeed.