Windows 10: DCom hardening breaks remote WMI in Windows PE

I recently found out that the DCom hardening soluition Microsoft shipped with the June updates causes remote WMI from Windows PE to fail with an access denied message. When implementing the temporary registry key workaround, remote WMI queries do work.My situation is one where I use a pre-start command in the Configuration Manager boot image to run a powershell script that uses WMI to query the configuration manager environment to check the local UUID against the database to see whether a system is already in Config Manager. The script uses a valid user account for the WMI query. With the June

:)

 

Windows Distributed Component Object Model (DCOM) Hardening changes

Read more:

• https://docs.microsoft.com/en-us/win...ge-center#2817
• https://support.microsoft.com/en-us/...e-37ed901c769c

 

Application of settings described in KB5004442 DCOM hardening

Hello,

The updates described in KB5004442 which will be coming in June of 2022 will "force" a hardened DCOM setting for clients. Will these changes be released in the cumulative security update for the month of June or will it be a separate update? If the June update is skipped, will the changes be applied in future cumulative updates? If a user were to skip the June 2022 update which applies the hardening settings in KB5004442, would the settings be applied in any future cumulative update?

 

Windows 10 update to 1511 breaks wireless internet connection

Hi Sachin,

WLAN Autoconfig service is already running and the startup type was already automatic.

The dependent services listed with WLAN Autoconfig are:

• Remote Procedure Call (RPC)
  • DCOM Service Process Launcher
  • RPC Endpoint Mapper
• Windows Connection Manager
  • Remote Procedure Call (RPC)

All of these services are running and configured for automatic startup, but I still have no internet on the Wi-Fi.

Any other suggestions?