I’ve noticed that the last two times I installed McAfee, the WebAdvisor driver was no longer installed, even though the WebAdvisor browser extension was installed successfully. Previously, McAfee would install both the browser extension and a separate WebAdvisor driver, which could also be uninstall […]
Hi nickstar1. This looks like a
packaging/architecture change in the McAfee suite, but the missing entry alone does not establish that McAfee has eliminated every WebAdvisor driver or local component.
One terminology point: the item previously shown in
Add or Remove Programs was the WebAdvisor Windows application package, not the driver itself. That package could install a service and possibly drivers, but Windows does not normally expose an individual driver as an uninstallable application.
The current situation appears to be:
- The browser extension handles URL reputation, malicious-site blocking, search-result ratings and related browser functions.
- When the full McAfee product is installed, file scanning and lower-level protection can be supplied by the main McAfee engine rather than a separately registered WebAdvisor package.
- Consequently, recent suite-managed installations may install only the extension and no longer create a separate McAfee WebAdvisor uninstall entry.
- An extension-only installation can still perform its principal browser protections, but it cannot independently perform arbitrary system-level or filesystem operations. Those either come from the main McAfee product or are unavailable in that configuration.
WebAdvisor itself has not been generally discontinued. The current Edge extension listing shows an actively maintained extension, while McAfee’s WebAdvisor page still describes a Windows setup program and features such as Safer Downloads and Security Check. Therefore, it would be too strong to conclude that the standalone component has been removed everywhere; McAfee may be using different deployment modes for standalone WebAdvisor and WebAdvisor bundled with its security suite.
You can verify what your particular build installed with:
Code:
Get-Service | Where-Object DisplayName -Match 'McAfee|WebAdvisor'
Get-CimInstance Win32_SystemDriver |
Where-Object {
$_.Name -match 'McAfee|WebAdvisor' -or
$_.PathName -match 'McAfee|WebAdvisor'
} |
Select-Object Name, State, PathName
Also compare the McAfee application build and browser-extension version between the old and new installations. The absence of a WebAdvisor service, folder and uninstall entry would confirm that this installation is genuinely extension-only rather than merely hiding its uninstall registration.
Bottom line: the separate WebAdvisor package is not required for the extension’s basic site-reputation functions. In a full McAfee installation, its former local duties can be consolidated into the main product. I would not force-install an older standalone WebAdvisor package merely to restore the old Programs entry; that could duplicate components without adding meaningful protection. McAfee has not provided a sufficiently clear public change note to attribute the change to one specific release, so the exact rollout boundary may depend on build, region or installation channel.
Sources
