I have spent the last few days trying to do a Host Refresh of Win7 using a wim, touched by the latest version of NTLite. (v 2.3.2.8526.) No matter what I try, it always fails about 2/3'rds into Setup (just after the 2nd reboot, where the screen goes into a VGA mode), telling me that "Setup can't complete." And that the computer will roll back to the previous version of Windows.
This on both my desktop and in a VM. (More on the VM test in a moment.)
I have been able to do a Host Refresh to the same Win7 using a wim I made early last year. (January 2021.)
But it doesn't work with a wim made with the current version of NTLIte.
So the problem seems to be following NTLite.
OR - it is following Time.
That is, I can make an argument that this is a Catch-22 Situation. (Sorry, non-native speakers - this is a North American idiom, from a book written in the 60's. (When hippies roamed the earth. (They're still around. They're just in government now.))) The Situation would go like this:
My current version of Win7 does not have KB4474419, SHA-2 Code Signing Support at this time.
I build my wim (for WIn7) in Win8.1 or Win10. So the process goes smoothly.
But when I do a Host Refresh, the SHA-2 Code signing isn't in the old Win7. And so I suspect that the Setup process aborts later in setup.
Does this sound like a reasonable hypothesis?
I plan to manually install KB4474419 into my current Win7 before trying the next Host Refresh, which should tell me if my hypothesis is correct. But it's 1 a.m. here and I've spent the last few days staring at screens.
In the meantime, perhaps we can take advantage of different time zones. Nuhi, perhaps you can demonstrate this problem for yourself:
Take a Win7+SP1 64-bit iso (US English) and install Home Premium in a VM. (I use VBox.)
Then take that iso and, using NTLite, bring it up to the Convenience Rollup, per my Preset. (So just three updates.)
Use the setup.exe from that wim to Refresh the vanilla Win7.
(I had to add GuestAdditions to VBox to transfer the wim. But that shouldn't affect this experiment.)
See setup refuses to complete for you too.
UPDATE: I should point out that if you do a Host Refresh using the same first WIn7+SP1 wim, then setup completes.
So it seems as soon as NTLite touches the iso with an Update, then something breaks.
(For grins I will try simply removing fonts, languages, keyboards to see if that will compete. (Trying to pin down where the problem lays.))
This on both my desktop and in a VM. (More on the VM test in a moment.)
I have been able to do a Host Refresh to the same Win7 using a wim I made early last year. (January 2021.)
But it doesn't work with a wim made with the current version of NTLIte.
So the problem seems to be following NTLite.
OR - it is following Time.
That is, I can make an argument that this is a Catch-22 Situation. (Sorry, non-native speakers - this is a North American idiom, from a book written in the 60's. (When hippies roamed the earth. (They're still around. They're just in government now.))) The Situation would go like this:
My current version of Win7 does not have KB4474419, SHA-2 Code Signing Support at this time.
I build my wim (for WIn7) in Win8.1 or Win10. So the process goes smoothly.
But when I do a Host Refresh, the SHA-2 Code signing isn't in the old Win7. And so I suspect that the Setup process aborts later in setup.
Does this sound like a reasonable hypothesis?
I plan to manually install KB4474419 into my current Win7 before trying the next Host Refresh, which should tell me if my hypothesis is correct. But it's 1 a.m. here and I've spent the last few days staring at screens.
In the meantime, perhaps we can take advantage of different time zones. Nuhi, perhaps you can demonstrate this problem for yourself:
Take a Win7+SP1 64-bit iso (US English) and install Home Premium in a VM. (I use VBox.)
Then take that iso and, using NTLite, bring it up to the Convenience Rollup, per my Preset. (So just three updates.)
Use the setup.exe from that wim to Refresh the vanilla Win7.
(I had to add GuestAdditions to VBox to transfer the wim. But that shouldn't affect this experiment.)
See setup refuses to complete for you too.
UPDATE: I should point out that if you do a Host Refresh using the same first WIn7+SP1 wim, then setup completes.
So it seems as soon as NTLite touches the iso with an Update, then something breaks.
(For grins I will try simply removing fonts, languages, keyboards to see if that will compete. (Trying to pin down where the problem lays.))
Attachments
Last edited: