- Messages
- 3,941
- Reaction score
- 1,648
Confirmed, but has nothing to do with NTLite.
Load/mount boot.wim, Explore Mounted Directory and extract with elevated 7-zip the same update content to the: .\Sources directory.
Save the changes and try then, confirmed working.
Now that this dynamic update integration became a bit more complex, will add support in the tool and update lists.
Load/mount boot.wim, Explore Mounted Directory and extract with elevated 7-zip the same update content to the: .\Sources directory.
Save the changes and try then, confirmed working.
Now that this dynamic update integration became a bit more complex, will add support in the tool and update lists.
W
Windows 10 User
Guest
I didn't have this problem after loading boot.wim on NTLite, clicking on Explore Mounted Directory, extracting the update content to the C:\Users\X\AppData\Local\Temp\NLTmpMount01\sources directory with elevated privileges and creating an image. Previously, I was extracting it to the extracted ISO content sources directory (I didn't need elevated privileges), loading install.wim on NTLite, creating an image and I wasn't having this problem. Maybe the update wasn't being applied? I don't know why we must use elevated privileges if doing the former/your way. What do you mean by saving changes, create a new ISO?
So, will we no longer need to extract it to a sources folder for it to be applied but just integrate it like we do with the other updates on NTLite?
I was told integrating KB4599861 didn't cause this problem.
W
Windows 10 User
Guest
Thanks, problem fixed. Anyway, I thought most updates were already called "Dynamic Updates" like it's told here.
Last edited by a moderator: