+x

 

Froggie - 29 January 2023 2:24 PM

...and if it's Windows 7 DISM that you're questioning (and you should... it's a bit different than the newer DISMs), probably best to do that build on a Windows 10 machine.  If you have one, just move the license (if there isn't one there), do the build and move the license back.

DISM updates are part of the ADK download package, as are other related applications such as ImageX and OSCDIMG.  You'd have to make sure to use the version in the appropriate ADK folder rather than relying on the version on your system and used by default thanks to its PATH variable, but to my knowledge Windows 7 is capable of running the Win11 DISM binary that comes with the ADK.

+x

 

Froggie - 29 January 2023 2:24 PM

...and if it's Windows 7 DISM that you're questioning (and you should... it's a bit different than the newer DISMs), probably best to do that build on a Windows 10 machine.  If you have one, just move the license (if there isn't one there), do the build and move the license back.

I have licenses for both computers, so that is not an issue. It is just that it is easier for me to make the iso on my Win7 machine. An iso made on this computer does work, but I have not been able to test the "Add BitLocker Support" and "Add iSCSI Support" options and don't want to find out it does not work should I need it. The safest way is surely to make them on the Win10 machine, but I wondered if Andrew could shed some light on the error messages, also because it might be an incompatibility between Win7 and the Rescue Media Builder that should be addressed one way or the other.

I have the good habit of almost always making an iso for every new Reflect version, even when I do not burn it or update my boot menu item, just to be able to fall back on a previous version should I have to. Likewise I keep my library of old Reflect versions and also WinPE versions, which came in very handy today when I wanted to revert to WinPE 10 v1709 to get my drive recognised in the recovery environment again.