Tool crashed unexpectedly
- Thread starter pmikep
- Start date
As per this thread, I was trying to integrate a cumulative update into my existing, deployed Lite'd Win10. But patching failed due to a missing file.
Okay, I moved on and did a Host Refresh.
But every time that I load my deployed image, I receive an warning that "This image had a previously cancelled session during processing and may be in an unstable state." It advises that I unload/reload. Which doesn't clear the message the next time.
Is there a way to clear the flag?
Okay, I moved on and did a Host Refresh.
But every time that I load my deployed image, I receive an warning that "This image had a previously cancelled session during processing and may be in an unstable state." It advises that I unload/reload. Which doesn't clear the message the next time.
Is there a way to clear the flag?
I just now tonight managed to update my "ancient" (5 year old) Win10 with the latest Cumulative Update. (it's now 3 am, once again another 'Lite All-niter Sprint to the finish.)
I had to use Host Refresh because - apparently - my highly Lite/tweaked Win10 isn't compatible anymore with Cumulative updates.
When I've used Host Refresh in the past, all my (or at least all but maybe one) of my custom settings/tweaks/registry hacks survived the refresh and I didn't have to touch anything to be back up and running.
But this time, something changed bigly. I'm thinking that Microsoft has changed Windows so much since Win10 1903 that old setting sometimes don't carry over into new locations.
For example, so far I've had to:
I don't see the Visual Performance settings anymore. So now I have shadows on window frames.
It's still too new to know what else changed/broke.
Still, I suppose this is better than spending a week trying to remember and redo the hundred (?) tweaks I've done to Windows over the past five years.
But I think that my Host Refresh days are numbered.
Oh no! WordPerfect won't start now. (As I attempt to spell check this.) Something about a side-by-side configuration is wrong.
I had to use Host Refresh because - apparently - my highly Lite/tweaked Win10 isn't compatible anymore with Cumulative updates.
When I've used Host Refresh in the past, all my (or at least all but maybe one) of my custom settings/tweaks/registry hacks survived the refresh and I didn't have to touch anything to be back up and running.
But this time, something changed bigly. I'm thinking that Microsoft has changed Windows so much since Win10 1903 that old setting sometimes don't carry over into new locations.
For example, so far I've had to:
- Rearrange all my desktop icons, because their arrangement was lost after the Refresh. (Both Admin and User accounts.)
- Reset my IP address. (From DHCP to Static. Rats. Where's that piece of paper with my IP on it?)
- Change my mouse pointer back to extra large.
- Reinstall the last display driver because Windows dropped back to an early Nvidia display driver after the Refresh.
- Change my NVME driver back to what I used before the Refresh.
I don't see the Visual Performance settings anymore. So now I have shadows on window frames.
It's still too new to know what else changed/broke.
Still, I suppose this is better than spending a week trying to remember and redo the hundred (?) tweaks I've done to Windows over the past five years.
But I think that my Host Refresh days are numbered.
Oh no! WordPerfect won't start now. (As I attempt to spell check this.) Something about a side-by-side configuration is wrong.
My two new posts above were moved here by the Moderator. So my Observation about Host Refresh being able to keep an old Win10 alive might not be seen now.
Anyway, I gave up and restored my previous Win10. In addition to all the problems above, most which I was able to solve, my Refreshed Win10 said that it wasn't Activacted any longer. (This is on a Dell that came with Win10 installed from the factory. So I presume that there's a key hidden in the firmware somewhere.)
I don't know why Activation stopped working after the Refresh. I don't pay attention to what Microsoft is doing to Windows anymore. But IIRC, MS was moving more to force people into using Microsoft Accounts in order to use Windows. And I never have had a MS account.
Anyway, I gave up and restored my previous Win10. In addition to all the problems above, most which I was able to solve, my Refreshed Win10 said that it wasn't Activacted any longer. (This is on a Dell that came with Win10 installed from the factory. So I presume that there's a key hidden in the firmware somewhere.)
I don't know why Activation stopped working after the Refresh. I don't pay attention to what Microsoft is doing to Windows anymore. But IIRC, MS was moving more to force people into using Microsoft Accounts in order to use Windows. And I never have had a MS account.
You don't need a MS account for activation. If you previously activated the system, MS will remember the host's unique HW ID (assuming the HW hasn't changed since then). Tying a host to a MS Account allows for easier tracking of Windows licenses if you have several PC's or VM's.
Tnx. I'm tempted to use the old setup.exe method to install the Refreshed iso to see if that makes any difference. There were so many things that didn't transfer over when I did the Refresh this time. It's worked fine in the past with the old way of refreshing.
No hardware changes. Just refreshing in place.
No hardware changes. Just refreshing in place.
Last edited:
may i ask you, i tried yesterday a host refrersh and it said "failed to install windows 11" any clue how this can happen?
It has been a few months since I had this problem. (It seems like years due to Old Age.) So I don't remember very much. I remember that I had to do a work around of sorts to do a Host Refresh of my Win10. First made a new iso with a recent version of Win10 with cummulative updates only. I used Setup with Keep Personalizations. Reboot and test. Then I used NTLite Live to begin removing components in interations. (Fonts, Language, Keyboard.) Reboot and then remove more components. Reboot, test, and so on. I think that Windows (and also NTLIte) has(have) changed so much over the years that one big ISO Host Refresh can't work anymore.
Sorry that I can't be more help.
Sorry that I can't be more help.
Last edited:
dont worry at all my friend, sitll thanks for answering rather quickly, hope all got sorted out for you so far
