Recent content by dkdubya2

Okay, thanks. It worked this time under user, just weird seeing the desktop & installer list.txt. Some post setup app switches couldn't run without admin privileges, so will have to install those the regular way should I go this route with my final install. Just one more thing: Local Weather...

Thanks, but never mind; it's been such the while, I took some incorrect component removal steps that probably messed things up, because when I restarted the VM, post setup was of course skipped, but the install finished, so hopefully the problem is solved.

I had to come back to doing new NTLite sessions with my copy of Windows 10 build 1903, after the motherboard had to be replaced on my custom PC with a different brand which require different drivers so I couldn't use the very last saved installation ISO I burned to USB for the fresh install...

Isn't there a maximum size limit for how many programs can be integrated via SFX?

I am VERY happy to report, that update 8074 is working 100% for Win. 10 Build 1903, either with the Telemetry component removed, or with Telemetry elements disabled; KUDOS for Nuhi!

If even Microsoft advises to use unattend.xml over the "deprecated" Out of Box Experience (OOBE) settings since they've made other changes for recent Windows 10 builds, why don't they just delete them from all from the public answer file template they offer for deployment?

Same Telemetry break issue here with v2.1.2.8047 in fine-tuning my build 1903 twice, exactly the reason I came here to look-see if others were having the same issue as I'm in mid-session, so glad I did & will just have to leave that tweak alone & unload to see if update 8074 takes care of...

Nuhi, as I wrap-up my completed Win. 10 slipstream, I just wanted to give you kudos for is probably THE best feature you could have added to NtLite here, it eliminates about 50% of the overall grunt-work that had previously made DIY update integration such the chore!

Hi Nuhi, I never do ESD compression because I've always had wonky issues with reconverted install.wim images, just plain ol' unlucky in that regard. I trashed the ntlite.log since the logging stopped at doing the export before the subsequent crash, which it didn't mention. However, it turns...

During a late-night 1st session ( NtLite, v.2.1.2.8041, everything worked smoothly when processing, until it got to "Optimze image file structure (Export WIM)", where it slowed like a snail then crashed & closed at 36% after running 6 hours (I didn't catch the moment of the crash), & currently...

Since I finally had a successful NtLite Win. 10 1903 ISO made, I chose to go back & risk removing the win. defender component, then ran a newly created test Win. 10 ISO as a VM with no issues. However, I noticed that in services.msc in the test running Win. 10 VM, it shows WD as running and...

Finally, success! As per your advice, I was able to create a working Win. 10 ISO (no post-set up files) which I have saved, so I am currently doing another session to see what I can can safely add and/ or remove without any issues for a final desired ISO. BIG SIGH, thank you SO much!

Okay, Thanks for replying to all of my comments. From what I read myself in the log, the Windows Retail Product Key I used was validated, but it looks like setup couldn't see either my owner, or my organization name, despite my inputting them to what I thought was to spec. In any case, I...

This is the latest issue that comes at the very end of the VM test install, I added a local user & a guest user in the autounattend, then checked the outside autologon option with the main local user & pass info. If I can lick this issue, I think I'll finally be good to go for a working slipstream:

As a proactive troubleshooting measure, I removed my Windows 10 trial VM that uses an earlier build (was close to expiring anyway), & am now using an attached "Activated" 1903 Build ISO I found online as a Virtualbox VM to match the build I'm trying to slipstream & see if this make any...