WaasMedic Agent Exe stopping me from working

For me the problem of 100% "Active Time" (Task Manager, Performance tab) has always existed as long as I can remember on Windows 10.  My initial investigations seem to indicate it was mostly McAfee I/O and indexing. 

What was new starting in January, was that the RATE of disk I/O in Resource Manager also started showing a constant 10 MB/s or higher for long periods of time EVERY DAY.  That disk I/O RATE appeared to be due to WaasMedic and was preventing me from getting a usable response to UI input (i.e. greater than 10 - 30 secs for a mouse click or > 10 - 15 sec for a keystroke response) for between 20 minutes to 75 minutes after pressing the power button.  This situation was unaffected by turning off indexing, and only mildly improved by turning on fast startup.

It is difficult to say exactly what is going on because when the disk I/O is so heavy that UI inputs are futile, invoking task manager with CTRL-ALT-DEL ('cause it is impossible from the desktop) can take up to 2 mins for the task manager window to appear, another 2 - 3 minuted got the window to fill in with information and allow me to access the performance tab.  Clicking "Open Resource Manager" takes another 2 - 3 mins for the Resource Manger UI to appear and sometimes another 2 - 5 mins before the UI fills in with processes and the graphs start filling in.  In the disk tab, "Processes with Disk Activity" pane WaasMedic is at the top of the list (sorted by "Total (B/sec)" column) and its IO sometimes clips with the max graph point at 10 MB/sec.  Looking down at the "Disk Activity" pane, there are usually multiple instances of WaasMedic running all referencing different files.  My guess is that since I am running dual 9-core CPUs I have 16 threads of WaasMedic running, at least that is how it appears.

With the disk activity entries jumping around all over the place and different instances changing position as top IO user, it is hard to bet a read on which files each instance of WaasMedic is accessing but it appears most of them are looking at master boot records and block tables.  This got me thinking back to the the fact that this problem seemed to have started shortly after the "optional" Flash removal update auto-installed.  Also of note was that this "update" COULD NOT be uninstalled / rolled back.  So, just as with SECDRV, I believe all this activity is a willful Microsoft strategy to MAKE SURE no one finds a way to re-install Flash or undo the update to the kernel that prevents Flash from being re-installed / run ever again.

So I believe if MS quit being so dictatorial about what legacy apps it will and won't let you run (usually tied to MS trying to force you to an MS alternative) this problem would be resolved.

Lisa Larkin. I have Dell SA installed but all tasks are disabled as to run automatically. There are 5 tasks available, neither of which actually replicate what WassMedic does. On the occasions I have had issues, Dell SA is not listed as running. It can can check for Dell updates but not Windows updates, it can check  for BIOS updates (effectively a Dell update), it checks for various driver updates, it can scan for hardware issues, it can optimise disc, it can can optimise network. It does not attempt to repair Windows Updates, this is what WaasMedic is supposed to do. The fact so many people are having issues I assume that not all contributors have a Dell computer so connection with Dell SA spurious.

There's a mix of issues here. Malware do target this program so if you see red flags of abnormal patterns in task manger then scan heavily. When a program is intergrade in the computer it will cause whole mess of problems when the infection starts. This what happens with some window 10 users who have adobe intergrade in their computers became target of nasty of no way to really to get rid of it. This makes the user much more a target by a horrible design.  

Another reason will be the damage the program will find due to updates not being updated. Corrupt files can occur since this program fix anything in the back ground. The longer updates are not install the bigger resources it will take to fix it. Not all updates need to be installed.

Other programs that run in the back ground can have conflicts and that will display resources intake. Anti virus programs is often the cause making other programs brake, not responding, hang up, and etc when they're running. 

Need to go through so much to get to the program itself problem if its the culprit. Many times people don't want to deal with a program interfering what they want to do and want to disable it. Then wonder why the computer isn't working correctly. The longer the problem not being fix will mean the longer the intake of resource will appear. Like command prompt searching and fixing files. This also the case of how big your drive is to scan. The program will take linger due to other program running.

Check your system event log for disk errors !

It seems disk (read) errors will invoke WaaZMedic and WaaZMedic will cause new disk errors to be logged.

I replaced my harddisk and now WaaZMedic at least stopped running on every boot.

(And why the hell doesn't Windows warn me for disk errors? I get popups for every insignificant issue but none for real problems!)