WaasMedic Agent Exe stopping me from working

In response to wmcole. I had been on 2004 since last October when it auto updated itself, 20H2 showing as an option. Did not update, left it there as an option. June 5th first boot of day, noticed lot of disc activity, Task Manager showed Windows Module installer running. Finally request to restart, found I had been updated to 21H1 thereby leap-frogging 20H2. Time taken to complete was not that long, did not notice any differences in appearance, running etc. I was holding on updating to 20H2 as according to MS there were fundamental changes to the workings, main concern was that the traditional Control Panel was in effect, disappearing. Still available as it has been for years.

In response to MarcHoppe. Wednesday, 3 minutes after AM boot, notification that I needed to restart to install update. This was KB5004945, the MS FIX referred to. Installed as no choice. Went into control panel to check if Restore Point had been created, RECOVERY icon had moved on a place, noticed there was now an item for FLASH Player. Half hour later, BLUE SCREENED when in an EXCEL worksheet, auto restarted, up & running again. Event Viewer log entry under error listed 'BUGCHECK'. Couple of hours later another BLUE Screen again, I was just about to open File Explorer from Task Bar, auto rebooted again & running, EV showed another BUGCHECK error. Ran FP normal uninstaller, ran but FP still in Control Panel. Ran MS Catalog FP uninstall, came up with as already installed so FP still in control panel. Removed KB5004945 thru' uninstall updates, FP still there although no more blue screening after, well at least for the next 3 hours. Spoke to my computer guru, suggested doing a System Restore, done that, FP now gone from Control Panel. I then halted further updates till after the next patch Tuesday. Touch wood, no more BLUE SCREENS since. MS seem to completely lost the plot now, looks as though released this update in a panic, and once again, did not test before release. What we really need is a way of halting updates on a permanent basis

MichaelIrons said:

>>What we really need is a way of halting updates on a permanent basis<<

... and / or restoration of the old option to announce update and let us choose if and when we want to install it or not on a case by case basis.

'Another Fine mess you have got me into Stanley'. MS release of KB5004945, caused me problems, apparently a lot of other users as well. In their haste to issue an update to solve this PrintNightmare security vulnerability, MS have caused other problems similar to mine. Apparently a fix due to fix the fix, a true Laurel & Hardy effort here by MS. Few postings ago I thought the were attempting suicide, looks as though they now have the noose tight around their neck, another fine example of MS's total incompetence, when will this all end?

Today WaasMedic ran for over 40 minutes keeping the system next to useless. I did manage to get Resource Monitor open in time to catch it not only reading but also WRITING to disk. About 1/4 of its total MB/s IO were writes! Yes the machine was booted yesterday, yes it ran yesterday, and no there is no task in Task Scheduler to run today. So it appears MS got tired or resetting the task for the Sunday runs that we attempted to remove from the task list, and have just integrated WaasMedic running into the base OS boot procedure. I.e., MS knows what is best for you even if it means reducing your productivity to nil.

As for "MS Suicide", I believe the problem is this: MS does not like to hire experienced people. Rather they like to hire straight out of college to they can teach the "MS culture" to their 'engineers'. That basically involves keeping them in the dark about all but a specific aspect of the OS so that no one person knows enough to go out on their own and build a competing OS. I.e. they are keeping people from doing what Bill Gates did to the originators of CPM. He effectively stole their product, simply reversed command arguments and called it "MS DOS". The upshot of the "MS culture" is a patch work of modules assembled into an OS without an overarching, disciplined and rigorous "Integration Engineering" function. That is a person and department responsible for developing requirements, overseeing design and development to a holistic architecture the requirements define, and rigorously testing to the requirements before release. Without that you get the ad-hoc, "organic" sprawl and disorganize assemblage of functions that is Windows 10.

Further, since the "development team" are all social media babies, they are no longer OS engineers but "connectivity advocates" who are intent on hanging every bit of "connectedness" for a 24-7 "digital life", which means chaining you ever tighter to MS cloud and marketing services by weaving applications into the OS rather than providing the the most compact, secure, flexible yet easily configurable software to run your computer hardware in service of the applications of YOUR choosing.