Windows 10: Problems installing win10 22H2 onto an iSCSI disk

Win10 1709 && 1809 works in my iSCSI setup. But 22H2 appears to be problematic to me.In short, I can't get 22H2 installed, either through iPXE booting the WinPE from the ISO and running the setup.exe from a SAMBA share, or through simple windows feature upgrade from a working 1709 / 1809 install.For the setup.exe path, the system crash reboots shortly after it partitions the destination disk and begins to copy file to the disk, without any information that I can collect.For the windows feature upgrade path, it failed to boot after restart into the installer. I'm eventually dumped into

:)

 

How to get the Windows 10 2022 Update version 22H2 Win Update

If you can't install it from windows update you can try to install it manually, it's the same KB5015684 obtained with windows update.

Windows 10 Version 22H2 is coming in October 2022 ---> KB5015684 Provides Quick Windows 10 22H2 Upgrade - Ed Tittel On the Ed Tittel page click on the links DeskModder.de or .MSU x64 version of the upgrade.

KB5015684 Funktionsupdate auf die Windows 10 22H2 (19045) [Manueller Download] - Deskmodder.de

Do dism and sfc /scannow commands before and/or after installing it.

 

How to get the Windows 10 2022 Update version 22H2 Win Update

I wish things are that simple. My error code was 0x80246017, and I don't have KB5020435 installed so it's a dead end. BTW, MS lists like 6 or 7 error codes of the format 0x8024xxxx on the "troubleshooting WU problems", and when you chose next step, it suggests generic steps: run WU troubleshooter, check if your disk has no errors, is your remote disk is accessible, etc. Same as MS community; each similar error has completely different cause and (re)solution.
MS in notorious for this- if it works then OK, if it doesn't then good luck.

 

Windows 10 iSCSI installation possible?

The reason I'm interested in this subject is that I recently had an encounter with CryptoLocker malware and it was unpleasant. I thought that if I could boot from an iSCSI drive that was actually a zfs volume on a storage server I could use the zfs snapshot/rollback capability to quickly recover from such problems. I've gotten as far as PXE booting and starting the win10 install but the iSCSI target isn't shown as one of the possible installation targets. I can't be the first person to want to do this...