Search results

I am still having issues with version 2024.8.10045. This worked for ages on this network and now it does not. I'm not above thinking it is something on my network, but don't have all the information to trace it. I don't see any blocked URLs on my firewall logs, even turned off all security...

I'm curious what that 'own server' DNS name is so I can see if a content filter or something has it miscategorized possibly.

What host is the update trying to connect to? I'll see if it is getting caught somewhere.

Happening on another computer with an older version and another computer in another network. Guessing something beyond my environment is the issue.

Getting the following error message when I was doing an update check for NTLite - so I did a manual update to the latest version. When checking for Windows updates, I get the same message.

In previous versions I would go to Post-Setup and put in the MSI for Edge with /qn. Now I see Before Logon and After logon. Wondering which I should use for an Edge MSI install. Thanks!

Thanks so much for that. PowerShell even....love it :)

See a lot of threads on getting rid of Defender, but not trying to do that. What folder(s) should I add to the exclusion list in Defender when I am creating ISOs? That way if I forget to turn it off it doesn't go slow.

Thanks for confirming. Moral of the story kids? When in down - download a new ISO!

I think so since it shows 19045.3803 as the build. Guess that was a gimme :)

Got a new ISO from the MCT, and when I go to add updates, shows this: Does that mean the ISO I downloaded already has the 2023-12 updates installed?

Will get a fresh ISO. I have probably had this ISO since 22H2 went RTM.

I see what you are asking for.

It's a downloaded 22H2 from media creator. 10.0.19041

Trying to do a Windows 10 22H2 ISO and getting a couple of updates - KB5033372 and KB5031988 that NTLite skips. Trying to figure out why. Anyone have any thoughts?

Getting this when trying to add to a original 2016 ISO. Just doing 2016 Standard (Desktop Experience)

Thanks, trying it again with just the Standard edition. Getting to the point where 2016 won't be in use, just updating out of habit!

Is this still an issue with 2016? Last few months I have been updating my ISOs after the updates come out, and the CU is always not checked. I force it, and get an error when processing.

I'm reading this thread and I just put /qn /norestart in post setup. Do I need to copy this file somewhere? Or change something in the ISO? I am doing the updates directly from the MS ISO. EDIT - I tried in a VM and it was installed during setup. :) I only added it in that spot in NTLite.

Thanks. I did see that, thought it might have been something else. Now that I think about it, I had a 2016 system or two that kept bombing on that update. Maybe it will be corrected in 2022-05 :)