Search results

Yeah, I guess nuhi can confirm if that is related to Windows or NTLite. As you said, at least to add warning, because for Capability Access there's no such warning, and some other components have it (breaking start menu for example).

I think with UEFI boot, bootres.dll (usually) is not used?

One more thing to report for LTSC. Removing 'Capability Access' (capabilityaccess) breaks Start menu (left click, right click still works), as well as immersive control panel.

I think I have something similar to report for LTSC, I'll check today and report back. EDIT: I removed these components, and they are still present, meaning they are still available for removal (not sure if they are removed or not).

I'm interested in this as well, but looks to be difficult. I've read somewhere that even modifying bootres.dll (actually signing) doesn't work on LTSC and later versions.

I noticed that after some component was removed folder was still present in WinSxS, thought kinda empty. For example I removed 1394 driver but folder amd64_1394.inf.resources_31bf3856ad364e35_10.0.17763.1_en-us_5380d7967a090394 is still there with 1394.inf_loc file inside (sys file was removed)...

I noticed that iso built after W10UI had winre.vim which wasn't present in iso built afte NTLite integration, so difference in size is actually ~140MB.

I noticed that NTLite built image had .cab file of KB4586793 in c:\windows\SoftwareDistribution\Download, and one built by VM10UI did not. Though that cab is ~340MB and difference is ~100MB.

I've tried W10UI, and I can confirm that with ResetBase final iso image is ~100MB smaller, which is nice. Tested it in a VM, all looks good.

Thanks AeonX I'll try W10UI,

Worked for me with ResetBase without problem. And procedure as George King mentioned, couple of clicks, can't be more simple.

Thanks Clanger Is there a difference in using abbodi86 BatUtil vs what I used as suggestion by George King? I believe NTLite is doing what I found in description of BatUtil: "Enable .NET Framework 3.5 if available source detected, and reinstall Cumulative updates afterwards." I guess because...

I did what George King suggested, and it worked. I added all updates, .net 3.5 in one pass, selected ResetBase, and it worked. It took more time then usual, I think before integrating .net 3.5, it did ResetBase and then got back to 3.5. Also, I found forum topic from, I think, 2 years ago about...

George King, thank you very much. That did the trick. I didn't know I can use Resetbase with .Net 3.5 as it was giving me message that some task as pending.

nuhi Clanger Any advise on this issue?

Hello. I have a strange issue with integrating .NET 3.5 (using template in Updates section). So I start with fresh LTSC x64 iso, I remove regular edition and leave just N, create iso from that. Then in second pass, I add following updates: KB4465065 KB4587735 (latest servicing stack update)...