NOT ABLE TO INSTALL Windows 11, version 22H2 Insider Preview 10.0.22598.100 (ni_release)

New Contributor

I AM NOT ABLE TO INSTALL THE WINDOW 11, I AM HAVING AN INSTALL ERROR - 0x80070002 EVERY TIME. TRIED EVERYTHING FROM RUNNING WINDOWS TROUBLESHOOTER, STOPPING WINDOWS UPDATE SERVICE AND DELETING THE SOFTWARE DISTRIBUTION FOLDER AND STARTING THE WINDOWS UPDATE SERVICE, AND GOING TO THE REGISTRY EDITOR METHOD STILL THE COULDN'T UPDATE MY DEVICE TO THE NEW BUILD.

SportingDot_0-1650302636453.png

AND RECENTLY THIS ALSO STARTED COMING.

 

 

26 Replies
I have this exact issue. Same error as well (0x80070002) as I did same steps. Seems to be a bug in the update. I also ran a bunch of scans but they all came back fine. The ISO did not work and it just undid the changes made. Im so tired with this. For the last 3 updates the same error for me.

Hi @SportingDot 

Have you tried to download ISO and update in place?

For this version, ISO has been released - check this :

Using ISOs - Windows Insider Program | Microsoft Docs

of course, if nothing helps using this ISO of the latest version you can reinstall the system, but it often helps to reset the computer to the initial version

Using ISOs - Windows Insider Program | Microsoft Docs

@SportingDot Exact same issue, tried 5 times all ready, just installs and then it undo's the changes at the end.

Yes, I have tried but still, the error persists.

In fact that's the second update I cannot install. 22598.100 didn`t work at all for me, tried a couple of times. Same error code as now with 22598.200. Besides the mentioned steps I also tried disabling and reenabling MSMQ, no success.

 

My logs always show some form of path not found exception , like this:

 

Failure while getting the known folder path for CSIDL_PRINTHOOD (S-1-5-21-2311215600-815168974-1672239869-1005): Win32Exception: The system cannot find the file specified. [0x00000002] class UnBCL::String *__cdecl Mig::CFacadeUser::GetKnownFolderLocation(class UnBCL::String *,int *,class UnBCL::String **)[gle=0x000036b7]

 

I don't see what could be causing that.

Getting the same issue now with .200

Log says :

{942FD6BC-E6EF-4425-AA78-BCC6FE3B42E4} 2022-04-21 09:56:40:873+0200 1 182 [AGENT_INSTALLING_FAILED] 101 {7405F8E8-AA99-41C8-A2AC-2F31182866B4} 1 80070002 MoUpdateOrchestrator Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070002: Windows 11, version 22H2 Insider Preview 10.0.22598.200 (ni_release). 5A5jJSsgAUqGQA02.7.2.3.0.0

@SportingDot  USE  **RUFUS** TO MAKE ISO FROM INSIDER SITE, WITH MODIFIED PARAMATER "NO TPM/ SECURE BOOT"

Screenshot 2022-04-22 010651.png

Insider ISO's

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

 

Rufus

https://rufus.ie/en/

I have this exact issue. Same error as well (0x80070002)

@SportingDot you may use the first file iso that is not compatible with your laptop, please try to use the same iso file that you are used to install your current system.

I am in the same boat. I have TPM 2.0. It is active in BIOS. I am good to go for installing Windows 11. I have had Windows 11 since it came out. I have tried the Insider Preview build in-place, I have tried making an ISO from UUP dump (created correctly, but states it cannot detect drive size). The only thing I have not done is completely wipe. If it comes down to that, I will just go back to retail and call it a day.
Same problem. Just installed Windows 11 Pro from scratch and got:
Version 21H2
OS build 22000.613
Intel(R) Xeon(R) Platinum 8171M

@SportingDot  I had the same problem and it seems that turning on virtualization will fix the problem.

My pc has the virtualization on and I still get error 0x80070002. Have not tried the latest .200 yet

@SportingDot 

I have a Lenovo Thinkpad and I also had an issue for weeks trying update to version 22H2 Insider Preview 10.0.22598.100.  There were two things I did, uninstall Avast AV and turned off Kernal DMA Protection in the BIOS.

Thank you for your helpful information!
" uninstall Avast AV and turned off Kernal DMA Protection in the BIOS."

@Andrzej1 I’m not certain that it was Avast that was the issue. I do think it was the Kernel DMA Protection in Virtualization that was the underlying issue