Recent content by splinterededge

Bump.

Any thoughts?

Notably, the I do get the desired behavior with registry files, but these symlinks point to a file and instead of a folder.

Bump. It would be a nice improvement if I could subscribe the parent directory containing these symlinks to my repository of drivers.

I use symlinks to bridge together the resources for the system images that I make with NTLite and Powershell. This saves me the trouble from making multiple copies, having out-of-date items or breaking a configuration or scripts because the filenames may have changed. Sometimes I symlink apps...

I will test this soon, probably in a few days. I would expect that this one is probably well under control so I am going to change the post name to resolved. Thanks fellas.

I have never tried to integrate netfx3 without the en-us lang pack that goes with it. Are you saying that I can integrate netfx without the lang cab? I will happy to try that next time i am tooling around. I will probably starting working with v201h in a few weeks, If it happens to reoccur...

sorry for the delay, its been a very busy week for me. I have went ahead an attached the en-us cab that throws the error during integration. This is from the iso: 6f80e72cc86eeff01f17b11af160cf598cda4ec0 *en_windows_10_business_editions_version_1909_updated_jan_2020_x64_dvd_e9cb5542.iso

bump

NTlite v1.9.0.7290 does not want to integrate NETFX3 cabs into the following unmodified iso: 6f80e72cc86eeff01f17b11af160cf598cda4ec0 *en_windows_10_business_editions_version_1909_updated_jan_2020_x64_dvd_e9cb5542.iso This also seems to have occurred when attempting to integrate netfx35 with...

Interesting, if you trigger the DISM cleanup a second time during the feature add/remove run it will reproduce the error. So it probably related to pending changes related to the updates. Generally speaking if I am integrating updates with I tend to avoid any update cleanups until after OOBE...

Also, since when have I been a "new member" :) I'd think to think of it as new forums.

So it seems that separating the two runs does indeed avoid the DISM - Error 0x800f0806 '[2054]' in my case.

I just hit this same snag, I am going to try to run the updates and features in separate runs. I will let you know if DISM decides to complete the cleanup.