On upgrade, if you have deployments requiring approvals that reference built-in CIs created before 1706, you will see significant SQL I/O and high CPU utilization on the MPs as the CIs and deployments are updated.

CRP certificate revocation is slowly processing and blocking the main thread in SMS_CERTIFICATE_MANAGER.When you edit an existing co-management policy, instead of the changes being saved, the policy is reset to the default state of No AutoEnroll, all workloads are set to SCCM, and pilot collection is empty.OfflineServicingMgr leaks handle and cause a decrease in performance if it fails to find the content library location on a UNC path.OfflineServicingMgr fails to find the content library location when the Content Library is on a Universal Naming Convention (UNC) path.Ccmexec crashes continuously when Pull DPs are installed.CMPivot fails to run a PowerShell script that contains a command to retrieve a registry entry if the registry value contains a NULL.CMPivot is missing the “not like” operator.The SCCM console crashes if you create or edit an ADR and set the deployment package to “No deployment package.”.CMPivot cannot run a PowerShell script that contains a command to retrieve a registry entry if the registry contains a NULL value.After the deletion action, the area remains in either an “active” or “deleting” state. Task sequences that have a restart action before an Install Packages action may fail. SCCM 1806 Known Issues fixed.After the WDS-less PXE responder service is configured after an upgrade to SCCM 1806, it may reject PXE-boot requests from clients when the management point (MP) is remote.

I will try to update it whenever Microsoft releases new hotfixes. The following list provides SCCM 1806 Known issues. List of SCCM 1806 Known Issues – Documented 2 List of SCCM 1806 Known Issues

Event 2001 microsoft antimalware