See Alkerion's post of 04-08-2021 06:05 AM earllier in this thread. All you can do is use the Microsloth tool s/he pointed to to hide the update. Whether this stops the daily installs or simply hides them from users I can't say. But it does not seem to address the daily run of WaasMedicAgent.exe which for many users causes their computers to be unusable for a long time after power up due to the disk IO of WaasMedic.
This experience of the constantly installing driver also seems to afflict users of other printers as well (mostly HP). In Xerox case, I believe it is a collaboration between Microsloth and Xerox to force "Type 4" (Microsloth "App Store app compatible") drivers down users' throats even though these drivers UIs are horribly lacking in functional user control compared to "Type 3". My limited experience with Type 4 drivers installed was that it stopped the attempted update. But I couldn't live with the lack of print preference functionality (choose tray, different paper size / type - including custom sizes I had created - etc.) So I went back to typ 3 drivers, downloaded and ran the wushowhide.diagcab utility to hide the Xerox Extension 7.208.0 update so I don't get either the daily install failed or install succeeded message / error.
I believe that since neither Xerox nor Microsloth will respond to this issue (and there are several threads with more than 1,000 postings on this issue in a Microsloth user forum) it is an intentional push to get you to use drivers suitable for mobile device access to printers at the expense of the flexibility and functionality of desktop application printing. The younger generation for whom cell phones are simply another body part that is in constant demand want all us old farts who still use desktop applications to just go away and die. Therefore all the new "innovation" has to just do simple basic crap that can easily be done with one finger on a small screen. The rest of us...?
My windows PC has "sucessfully installed" this update every day since March 5th. Seven weeks later, is there any indication that Xerox is taking responsibility for this and fixing the issue with this software? In the meantime, any advice on how to work around this would be welcome.
Hi !
On all my PC the "windows update medic service" is set to Manual, and not starting at boot time, so no issue at all.
Does hiding the update prevent WaasMedicAgent from running at boot time and slowing the machine to between barely tolerable and unusable for up to an hour?
Either way, thanks for the pointer to the windows utility and instructions on how to use it. Hopefully this helps. If it does you should send a bill to both MS and Xerox for doing their work for them.
Hi !
I've the exact same issue with all the PC of my company on a Versalink C7025, really annoying.
I don't know (and care) who's responsible of this error, but Xerox and MS should have already fixed this error.
I've hidden the update with the MS Show or hide updates troubleshooter to get rid of this error message every time.
https://www.f0il.com/fix-windows-10-windows-update-error-0x800f020b/
@Spete87 wrote:Anyupdate on this issue? I just came across this post as well after finding a PC with the same problem. I hid the update as a temporary fix but i'm wondering if it was causing other issues as well.
...and you would think by now that Xerox would address this as it now appears Xerox printers are no longer really compatible with Windows 10 systems. But - hey - a company that refuses to allow you to contact support if you don't have a Xerox invoice # for your printer (like me who bought from a retailer / dealer - Staples) even during its warranty period! What else should we expect other than crickets.
Anyupdate on this issue? I just came across this post as well after finding a PC with the same problem. I hid the update as a temporary fix but i'm wondering if it was causing other issues as well.
It turns out you CAN install both "Type 3" and "Type 4" drivers. Doing so creates two printers (in my case "Phaser 6510 PS" and "Phaser 6510 PS-2" [that I renamed to "Phaser 6510 PS-2 Type 4"]). Then the "Xerox Extension 7.208.0.0" installation succeeds. You then have a largely useless, very limited version of Xerox drivers (Type 4) taking up space on the hard drive, but at least you don't get the failed Windows Update / Xerox Extension everyday and the subsequent penalty of WaasMedicAgent running and SERIOUSLY bogging down you machine after every boot-up.
However, the failure of "Xerox Desktop Experience" to properly install, either during driver installation or separately from the standalone installer, "XrxSetup_DesktopApp_x64.msi" still exists. Not really a problem unless that is where the additional functionality resides to provide the same level of control over the printer in the "Type 4" driver UI as you get from the Type 3 "Printing Preferences".
Hi Xerox User1,
Thank you for using the Support Forum. Please take a look at this forum post. Looks like the issue is with Microsoft's last update. Please review the post and see the things they did to get their products to work. The same should happen for you.