%3CLINGO-SUB%20id%3D%22lingo-sub-1558827%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1558827%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20seen%20computers%20report%20failed%20and%20then%20up-to-date%20for%20some%20time%20be%20great%20to%20see%20a%20fix%20for%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1603093%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1603093%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20you%20have%20an%20ETA%20for%20the%20issue%20to%20be%20resolved%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1655521%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1655521%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F344828%22%20target%3D%22_blank%22%3E%40AadilTeeluckdharry%3C%2FA%3E%2C%20thanks%20for%20the%20question!%20Though%20we%20don't%20have%20an%20ETA%20to%20share%20at%20this%20time%2C%20we'll%20post%20an%20update%20to%20this%20blog%20as%20soon%20as%20we%20have%20more%20info%20to%20share.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1876277%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1876277%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Is%20there%20any%20further%20update%3F%20This%20looks%20to%20be%20working%20for%20us%20now%2C%20but%20it%20would%20be%20nice%20to%20confirm%20the%20bug%20has%20been%20fixed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1944752%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1944752%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20this%3F%20I%20have%20lots%20of%20devices%20which%20show%20failed%20but%20have%20no%20errors%20and%20have%20applied%20all%20of%20the%20updates.%20The%20gwmi%20command%20returns%20no%20errors%20either.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1549132%22%20slang%3D%22en-US%22%3EKnown%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1549132%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20were%20recently%20alerted%20to%20an%20issue%20whereby%20a%20device%20in%20the%20Microsoft%20Endpoint%20Manager%20admin%20console%20was%20showing%20%E2%80%9Cfailed%E2%80%9D%20for%20their%20Windows%20Update%20status.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUpon%20investigation%2C%20we%20discovered%20that%20the%20device%20was%20not%20missing%20any%20updates%20%E2%80%93%20everything%20had%20successfully%20applied.%20However%2C%20we%20did%20find%20two%20error%20codes%20on%20the%20device%2C%20which%20then%20were%20calculated%20by%20Intune%20as%20%E2%80%9Cfailed%E2%80%9D.%26nbsp%3B%20After%20the%20policy%20was%20re-evaluated%2C%20then%20the%20device%20returned%20to%20healthy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%E2%80%99s%3C%2FSPAN%3E%26nbsp%3Bthe%20steps%20we%20took%20to%20replicate%20this%20experience%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CSPAN%3ECreate%20a%20basic%20Windows%20Update%20ring%20policy%20and%20apply%20to%20Windows%2010%20devices.%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3ETrigger%20a%20check%20for%20updates%20and%20refresh%20the%20device.%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EDownload%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fsysinternals%2Fdownloads%2Fpsexec%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPsexec.exe%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3ERun%20%3CSTRONG%3Epsexec%20%2Fsid%20PowerShell.exe%3C%2FSTRONG%3E%26nbsp%3Bfrom%20an%20elevated%20command%20prompt%20or%20elevated%20PowerShell%20window.%26nbsp%3B%20A%20new%20PowerShell%20instance%20will%20open%2C%20running%20in%20system%20context.%3C%2FLI%3E%0A%3CLI%3ERun%20the%20following%20command%20in%20the%20system-context%20PowerShell%20window%20you%20created%20in%20step%204%3A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%20class%3D%22lia-indent-padding-left-60px%22%3Egwmi%20MDM_Update_FailedUpdates01_01%20-Namespace%20ROOT%5CCIMV2%5Cmdm%5Cdmmap%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20nothing%20is%20returned%2C%20the%20device%20does%20not%20currently%20have%20a%20failed%20update.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22WU_1.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F208336iB4560BF183D5018B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22WU_1.png%22%20alt%3D%22WU_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIf%20Windows%20Update%20returns%20one%20of%20the%20two%20error%20codes%20as%20you%20can%20see%20on%20the%20device%2C%20then%26nbsp%3Byou%E2%80%99ll%26nbsp%3Bsee%20%E2%80%9Cfailed%E2%80%9D%20in%20the%20console%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHResult%26nbsp%3B%20%26nbsp%3B%20%3A%20-2145082874%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInstanceID%20%3A%20ec67ed82-8cf6-4fa9-86bf-efdb4e7b5d00%3C%2FP%3E%0A%3CP%3EParentID%26nbsp%3B%20%26nbsp%3B%3A%20.%2FVendor%2FMSFT%2FUpdate%2FFailedUpdates%3C%2FP%3E%0A%3CP%3EState%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHResult%26nbsp%3B%20%26nbsp%3B%20%3A%20-2145082858%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInstanceID%20%3A%2033e3f18f-c868-4d00-8266-01c100acf444%3C%2FP%3E%0A%3CP%3EParentID%26nbsp%3B%20%26nbsp%3B%3A%20.%2FVendor%2FMSFT%2FUpdate%2FFailedUpdates%3C%2FP%3E%0A%3CP%3EState%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20two%20error%20codes%20are%20specific%20to%20Windows%20Update%20being%20too%20busy.%20It%E2%80%99s%20rare%2C%20but%20there%20are%20times%20that%20the%20service%20will%20return%20these%20codes.%26nbsp%3BIf%20you%26nbsp%3Brun%20into%20this%2C%20both%20the%20Intune%20policy%20refresh%20and%20then%20likely%20the%20Windows%20Update%20policy%20refresh%20will%20need%20to%20trigger%20to%20ensure%20policy%20is%20evaluated%20and%20updated.%20For%20more%20info%20on%20Intune%20policy%20refresh%20timelines%2C%20see%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fconfiguration%2Fdevice-profile-troubleshoot%23how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHow%20long%20does%20it%20take%20for%20devices%20to%20get%20a%20policy%2C%20profile%2C%20or%20app%20after%20they%20are%20assigned%3F%3C%2FA%3E%26nbsp%3Bto%20learn%20more.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollow%20Intune%20Support%20as%20a%20Feature%20on%20Twitter%20as%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FIntuneSuppTeam%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%40IntuneSuppTeam%3C%2FA%3E%20for%20helpful%20articles%2C%20release%20info%2C%20and%20more!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1549132%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20support%20team%20had%20a%20case%20on%20this%20topic%20and%20after%20working%20with%20our%20engineering%20team%2C%20thought%20it%20would%20be%20helpful%20to%20share%20more%20details!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1549132%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECustomer%20Success%20blog%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%20Known%20Issue%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2087798%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Windows%20Updates%20occasionally%20incorrectly%20show%20as%20not%20succeeded%20in%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2087798%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Team%2C%3C%2FP%3E%3CP%3ECould%20you%20please%20confirm%20whether%20this%20issue%20has%20been%20resolved%20or%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E

