Search results

Network drivers indicate that they are running correctly in the virtual environment. I do not run wifi. I double check vbox settings and it does show a network adapters are bridged. You are right, there is no internet connection in the vbox environment. Thank you for always pointing me in...

Interesting. Does it have anything to do with Hyper-V paravirtualization. The Clean Iso means no customizations?

Prepraration to migration to Windows 11, Been using vbox (latest Release) to verify w11. However I get the following error. I took a screen shot. Is there a setting that I am missing .

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.

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...

Unfortunately it is this entire thread. Host refresh is automatically invoked when selecting the preset. The preset is not actually loaded. The preset is automatically overwritten. I had to stop ntlite app via task manager.

Unfortunately the problem still exists with this version NTLite_setup_2025.2.10293_x64

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.....

Everything looks good except for a small item. The autosave preset file is over-written. This file is meant for a fresh install and shouldn't be over-written. Before this addition a new GUID file was created base on the imported preset.

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...

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.

Another way is to extract the contents of the zip file to a new directory, name it DXinstall; Before compressing the directory with 7zip rename #install.bat to install.bat. Use 7 zip to compress the contents of that directory Create a config.txt file with following contents ;!@Install@!UTF-8...

Here is a comparison of version 10169 and your current version. Version 10169 performed with no issues, and your current version 10208 stalled at reading updated data.

NTLite version 2024.12.10206_x64 exhibits the same problem.

The problem still exists.

The ntlite process wasn't using any CPU resources at all. It was stuck at 0% utilization. From the task manager I end terminated the NTlite application and then restarted it. Remount and continued the process. Anyway, I downloaded your new version and will report back.

Well, I got it to work, but not ideal. I ended the ntlite in the task manager, relaunched ntlite, remounted and click on process. I will revert back to the previous version.

I tried what you suggested and still the problem persists.

That is interesting. I reinstalled the previous version and had no problems. Then re-installed the current version and ran into the same issue. The point is I was not using temphostrefresh.

%SERIAL% suggest that the computer name would be dependent on the S/N of your mother board. For me a randomly generated characters based on a random generator would ensure there is no exposed info about your hardware would be present in the computer name.