WaasMedic Agent Exe stopping me from working

I am getting this on all 3 of my PC's an 'Intel i7' (2 yr old) and a 'Ryzen 7' (6 months old which was stated by Crucial on a check that it was the fastest they have seen).

Then there's my old trusty 10 yr old 'Medion Akoya' which has a 'Samsung 500 SSD' hard drive in as the main 'C' drive with the Old 1TB HDD being utilised internally as a Second Storage Drive. Then there is another removable 1TB 'Medion' Back Up hard drive that slides neatly into a specifically designed bay on the top of the case. So I don't think its just on Older machines as all three are getting this sudden 'Whooah -All Brakes On' lately that so many people are suffering from.

It doesn't last long I agree but to have it occur at times when its the last thing you want to happen causes great concern for obvious reasons and is driving us nuts.

Evil thought about this app:

It is ther to push people to upgread ther Systems. It makes your live wors and wors on older hardware, but on newer it eaven bother you that much and it eaven do not scann the things it scanns on older mashines whitout any SSD.

I had this problem immediately after signing in this morning. CPU utilization (the usual cause of slow performance on my old machine) was fairly low but disk active time was a solid 100% for several minutes. This has been happening to me at startup for several months, but not every time. It seems to correlate with whether I leave my OneNote window open while putting the PC to sleep for the night, and the duration of the high-use event seems to correlate with how long it's been since I last closed OneNote. I keep 2 Task View desktops open all the time and usually keep OneNote loaded in one of them, and I rarely sign out of my Windows account at all

When this happens, I notice that it isn't just slow after I sign in to my Windows user account. There's also a much longer delay between the appearance of my lock screen background and the presentation of my pin entry field, if I hit the spacebar to open the sign on screen as soon as the lock screen appears.

Possible workaround

Since (in my case at least) this seems to be related to leaving apps open during sleep, a workaround that might help is to make sure all your app windows are closed before sleeping the PC. I have tried this a few times after particularly slow startup episodes, and it seems to make the next startup happen at normal speed, but I haven't tried it enough times to be 100% convinced that it's a reliable workaround.

The nice thing about this workaround for others is that it's easy and doesn't disturb any settings, so if it helps you're good, and if it doesn't you're no worse off.

Possible cause

The apparent relationship to Task View makes me suspect that the Windows Timeline feature is responsible. When you launch your user account, Task View builds a history of the documents and web pages you've accessed in the last 30 days. Obviously, it must be scanning a journal on disk to build this. It might be that the scan always continues for the full life history of any tasks that exist when the scan started. For apps you leave running across PC sleeps, that could make it scan back much, much farther and could be causing this problem. I'm just speculating, but it would explain why the workaround succeeds, if in fact it does.

I read recently that Timeline will no longer be available in Windows 11, so this problem might go away when you update. If, like me, you don't have a PC that's capable of running Win11, you might be stuck with using this workaround until Win10 support ends in about 4–5 years.

So before overwriting Win10 on my laptop and replacing it with Kubuntu Linux I decided to do a fresh install of Win10 21H1 to see if that improved performance. It does boot faster but this morning Win 10 starting grinding away at the HDD for over 10 minutes on a fresh install of Win 10 less than 24 hours old. There are no other program installed on it and I removed all the bloatware I could. I had rebooted it several times yesterday and no high disk usage so it's obvious that M$ has chosen Sunday as the day they will take over our systems. 21H1 also required me to log into a M$ account in order to install. Not that big of a deal since I have accounts but what if I want to sell that system? So now M$ is trying to keep us from even selling our old systems since they will be tied to our personal accounts? With Win 11 not being able to run on most older systems and Win 10 only being supported until 2025 it's obvious the only solution is to drop the M$ malware called Windows and use Linux.

![](https://learn-attachment.microsoft.com/api/attachments/28bdb5f6-654c-4bfe-be44-20b42e7d55a2?platform=QnA