Windows Discovery is not fully working when administrative shares are disabledIssue Administrative share c$ is required for discovery to fully function. If you disable administrative shares via setting below registry key:HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters: AutoShareServer=0then restart server service:net stop server net start server===once this is done, below features will stop working: AWS/Azure pattern steps in Windows OS patterns, and ADM probe and File based discovery probeReleaseAll ReleasesResolutionWhen the registry key is set to zero, it defaults back to C:\temp, and if user has turned off C$ share then it will create the discovery to have issues. From checking our source code we can confirm c$ is required by discovery, and setting AutoShareServer=0 in the registry will cause issues to discovery. We also confirmed in the lab, it's not only causing issues to AWS/Azure pattern steps, it will also cause issues to ADM probe and File based discovery probe