Uninstall VSE, delete all VSE registry entries/folders, re-install. I've had the same problem in the past and this has fixed it. Something with VSE bugs out and it won't update, I've seen all sorts of updating issues over the years.
Since this is a recurrent issue, Please enable McScript debug logging on the client computer, increase the log size to 10MB, reproduce the issue so that the debug information is captured in the log. Then collect a MER log and escalate to McAfee Support for investigation.
- Click Start, Run, type regedit and click OK.
- Navigate to the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator]
- Right-click on LogLevel and select Modify from the menu.
- Type 8 in the Value data box.
- Click OK.
- Create the DWORD Value entry for LogSize if it does not exist.
NOTE: This value defines the size of the log in megabytes. The default value is 1. The value needed for level 8 logging varies depending on evaluated function.
- Right-click the ePolicy Orchestrator key and select New, DWORD Value.
- Type LogSize in the New Value field and press ENTER.
- Right-click the new LogSize value and select Modify.
- Set the Value data to an appropriate size in megabytes and click OK.
For CMA or McAfee Agent level 2 debugging:
- Click Start, Run, type regedit, then click OK.
Browse to the key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared Components\Framework\]
- Right-click Framework and select New, DWORD Value.
- In the Name field, type dwDebugScript.
- Right-click dwDebugScript and select Modify.
- In the Value Data field, type 2.
- Click OK.
Any news on that ? Ive got the same problem.
I gave up in the end. All McAfee tech support would repeatly suggest was to apply the SuperDat.
Basically from what i could tell the update task was taking so long on our older/slower computers that the two update tasks were colliding and causing the issue.
We changed our update task to once a day instead of every 4 hours. The clients now update every morning 30 minutes after boot-up with a little randomization.
So far the problem hasn't come back.
I know it's not a real solution but you could try adjusting the gap between updates to see if it makes a difference.