Ray

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » WMI  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ray commented  · 

    I suspect something went wrong with version 4.12.17007.18011-0 because on other servers with lower version the cmdlet ran without issues

    An error occurred while saving the comment
    Ray commented  · 

    More information:

    On those servers where this error happens, event logs shows below errors:

    2019-06-18T14:06:17.9670420Z 6/18/2019 2:06:16 PM 5857 Information ProtectionManagement provider started with result code 0x8007007E.
    2019-06-18T14:06:17.9671610Z HostProcess = wmiprvse.exe; ProcessID = 5452; ProviderPath =
    2019-06-18T14:06:17.9672564Z "%ProgramData%\Microsoft\Windows
    2019-06-18T14:06:17.9673718Z Defender\platform\4.12.17007.18011-0\ProtectionManagement.dll"
    2019-06-18T14:06:17.9694641Z 6/18/2019 2:06:16 PM 5858 Error Id = {9D48DD23-8EB5-4035-A4E1-2B4AADEB8E7C}; ClientMachine =
    2019-06-18T14:06:17.9694876Z ; User = ; ClientProcessId = ;
    2019-06-18T14:06:17.9695685Z Component = Unknown; Operation = Start IWbemServices::ExecMethod -
    2019-06-18T14:06:17.9696004Z root\Microsoft\Windows\Defender : MSFT_MpPreference::Add; ResultCode =
    2019-06-18T14:06:17.9697533Z 0x80041013; PossibleCause = Unknown

    Ray shared this idea  · 

Feedback and Knowledge Base