Overview

This knowledge base article addresses reports of failed driver or firmware updates for the Dell DW5933e (MediaTek T700 5G WWAN) module on Windows systems after installing Endpoint Data Protection. In these cases, customers observed that the WWAN update works on a clean system, but fails as soon as the EgoSecure Client is installed. Reinstalling or uninstalling EgoSecure does not resolve the issue, which has led to the assumption that EgoSecure leaves residual settings or interferes with the update process. Detailed technical analysis confirms that EgoSecure is not the cause of this behavior. The update failure is triggered solely by the existence of a Windows CoDeviceInstaller registry key for the Network Adapters device class, which can be created by Windows itself or by any Microsoft‑compliant software. This issue occurs even on systems where EgoSecure was never installed, and can be reproduced using an empty registry key. The root cause lies in a defect or limitation of the Dell/MediaTek WWAN installer, which fails as soon as the Network Adapters class key exists, regardless of its content.

Symptoms

• The firmware or driver update for the Dell DW5933e (MediaTek T700 5G WWAN Global) module fails or aborts during installation.
• The WWAN module does not update despite repeated attempts.
• The issue occurs on systems with EgoSecure installed, but also on systems where EgoSecure has never been installed.
• After a clean Windows installation, the WWAN update may work initially, but fails once additional drivers or software are installed.
• The update failure persists even after uninstalling EgoSecure.

Environment

• Windows 10 / Windows 11
• Dell systems equipped with the DW5933e (MediaTek T700 5G WWAN) module
• EgoSecure Data Protection (any configuration, including USB-only setups)

Background

EgoSecure must register its CoInstallers across several Windows device classes, to ensure its filter drivers are properly registered for controlled device classes, including USB-based devices, which often appear under additional classifications in Windows, such as:

• Network adapters (including WWAN/mobile broadband)
• Bluetooth devices
• Portable devices (MTP/PTP)
• Storage or volume devices

This behavior ensures consistent enforcement of AccessControl policies across all relevant device types. These entries are technically required and fully Microsoft-compliant.

Root Cause

Technical Cause

Internal testing shows that the Dell DW5933e driver/firmware installer fails as soon as the following registry key for Network Adapters device class exists:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CoDeviceInstallers\{4d36e972-e325-11ce-bfc1-08002be10318}

Key details:

•    The key may be completely empty.
•    No EgoSecure reference is required.
•    The problem occurs even on systems where EgoSecure was never installed.
•    The installer fails solely due to the existence of this Network Adapters Class GUID entry, regardless of its content.

This confirms that the Dell/MediaTek WWAN installer performs a faulty or incomplete validation of the Network Adapters CoDeviceInstaller class key and enters a failing state once the key is present. This behavior is inconsistent with standard Windows device‑class handling and indicates a defect or limitation within the installer implementation.

Important Clarification

EgoSecure registers CoDeviceInstaller entries for multiple Windows device classes in a fully Microsoft‑compliant and technically required manner. These shared device‑class registry keys are used by Windows itself as well as by various drivers and applications. EgoSecure is not the cause of this issue. The failure is triggered by the WWAN installer’s behavior, not by EgoSecure’s presence or actions.

Why does the issue not appear on a fresh Windows installation

A fresh Windows installation contains only a minimal set of device class keys. Windows generates additional Class GUID keys dynamically once components, drivers, or applications initialize the corresponding device classes. Once the Network Adapters Class GUID exists -created by Windows itself, by EgoSecure, or by any other software registering CoInstallers - the Dell WWAN installer enters a failing state.

Verification / Reproduction Steps

The failure can be reproduced without any EgoSecure installation:

1. Ensure EgoSecure is not installed.
2. Confirm that the following path contains no subkeys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CoDeviceInstallers
   Note: If this is not a new Windows installation, subkeys might already exist for one or more device classes.
3. Manually create the following empty registry key of type REG_MULTI_SZ (no value): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CoDeviceInstallers\{4d36e972-e325-11ce-bfc1-08002be10318}
4. Run the Dell DW5933e WWAN firmware or driver update.

Expected result

The update fails, confirming that the issue is unrelated to EgoSecure. This demonstrates:

• The failure occurs independently of EgoSecure.
• An empty Network Adapters Class GUID key alone triggers the problem.
• The content of the key does not matter.

Solution / Recommendation

• EgoSecure’s CoInstaller entries are technically required and Microsoft-compliant.
• These registry entries cannot be fully removed during EgoSecure uninstallation, because they are shared device-class keys used by Windows and other software. Microsoft requires that software using these keys only adds or removes its own content from the key, without further interference, to ensure compatibility.
• The update problem must be resolved by Dell or MediaTek, as it is a driver setup defect.
• Customers should provide Dell with this analysis when opening a support case.

Summary

• EgoSecure’s CoInstaller entries are necessary and Microsoft-compliant.
• These entries must not be fully removed because they are shared device class registry keys.
• The Dell DW5933e (MediaTek T700 5G WWAN) update fails even without EgoSecure installed, as soon as the Network Adapters Class GUID exists -even if empty.
• The root cause lies entirely in the Dell/MediaTek update logic, not in EgoSecure.