Manage Roaming Client Conflicts with Windows 10 Version 1809

Available Languages

Download Options

  • PDF     (14.3 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (81.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (67.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 7, 2025
Document ID:225155

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes newly introduced software conflicts between the Umbrella roaming client software and Windows 10 version 1809.

    Background Information

    If you are considering updating to Windows 10 version 1809 (October 2018), and a roaming client release earlier than 2.2.192 (June 2019) please read this article for more information. This condition also applies for prior versions where Hyper-V is enabled. 

    Windows 10 version 1809 and the Roaming Client

    Windows 10 version 1809 brings support for new security minded features such as built-in sandboxing. In order to enable these features, Microsoft makes use of the Hyper-V infrastructure it has developed for server-hosted virtualization. In order to enable local virtualization, the Hyper-V (default switch) network interface has been deployed and enabled by default in Windows 10. Workstations updating to this version notice the new NIC after the upgrade has completed, even if the Hyper-V role is not enabled.  

    The presence of this Hyper-V NIC with implied network sharing is currently known to cause interoperability challenges with the roaming client. At this time, the AnyConnect Roaming Security Module is not known to be affected. 

    DNS Suffixes 

    The impacts of this interaction between the Hyper-V nic and the roaming client today are:

    • High CPU load for dnscrypt-proxy.exe
    • Excessive repeated DNS queries to local DNS, for example:
      • WPAD queried: wpad.<domainsuffix>
    • Intermittent local DNS interruptions

    These impacts can be isolated to the workstation; however, in some cases the additional DNS traffic caused by this interaction can overwhelm local DNS servers. 

    Impact Confirmation

    To confirm that the roaming client-Hyper-V interactions are the root cause of these symptoms, there is a simple confirmation test:

    1. Open up the network and sharing center
    2. Click to view network adapter settings
    3. Disable the Hyper-V network adapter
    4. Confirm if all symptoms immediately disappear. 

    Resolution

    At this time there are steps that can be taken to minimize these impacts while the Cisco Umbrella team develops a permanent resolution. To learn more, please contact the Umbrella support team at umbrella-support@cisco.com.

    This issue is resolved in version 2.2.192 or higher, released in late June 2019. Contact the Umbrella support team to learn more.

    Revision History

    Revision Publish Date Comments
    1.0
    07-Oct-2025
    Initial Release
    TAC Authored

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products