Windows 11, version 24H2 won't install

got it

you are not wrong. my Y drive is full i am trying to find a command that clears the entire drive so i can get 24H2 and Dells BIOS Update 1.25.0

Suppose to require 40gb

https://answers.microsoft.com/en-us/windows/forum/all/how-much-storage-space-is-required-to-download-and/138fc2fe-5714-45fd-8729-8ffa7ea1da5a#:~:text=You%20need%20approximately%2040GB%20of,download%20and%20also%20temp%20files.

Thankfully I didn't have that issue but got dropped out into those funny drives letters a few times. It started to make different boot environments whilst obviously you didn't want that. Like a number of failed ones. This is how people get their systems to boot into different profiles. Had to sort that out. So that was a concern.

Carry on. As mentioned that partner had open heart surgery and recovered I just worked on their laptop. New valve all good... laptop not good. Think it was Lightroom they had installed where the problematic Adobe DVD driver came from which was the root cause. Failed memory integrity.

you are not wrong. my Y drive is full i am trying to find a command that clears the entire drive so i can get 24H2 and Dells BIOS Update 1.25.0

am trying to install windows on my new pc, but it says failure

what do you mean?

I MEAN THIS:

I installed the big 24H2 update on my computer (HP 470 G9 laptop, Windows 11 Pro).

**It failed several times at first,**when I tried to install it in several different ways!

Here are the different steps:

1) It originally appeared for download onWindows Update on Nov 22. I tried to download it 2 times – the downloadalways stopped at 8%

2)It appeared again on Windows Update on Dec 15. Now the download and installation proceeded to the end– but then theinstaller started automatically undoing the changes made to the computer --> revertedback to v. 23H2

3) I then tried installing from theISO file --> failed(for some reason it reported aproblem with the installation language (?)-->could not select the option at all: “Keep my files and apps”

**4) The update finally went well and without any problems with this method:**💻👍👍

Windows 11 Installation Assistant

I would like to emphasize that this is one of the three official installation methods recommended by Microsoft!

Microsoft: This is thebest option for installing Windows 11 on the device you’re currently using.

---

https://www.microsoft.com/en-us/software-download/windows11/

 

**Note!**It is important to note that in order to proceed the installation process, everyone must first pass the WindowsPCHealthCheck (which can be launched from the link at the top of the downloaded Windows 11 Installation Assistant -application window)

https://www.youtube.com/watch?v=xxr2fkOKfm0&ab_channel=Pureinfotech

It trips if the original language doesn't tally with the one selected. American English won't work with International English and vis versa why save files and apps is greyed out. In the ISO method it checks that.

Could you tell me why I was able to install 24H2 without any problems using the Windows 11 Installation Assistant ... and many others are having serious troubles all the time even though they follow strict, long, complicated instructions?🙄🤔

For example, any wrong driver has never been found on my computer.

Because Microsoft tightened up on backend security. It's what programs and drivers that have been installed. All are different so if you go one or more than one that fails the increased security it fails.

There were early reports of IT managers with virgin computers and they couldn't get 24h2 to upgrade on some. Evident identical PC aren't even "identical". Nodoubt at manufacture different driver packs were used.

I don't buy that the installation assistant installs differently than the ISO method. The installation assistant download is manufactured by Microsoft at the time of installation. The download is more time consuming and you don't get the error codes to debug. Ideally you start with the installation assistant and if that fails switch to the ISO method. You hope not to be bugged by the automatic update till you sort out what's going on. It will try a few times, then give up for a period, then tries again. You end up being pestered with that whilst trying to debug the update either way.