We were recently alerted to an issue whereby a device in the Microsoft Endpoint Manager admin console was showing “failed” for their Windows Update status.

 

Upon investigation, we discovered that the device was not missing any updates – everything had successfully applied. However, we did find two error codes on the device, which then were calculated by Intune as “failed”.  After the policy was re-evaluated, then the device returned to healthy.

 

Here’s the steps we took to replicate this experience: 

  1. Create a basic Windows Update ring policy and apply to Windows 10 devices. 
  2. Trigger a check for updates and refresh the device. 
  3. Download Psexec.exe
  4. Run psexec /sid PowerShell.exe from an elevated command prompt or elevated PowerShell window.  A new PowerShell instance will open, running in system context.
  5. Run the following command in the system-context PowerShell window you created in step 4:

gwmi MDM_Update_FailedUpdates01_01 -Namespace ROOT\CIMV2\mdm\dmmap

 

If nothing is returned, the device does not currently have a failed update.  

WU_1.png

 

If Windows Update returns one of the two error codes as you can see on the device, then you’ll see “failed” in the console: 

 

HResult    : -2145082874   

InstanceID : ec67ed82-8cf6-4fa9-86bf-efdb4e7b5d00

ParentID   : ./Vendor/MSFT/Update/FailedUpdates

State      : 

 

HResult    : -2145082858   

InstanceID : 33e3f18f-c868-4d00-8266-01c100acf444

ParentID   : ./Vendor/MSFT/Update/FailedUpdates

State      : 

 

These two error codes are specific to Windows Update being too busy. It’s rare, but there are times that the service will return these codes. If you run into this, both the Intune policy refresh and then likely the Windows Update policy refresh will need to trigger to ensure policy is evaluated and updated. For more info on Intune policy refresh timelines, see: How long does it take for devices to get a policy, profile, or app after they are assigned? to learn more.

 

Follow Intune Support as a Feature on Twitter as @IntuneSuppTeam for helpful articles, release info, and more!

6 Comments
Senior Member

I have seen computers report failed and then up-to-date for some time be great to see a fix for this.

New Contributor

Do you have an ETA for the issue to be resolved? 

Hi @AadilTeeluckdharry, thanks for the question! Though we don't have an ETA to share at this time, we'll post an update to this blog as soon as we have more info to share.

Occasional Visitor

Hi, Is there any further update? This looks to be working for us now, but it would be nice to confirm the bug has been fixed.

Occasional Visitor

Any update on this? I have lots of devices which show failed but have no errors and have applied all of the updates. The gwmi command returns no errors either.

New Contributor

Hello Team,

Could you please confirm whether this issue has been resolved or not.