Xps 13 Plus 9320 - Windows 11 24H2

Make a bootable USB stick so when it is time for a fresh install of Windows

Do I have to erase all files, or is it possible to keep them? I don't know if new version of Windows is worth completely wipe out my hard drive.

you will have to wipe the machine so save personal files and downloads to a larger capacity USB stick

And does my notebook even support this version of windows? It is not available right now through windows update. After failed installation it is not possible to download it again.

When it fails windows pulls it 

You machine can run 24H2 fine

I have the same exact problem as themidz.  XPS 13 9320 which cannot install the Windows 24H2.   I followed the process and almost in the end, the installation rolled back because some driver error (0x80070002 - 0x20007).​  And, I am NOT going to do a clean install of Windows; if it is an update it should just work.

@DMIG_cfc010​ Hi. I managed to install the new update with this guide. Everything works fine after the update - https://peppercrew.nl/2023/01/upgrading-windows-11-22h2-fails-with-error-0x80070002/#:~:text=In%20conclusion%2C%20the%200x80070002%20error,and%20successfully%20upgrade%20my%20system  But I still think, that it would be great if Dell fix this problem somehow.

@themidz​ Sorry, but I am unable to find the paths that the article is referring to, such as C:$WINDOWS.~BT\Sources\Panther\setupact.log OR ‘pnputil -enum-drivers > c:\temp\drivers.txt‘

How do I find out which driver is causing Windows 24H2 to fail?

@DMIG_cfc010​ I would love to help you, but I am not a specialist :( As far as I know, the folder Windows~BT is created during update. You can try to download Windows 11 directly (https://www.microsoft.com/cs-cz/software-download/windows11) and when it fails, the folder should be present on your computer. 

@DMIG_cfc010​ I've followed the instructions at peppercrew.nl and have identified the offending driver (on *my* machine). I'll be uninstalling it and trying the upgrade again this evening (PDT) or Monday 3/10/25. If you respond to this, I'll send you my email and then guide you through it.

@tashkerm​ Thanks!  Please let me know what is the process you followed to find the offending driver.  Thanks so much! 

@DMIG_cfc010​ I did indeed follow the path sketched out on peppercrew.nl with success. My problem was a Western Digital compatibility driver that internet knowledge tells me is largely unnecessary. 24h2 installed fine now.

What you're doing is looking at the setup log for the failed install for certain terms, specifically "Failed to install the driver package". The line that includes that phrase will list an .inf file. You will look that up in a list of your drivers (created with pnputil -enum-drivers command). That will display an equivalent oemXX.inf file name, which will be deleted by another pnputil invocation.

If you can't follow that, here's what to do.

- Open a command prompt from the start menu.

- Enter this command:

copy C:$WINDOWS.~BT\Sources\Panther\setupact.log %homepath%\Desktop

This should put a file "setupact.log" onto your desktop.

NB: the folder C:$WINDOWS.~BT may be hidden, but the command above should still work. If it doesn't, there's more to do.

- Enter this command:

pnputil -enum-drivers > %homepath%\Desktop\drivers.txt

This will put a file "drivers.txt" onto your desktop.

Those are the two files you need to work with. If you can find the string "Failed to install the driver package" in setupact.log (open it in notepad and search), note what inf file is on the same line. For example, 

Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\wdcsam.inf_amd64_7ce69fc8798d6116\wdcsam.inf

The important thing is 'wdcsam.inf'.

Now locate that in drivers.txt. You'll see something like:
Published Name:     oem26.inf
Original Name:      wdcsam.inf

oem26.inf is what to remove/delete!

At the command prompt, enter the command:
pnputil /delete-driver oem26.inf /uninstall

Remember: it's oem26.inf on my machine, not yours. You need to find the published name of the offending driver that won't install by looking through the setup log and cross referencing it in your list of installed drivers.

Post if it works; post if it doesn't.