So I'll post my preset later today when I get home, but in the meantime wanted to see if others might be familiar with this issue.
NTlite version: 2024.12.10221 x64
Host OS: Win 10 21h2 x64
Target OS: Win 10 22h2 x64
I have a moderately conservative preset for ntlite that removes a lot of MS junk but doesn't touch any core functionalities, integrates updates, the usual. I recently updated all my install ISOs to include all updates from the last ~3 years (which was the last time I did this), as well as newly adding 22h2 to the list.
Installing the 22h2 ISO on both a live system as well as Virtualbox 7.1.4, I get a BSOD after the first reset, complaining about missing nvstor.sys, with error 0xc000000f (? not sure here, going from memory).
So I tried installing my new 21h2 ISO that I created with the **EXACT SAME PRESET** (except integrating 21h2 updates instead of 22h2) and that worked fine.
This is my first time working with 22h2 media, so the immediate question is: what's different/unique about 22h2 that might cause this?
Thanks for any and all help.
NTlite version: 2024.12.10221 x64
Host OS: Win 10 21h2 x64
Target OS: Win 10 22h2 x64
I have a moderately conservative preset for ntlite that removes a lot of MS junk but doesn't touch any core functionalities, integrates updates, the usual. I recently updated all my install ISOs to include all updates from the last ~3 years (which was the last time I did this), as well as newly adding 22h2 to the list.
Installing the 22h2 ISO on both a live system as well as Virtualbox 7.1.4, I get a BSOD after the first reset, complaining about missing nvstor.sys, with error 0xc000000f (? not sure here, going from memory).
So I tried installing my new 21h2 ISO that I created with the **EXACT SAME PRESET** (except integrating 21h2 updates instead of 22h2) and that worked fine.
This is my first time working with 22h2 media, so the immediate question is: what's different/unique about 22h2 that might cause this?
Thanks for any and all help.