svchost.exe_DiagTrack stopped working

Page 3 of 3 FirstFirst 123

  1. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #21

    DaveH1 said:
    Yes, I was referring to the 1903 feature update.
    I guess @thomaseg1 must have cleared it, as you say.
    Shows now relatively minor the 1909 update is if it didn't automatically clear the record of the previous 1903 update!
    A "proper" feature update would have cleared the whole update history.
    I usually only keep history for a month or so to see if the updates are working
    right. before Patch Tuesday I clear it otherwise it would be very bulky.
    there has been like 100 updates and who knows how many security
    definitions since Win 10 began.
      My Computers


  2. Posts : 347
    Windows 10 Home Version 21H1 OS Build 19044.1645
    Thread Starter
       #22

    thomaseg1 said:
    I usually only keep history for a month or so to see if the updates are working
    right. before Patch Tuesday I clear it otherwise it would be very bulky.
    there has been like 100 updates and who knows how many security
    definitions since Win 10 began.
    That's probably a good idea. It does take forever to open after a while.
      My Computer


  3. Posts : 134
    Windows 10 Pro x64 20H2
       #23

    True!

    @thomaseg1
    To get back on topic, are you seeing the
    "svchost.exe_DiagTrack" service crashing all the time too?

      My Computer


  4. Posts : 2,284
    Windows 10
       #24

    Why would (2) bother you, it installed and that is it. Mine is the same.

    svchost.exe_DiagTrack has been going on since mid October with one of the Defender updates If I remember correctly.

    Does not affect you using your PC.
    That one stopped about 9 Nov with mine.
      My Computer


  5. Posts : 134
    Windows 10 Pro x64 20H2
       #25

    It doesn't bother me, don't worry I'm not losing sleep over it, I'm just puzzled why it's there, as it would normally only be appended to an entry that had installed (or failed) more than once.
    Likewise with the service crashes, it doesn't affect the use of the machine, but it shouldn't be happening, in fact Microsoft are presumably losing telemetry because of it!
    Interesting that the problem seems to be gradually disappearing, but at different times for different people.
    Maybe if it's a server problem, as it appears to be, the timing of fix is dependant on the region you're in.
      My Computer


  6. Posts : 134
    Windows 10 Pro x64 20H2
       #26

    Just an update that the problem appears to have been fixed by clearing the diagnostic data.
    I went into Settings>Privacy>Diagnostics & Feedback, and on a hunch used the "Delete Diagnostic Data" function.
    Since then, I have seen no more DiagTrack service crashes in the logs.
    I can only assume that there was some sort of corruption in the stored data which was causing the service to crash.
    I hope the problem doesn't now come back again!
    Cheers, Dave.
      My Computer


  7. Posts : 347
    Windows 10 Home Version 21H1 OS Build 19044.1645
    Thread Starter
       #27

    DaveH1 said:
    Just an update that the problem appears to have been fixed by clearing the diagnostic data.
    I went into Settings>Privacy>Diagnostics & Feedback, and on a hunch used the "Delete Diagnostic Data" function.
    Since then, I have seen no more DiagTrack service crashes in the logs.
    I can only assume that there was some sort of corruption in the stored data which was causing the service to crash.
    I hope the problem doesn't now come back again!
    Cheers, Dave.
    Glad you solved it - I waited a bit longer and it was solved without me doing anything. I looked back in Reliability Monitor, and lo and behold, there was another update to the antimalware platform about 24 hours earlier. If memory serves, the error first appeared about 24 hours after the previous update.
    It only took about six weeks, but it now seems to be back to normal.
      My Computer


  8. Posts : 134
    Windows 10 Pro x64 20H2
       #28

    Strange, mine showed no sign of fixing itself.
    Anyway, let's hope the problem doesn't come back!
    It's good to see a (relatively) clean log again.
    Cheers, Dave.
      My Computer


  9. Posts : 347
    Windows 10 Home Version 21H1 OS Build 19044.1645
    Thread Starter
       #29

    @DaveH1 The antimalware platform update is KB4052623. It was installed for me the same day you deleted the diagnostic data, so the same result may have happenned if you had waited a liittle longer. Did you have that KB installed around 3rd Dec?
      My Computer


  10. Posts : 134
    Windows 10 Pro x64 20H2
       #30

    I've just checked, and that KB4052623 update was installed for me this evening at around 2000, so it was installed a few days after I cleared the data.
    I guess we'll now never know whether that would have actually fixed the problem if I hadn't done that!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:27.
Find Us




Windows 10 Forums