Reimbursement as a consequence for their actions? Ha! That's no longer a thing here in America these days, sadly. You, I, and the gal them down the street will bear the burden of all associated costs as usual. Taxpayers foot all the bills. And Active Duty & Veterans find themselves settling all other outstanding debts in one way or another.

@IntuitCharlene  does this now fall under your jurisdiction? Please see previous posts. Thanks. Also. Might this be a good time to "invent?" a "catch all" @ for getting a response? As people move on, or get annoyed by my pestering. If Almighty Intuit would grace this mere Community with a constant @ to get a Response that might cut down on the noise. Not a specific employee/admin for example @ ADMIN or @ MOD or @ ASSISTANCE or @ QUERY etc. to get on yinz radar. 

@IntuitBettyJo  @IntuitGabi   Greetings. Any of you able to shine any light on the phenomena of spontaneous updating I would greatly appreciate you sharing illumination. Are my Users forcing Updates? I have them restricted by Trustee Rights. Is there some Loophole allowing updates to override Scheduler's schedule?

@IntuitGabi  are their "tiers" of Updates?  Some appear to respect authority of Scheduler and others, well to put it nicely -- do whatever they feel like spontaneously upon release from Mothership.   

It's back @IntuitGabi  Description Faulting application name: w21tax.exe, version: 42.0.0.2494, time stamp: 0x6307845d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x039c3412 Faulting process id: 0xf1c Faulting application start time: 0x01d8bca2c7f25aa9 Faulting application path: C:\Lacerte\21tax\w21tax.exe Faulting module path: unknown Report Id: 5172d6e5-7bf3-4bf6-b7c4-4c4004152f36 Faulting package full name: Faulting package-relative application ID:  

[cough] @IntuitGabi  I presume all Intuit Lacerte devs work in windowless silos chained to concrete slabs. If not please suggest. NOTE: Similar malfunction - application vanishing - in flavors of QuickBooks as well; say my boots on the ground busy shoveling client mess. How much does QB share with core Lacerte?! 😠 Description Faulting application name: w21tax.exe, version: 42.0.0.2434, time stamp: 0x62f2454b Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624cf48c Exception code: 0xc0000409 Fault offset: 0x0065d4c8 Faulting process id: 0x9f0 Faulting application start time: 0x01d8adaa97c849cb Faulting application path: C:\Lacerte\21tax\w21tax.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: 5e578dbd-1f15-4c9f-80d3-b28f7ecb6f15 Faulting package full name: Faulting package-relative application ID:

@IntuitGabi related or not, I can neither confirm nor deny -- this User also had pre-existing Windows critical events (Start menu, Your phone, Microsoft Store - a real hodgepodge of horrors,) in addition to this specific Lacerte menace. An afternoon with Windows 10's Reset this PC, and reinstallation of several years of Intuit Lacerte tax applications, I am hopeful this PC is now "clean." (Knock on wood, no jinx!) Next up are the various flavors of Intuit QuickBooks to reinstall - yippee!

Thanks for digging-in. I performed Web Setup yesterday. Are there underlying issues with platform/components that Lacerte piggybacks on? Something internal to Windows/Microsoft? .Net? ...and similar?