Recent content by jailbird

  1. J

    Install KB50095555 on Server 2022

    Okay, I finally figured it out. For some reason, removing SMBv1 breaks updates on Server 2022. Why? No clue! :) Also, including KB5010796 also breaks things. For some reason, if you add that, after you install it'll attempt to reinstall KB5010796, but with a "[Corp Intranet Required]" prefix...
  2. J

    Install KB50095555 on Server 2022

    Just checked, NTLite says that: KB5004330 KB5005039 KB5005552 - Fix for ServicingStack 10.0.20348.169 Are all preinstalled in the .wim
  3. J

    Install KB50095555 on Server 2022

    Nope, other than the fact that NTLite's update check and Windows' native update check doesn't suggest that one. Since that update was released Aug 10th and RTM of 2022 was released Aug 21st, I'd hope it would already have that. Let me load the .wim into NTLite and looked at the preinstalled...
  4. J

    Install KB50095555 on Server 2022

    Of course, duh! Here it is!
  5. J

    Install KB50095555 on Server 2022

    I know removing components in Server 2022 is unsupported, but I'm hoping somebody else has figured this out for me... I've carefully removed components in 10 LTSC and also Server 2019 in the past and never had a problem once I gone through the trouble and figuring out which components can and...
  6. J

    NTLite clobbering its own SetupComplete.cmd?

    And that's exactly what I'm doing now :). Thanks for the tip!
  7. J

    NTLite clobbering its own SetupComplete.cmd?

    I'm checking the one outside of the .WIM (the one inside the $OEM$ folder), maybe that's why? I didn't even think to check inside the .WIN. I have it happen even when not loading any preset at all. I'll try and narrow it down to a better test case. Thanks for the reply!
  8. J

    NTLite clobbering its own SetupComplete.cmd?

    Awesome, thanks. At least I know I'm not crazier than what I thought! So I worked around it by copying the good one out from underneath it, and then once it finished, copying it back over the bad one. Seems to work swimmingly then!
  9. J

    NTLite clobbering its own SetupComplete.cmd?

    I'm running registered NTLite 1.8.0.6650 64-bit working on a LTSC 2019 image. Right after NTLite processes the Post-Setup part, the SetupComplete.cmd file looks correct: @echo off powercfg /hibernate off net accounts /maxpwage:unlimited msiexec /i...
  10. J

    Task Scheduler wouldn't start: Time Broker Service

    Makes sense! I was doing somewhat similar by making a VM in VBox, then making a snapshot before I booted off of the ISO. That way if it didn't work, I could just revert to the clean snapshot and let it reinstall again. Not quite as fast as your method, but it sure as hell beat...
  11. J

    Task Scheduler wouldn't start: Time Broker Service

    Sorry if this is a dupe, I didn't find anything in a search. This is just a heads up to save others the headache I went through for about a week trying to figure out why Software Protection Service was bouncing every few seconds and why Task Scheduler wouldn't start: Time Broker! Time...
Back
Top