Search results

I'll just wait for nuhi to reply to this thread. I already gave as much information as I possibly could from the observations during the update integration process, plus the preset information as well. As for what updates get removed depends on alot of factors. Supersedence, and what...

When you reinstall kb2670838 and monitor the winsxs folder (sort by date) you will notice some entries get reinstalled

I checked before using the cleanupmgr. Although it says it was integrated, it somehow gets removed during the component removal process. If you check installed updates, it is not listed. I checked it in a virtual environment and after a fresh install and in both cases it was not listed...

Try to integrate only updates without removals or tweaks, after that, remove components. I have tried that approach, and get the same results. Monitoring the winsxs during the integration process into the mounted wim suggest that there is a xps component directly related to kb2670838 as well...

bump I presently use the windows update downloader with the convenient rollup. KB2670838 gets removed somehow with your new version during the customizing. However, 1.3.0.5020 does not remove this update. The preset is the same as above other than the version of NTlite being used. The video...

It has been confirmed it is the spectre patches that causes the host driver to crash. The crash is between the VM and the host. Guess, I will need to be patient as newer updates are released to address the spectre issue.

I think you misunderstood what I am saying. Integrating the updates first, then customization next. When I check the features page after integrating the updates first it shows the IE-11 is disabled. When I compare the files in the "program files\Internet explorer" folder I know from...

If I integrate the updates {which includes ie-11} first, creating a base ISO, then remount the wim. The resulting features indicate IE-11 has been disabled, in which the opposite is true.

I presently use the windows update downloader with the convenient rollup. KB2670838 gets removed somehow with your new version during the customizing. However, 1.3.0.5020 does not remove this update. The preset is the same as above other than the version of NTlite being used.

Windows 7-x64 I have been using 1.3.0.5020 which I found extremely fast when it came to removing printer and modem inf files. Your new version takes each inf and parses it to dism.exe for removal. I found the process to be 35 minutes longer for this operation. I switched back to 1.3.0.5020...

I am currently using ntlite version 1.5.0.6025 (latest). After integration and customization and checking windows update in a virtual environment it indicated that kb2670838 needed to be reinstalled. However, that update is included in the build originally (Note preset, file attached). This...

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase is only supported by windows 8 and above. Thus I was curious to see that option to enable resetbase. I enabled the option. I then ran CMD (admin mode), and it showed command not recognized. Moderator note - Related thread here.

I tried 1.5.0.6025 success the registry value was set correctly, however, the desktop icons, and folder options were not. I included a copy of my preset. The current preset does not have the same tweak section as the previous preset. Correction, my apologies, tweaks are now under the...

Secondly, the version after that showed that kb4038803 that sp1 needed to be installed as a prerequisite. Which I thought as strange since I am using sp1 already integrated into the ISO. And the ISO came from microsoft.

My last tool update which I have, and haven't tried was 1.4.1.5590. When I bought the tool, it allowed for one year of updates. Is there a difference in how the reg file is applied. There is only a slight difference...

The question is with regards to using ntlite. The integration of the above two rollups being successful is when the registry key is present. This is during the integration process of installing the updates.

Lately, the rollup updates for January and February of 2018 require this registry flag to be set Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000” I've tried integrating the...