![]() I never understood why DotNet3.5, an "optional feature", was distributed as a. That has to be a bug (Microsoft or NTLite) with the sequence/order of how KBs are processed, either on 1st boot, or during NTLite customization process. I'm not sure why/what this change-of-sequence affects internally ( WRT 1st boot activities and dependencies ) ? In either case, DotNet4.8 CU (either KB5007152 or KB5004752) will successfully integrate. B (a 3rd Phase, separately, with an image load/close operation) *) Add DotNet4.8 Feature Package (KB4486129) during Pass #2. *) Add DotNet4.8 Feature Package (KB4486129) during Pass #2 (At the same time I'm adding DotNet3.5) ![]() I changed my/the sequence-process as-follows in the following way: I have it working again I can now successfully integrate latest DotNet4.8 CU (either KB5007152 or KB5004752). DotNet4.8 Cumulative Update (kb5007152) Remove/Trim unnecessary editions (datacenter, etc.) That exact process still works just fine on Win10_Ent/IOT_LTSC_2019 This exact processed previously worked with older KBs in SVR2016/v1607 The problem with that theory, however simplifying: (And that it should always be done post-OS-Install)Īnd perhaps this is simply my amature mistake in strategy. I'm beginning to think that DotNet4.8 Feature Pack (KB4486129) was never meant/intended to be integrated into the image using ADK/NTLite? Exec: not able to pre-stage package: Package_5_for_KB5004752*** clrjit.dll, mscordacwks.dll, etc.īah! Same result using the ISO. CBS Failed to process single phase execution 0x800f081f CBS_E_SOURCE_MISSING Add Misc KBs (Intel Microcode (KB4589210), Adobe Flash Removal (KB4577586), etc.) DotNet4.8 Cumulative Update (KB5004752) I'm going to ask for an exception, and get approval to try/use the November 2021 DotNet CU (KB5007152) instead of August: Registering 1st boot stage, all at the same time has a dependency, or a post-install-bootĪn earlier build in 2020, using KB4552926 (instead of KB5004752) worked perfectly fine with the exact same procedure. I'm suspect this is the result of process order/sequence problem.įor example, perhaps one of the other KBs I'm integrating at the same time is also Moreover, after 1st/2nd boot (with the rollback delay), KB5004752 manually installs just fine on resulting image fine. (Confirmed that resulting installed OS image does not list it as successfully installed). However, during 1st boot, it causes an extreme delays, and eventually "rolls back" this KB. It installs/merges fine during NTLite build process. ![]() I have some difficulty with KB5004752 ( the August 2021 DotNet4.8 Cumulative Update) on WinServer 2016 (v1607) I want to ask the collective brain trust about a KB/DISM error causing a roll-back on first boot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |