Windows 10: Windows 11 24H2 unable to log into domain after applying security or cumulative updates

We have several brand-new PCs that came with Windows 11 24H2 installed. After the initial setup, they worked fine for a day or two until Windows updated. After that, users are unable to log into the domain we can't sign you in with this credential because your domain isn't available... After uninstalling the updates, all works fine again. This occurs with any security or cumulative update after KB5048667. I'm seeing constant event 7023/DNS Client terminated with the following error: Access is denied in the System Log. The last update that I was able to install without breaking things

:)

 

KB4457426 Cumulative security update for Internet Explorer - Sept. 11

Windows 10 does not have such a thing as a 'Monthly Quality Rollup', but Windows 7 and 8.1 do, it's their equivalent of the Cumulative Update. This patch must be intended for W7/8.1, Windows 10 does not need (and probably will refuse to install) this update because these fixes should have been in the Cumulative update we've just had.

Cumulative Update KB4457128 Windows 10 v1803 Build 17134.285 Sept. 11

 

Factory reset Windows 11 24H2 (build 26100.863)

Hi, I am Dave, I will help you with this.

There are no currently listed problems resetting version 24H2 of Windows 11 and no specific steps you need to perform, are you experiencing any problems with that insider build that is causing you to perform a Windows reset?

 

Windows Security Issue: Missing 'windowsdefender' in Windows 11 24H2 (26100.863)

Chewed on this for a day. My first post as well. Hopefully this finds people in the same boat.

KB5043950: Windows 11, version 24H2 support - Microsoft Support

Known issue

New Windows 11, version 24H2 devices that are intended to be onboarded to Microsoft Defender for Endpoint might require customers to enable the prerequisite feature. This affects all supported architectures.

IT admins might observe devices not being able to be onboarded to the Defender for Endpoint cloud service, and not receiving the expected protection as a result, even if Intune is expected to execute the onboarding sequence by applying an endpoint detection and response (EDR) policy. Intune will also display an error as it is unable to successfully apply the policy. Users may also not be able to connect to corporate resources if a Conditional Access policy is configured to require Defender for Endpoint being enabled and actively reporting in. Compliance status is visible in the Microsoft Intune device compliance dashboard. This might happen in one of the following scenarios.

• A user buys a new device that has the Home SKU. This SKU does not support Defender for Endpoint. Then the user upgrades to Pro using a Pro product key. This process, called “transmog,” does not install Defender for Endpoint, which is by design. The Defender for Endpoint agent is not correctly enrolled in the Defender for Endpoint service, and the device is not protected.
  
• A user buys a new device that has the Pro SKU, and the OEM did not install the required feature.
  

Important Defender for Endpoint has been removed from the base image for Windows 11, version 24H2 and needs to be manually installed whenever a device goes from Home to Pro.

Workaround

Use the Deployment Image Servicing and Management (DISM) command-line tool to install the Windows Sense Client from an elevated command prompt. See the command below.

DISM /online /Add-Capability /CapabilityName:Microsoft.Windows.Sense.Client~~~~

KB5043950: Windows 11, version 24H2 support - Microsoft Support