When I invoked host refresh with you newest release it automatically started to do an upgrade with out me doing anything. I stopped the process by ending the ntlite process with the task manager. Yesterday I had to do a fresh install as the result of this.
Host Refresh: NTLite v2025.01.10258
- Thread starter Bournesup
- Start date
- Messages
- 3,948
- Reaction score
- 1,652
It now allows for no-edit host refresh.
You can pick preset or manual stop before continuation like before.
This was an upgrade, as people want to use their custom images, without necessarily editing on-the-fly as well.
Especially if ESD compressed.
You can pick preset or manual stop before continuation like before.
This was an upgrade, as people want to use their custom images, without necessarily editing on-the-fly as well.
Especially if ESD compressed.
If I understand what you are saying. I can make a custom iso via ntlite, then use that Iso to perform the host refresh. What just happen to me was I used the non custom ISO pick a preset, but it it did not show the integration of the updates etc. It bypassed that step, which then I was forced to perform a fresh install.
- Messages
- 3,948
- Reaction score
- 1,652
Oh, testing confirmed the preset is not loaded in that scenario - basically I broke data refresh with the skip image loading option.
Btw you can close the Windows setup.exe continuation or image saving, before it reboots the first time you're safe to abort.
Working on it, will reply here when done (probably today).
Thank you.
Btw you can close the Windows setup.exe continuation or image saving, before it reboots the first time you're safe to abort.
Working on it, will reply here when done (probably today).
Thank you.
- Messages
- 3,948
- Reaction score
- 1,652
Thanks.
New guid file is created when image is changed - saved, then loaded, while for the same source it will always be identical (ovewritten).
Are you suggesting for autosave to be off in a session where Host Refresh is used?
I would like to understand why - what's the difference since it's a full tool being open and processes the image - are you having a different stance towards it when it's a Host Refresh wizard?
New guid file is created when image is changed - saved, then loaded, while for the same source it will always be identical (ovewritten).
Are you suggesting for autosave to be off in a session where Host Refresh is used?
I would like to understand why - what's the difference since it's a full tool being open and processes the image - are you having a different stance towards it when it's a Host Refresh wizard?
Before this version, previous version always created a new preset file, thus perserving the integretity of the imported preset. The imported preset had info on the autounattend.xml file, and included post setup execution files.....
Last edited:
Has the mechanics of host refresh changed. If I compare version NTLite_setup_2024.11.10169_x64 to the current version, not only does that version load the preset, it allows one to make changes berfore invoking start the process. The preset that is imported is not over written but a new preset is save as well with a different filename.
@ilovemycactus on Discord reported the same problem. I walked him thru a Host refresh to restore WU components.
Here is my point. I have been using HOST for several years now, and had no problems until now. So, again whats changed? Secondly, it has been suggested by Nuhi when Host refresh was introduced to use this method to install the current cumulaled update, then use remove reinstalls afterwords.
Last edited: