Shutdown Event Tracker on Windows Server 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1402171%22%20slang%3D%22en-US%22%3EShutdown%20Event%20Tracker%20on%20Windows%20Server%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1402171%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20build%20some%20new%20servers%20and%20all%20have%20the%20same%20behavior%20after%20installing%20Windows%20updates.%20After%20the%20user%20logon%20Shutdown%20Event%20tracker%20keeps%20appearing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20quick%20search%20pointed%20in%20the%20direction%20of%20a%20Windows%20update%20(KB4490481%20-%20CU%202019-03).%20See%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fc543eed6-f647-4563-85ce-8e72d1b36a85%2Fshutdown-event-tracker-keeps-appearing-after-installing-kb4490481-and-an-unexpected-shutdown%3Fforum%3Dws2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Elink%3C%2FA%3E.%3C%2FP%3E%3CP%3EWe%20can%20change%20this%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.lweb.co.uk%2Fshutdown-event-tracker-keeps-appearing-on-server-2019%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eregkey%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FA%3Ebut%20that's%20a%20workaround%2C%20not%20a%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20to%20know%20if%20I%20forgot%20something%20or%20maybe%20someone%20has%20solved%20the%20problem.%20So%20please%20share%20your%20thoughts%20about%20this.%3C%2FP%3E%3CP%3EWhat%20I%20did%20to%20reproduce%20the%20problem.%20Started%20with%20a%20fresh%20machine%2C%20WS%202019%20Standard%20version%20201911.%3CBR%20%2F%3EAfter%20installing%3A%3C%2FP%3E%3CUL%3E%3CLI%3ECU%202019-09%20-%20KB4512578%20%26gt%3B%20already%20present%20after%20the%20installation%20%26gt%3B%20logon%20goes%20fine.%3C%2FLI%3E%3CLI%3EInstalled%20CU%202020-03%20-%20KB4538461%20%26gt%3B%20reboot%20%26gt%3B%20no%20problem%3C%2FLI%3E%3CLI%3Erevert%20to%20the%20fresh%20installation%3C%2FLI%3E%3CLI%3ESSU%202019-11%20-%20KB4523204%20%26gt%3B%20reboot%20%26gt%3B%20no%20problem%3C%2FLI%3E%3CLI%3E%3CSPAN%3EInstalled%202020-03%20-%20KB4538461%20%26gt%3B%20reboot%26gt%3B%20no%20problem%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3ELog%20off%20%26gt%3B%20no%20problem%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EReboot%2C%20with%20a%20reason%20%26gt%3B%20Other%20Unplanned%20%26gt%3B%20no%20problem%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3ELet%20the%20machine%20crash%20with%20Not%20My%20Fault%26gt%3B%20after%20booting%20%26gt%3B%20Shutdown%20Event%20Tracker%20is%20appearing%2C%20which%20makes%20sense.%26nbsp%3B%3C%2FLI%3E%3CLI%3ELog%20off%20%26gt%3B%20shutdown%20event%20tracker%20is%20back.%3C%2FLI%3E%3CLI%3E%3CSPAN%3EReboot%20(with%20a%20reason%3A%20Other%20planned)%20%26gt%3B%20and%20SET%20is%20back%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EUninstall%20CU%202020-03%20-KB4538461%20%26gt%3B%20reboot%20%26gt%3B%20still%20there%3C%2FLI%3E%3CLI%3E%3CSPAN%3EUninstall%20SSU%202019-11%20-%20KB4523204%20%26gt%3B%20not%20possible%20is%20required%20voor%20de%20computer%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EInstall%20CU%202020-05%20-%20KB4551853%20%26gt%3B%20reboot%20%26gt%3B%20first%20time%20logon%20okay%2C%20next%20day%20it's%20back.%26nbsp%3B%3C%2FLI%3E%3CLI%3EInstalled%20SSU%202020-04%20%26gt%3B%20SET%20still%20present.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3BSo%E2%80%A6.%3F%3C%2FP%3E%3CP%3EIt%20seems%20to%20be%20a%20combination%20of%20the%20SSU%20KB4523204%20and%20CU%20KB4538461.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20still%20testing%20some%20scenario's%20but%20I%20want%20to%20see%20anyone%20has%20a%20solution%20or%20tips%20to%20test.%3C%2FP%3E%3CP%20class%3D%22%22%3EThanks%20for%20the%20feedback%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1402171%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1462902%22%20slang%3D%22en-US%22%3ERe%3A%20Shutdown%20Event%20Tracker%20on%20Windows%20Server%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1462902%22%20slang%3D%22en-US%22%3E%3CP%3Ea%20quick%20update%20on%20this.%3C%2FP%3E%3CP%3EI've%20downloaded%20the%20latest%20iso%20(updated%20on%2030%2F04%2F2020)%20and%20after%20some%20testing%20this%20seems%20okay.%20I%20didn't%20receive%20the%20pop%20up%20anymoren.%3C%2FP%3E%3CP%3EOn%20other%20servers%20this%20popup%20didn't%20show%20up%20any%20more%20after%20the%20latest%20updates%20from%20June%20were%20installed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi all,

 

We've build some new servers and all have the same behavior after installing Windows updates. After the user logon Shutdown Event tracker keeps appearing.

 

A quick search pointed in the direction of a Windows update (KB4490481 - CU 2019-03). See link.

We can change this regkey but that's a workaround, not a solution.

 

I want to know if I forgot something or maybe someone has solved the problem. So please share your thoughts about this.

What I did to reproduce the problem. Started with a fresh machine, WS 2019 Standard version 201911.
After installing:

  • CU 2019-09 - KB4512578 > already present after the installation > logon goes fine.
  • Installed CU 2020-03 - KB4538461 > reboot > no problem
  • revert to the fresh installation
  • SSU 2019-11 - KB4523204 > reboot > no problem
  • Installed 2020-03 - KB4538461 > reboot> no problem
  • Log off > no problem
  • Reboot, with a reason > Other Unplanned > no problem
  • Let the machine crash with Not My Fault> after booting > Shutdown Event Tracker is appearing, which makes sense. 
  • Log off > shutdown event tracker is back.
  • Reboot (with a reason: Other planned) > and SET is back
  • Uninstall CU 2020-03 -KB4538461 > reboot > still there
  • Uninstall SSU 2019-11 - KB4523204 > not possible is required voor de computer
  • Install CU 2020-05 - KB4551853 > reboot > first time logon okay, next day it's back. 
  • Installed SSU 2020-04 > SET still present.

 So….?

It seems to be a combination of the SSU KB4523204 and CU KB4538461.

 

I'm still testing some scenario's but I want to see anyone has a solution or tips to test.

Thanks for the feedback

1 Reply

a quick update on this.

I've downloaded the latest iso (updated on 30/04/2020) and after some testing this seems okay. I didn't receive the pop up anymoren.

On other servers this popup didn't show up any more after the latest updates from June were installed.