Known Issue – Windows Updates occasionally incorrectly show as not succeeded in Intune

Published Jul 27 2020 06:02 PM 11K Views

Updated 6/3/21: To minimize confusion about the update state, (noted in MC254874) we will be removing the End user update status report found in Devices > Windows > Windows 10 Feature updates > Select a Profile. You will be able to find the same information in the Windows Feature Update report under Reports > Windows Updates (preview) > Reports tab > Generate Windows Feature Update report, “Update State” and “Update SubStates” columns.

 

We will also be removing the Update Status column in the June (2106) Intune service release. (Devices > Windows > Windows 10 update rings > Select a Profile).

 

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!

 

Blog updates:

6/3/21: To minimize confusion about the update state, we will be removing the Update Status column in the June (2106) Intune service release.

6/30/21: Additional note that in the in the May (2105) service release, we have also removed the Alert details column in the Windows 10 Feature Updates report. For accurate information on Alert details, you should use the operational report under Devices > Monitor > Feature update failures (Preview) > Select a Profile and then select an Alert Message. This will provide a pop-up with the description and recommendation to resolve.

12 Comments
%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-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%3CLINGO-SUB%20id%3D%22lingo-sub-2125300%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-2125300%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Intune%20Support%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20currently%20have%20many%20devices%20showing%20as%20failed%20under%20the%20'end%20user%20update%20status'%20(my%20device%20included)%2C%20however%20most%20of%20these%20devices%20are%20running%20the%20most%20recent%20update%20available%20to%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20an%20ETA%20on%20a%20fix%3F%20Or%20is%20there%20a%20work%20around%20that%20can%20be%20deployed%20in%20bulk%20remotely%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2165370%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-2165370%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F806104%22%20target%3D%22_blank%22%3E%40KernelCaleb%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20issue%20in%20my%20tenant%2C%20Please%20check%20in%20your%20Windows%20Update%20ring%20driver%20update%20are%20enabled%20or%20disable.%20What%20we%20observed%20is%20monthly%20windows%20patches%20getting%20installed%20perfectly%20but%20due%20to%20system%20drivers%20in%20Intune%20portal%20windows%20update%20status%20is%20shows%20as%20Failed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20disabling%20driver%20updates%20it's%20showing%20correct%20status.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20and%20Regards%2C%3C%2FP%3E%3CP%3EChetan%20Jadhav%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2199678%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-2199678%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20the%20exact%20same%20issue..out%20of%20approx.%20300%20devices%20270%20are%20shown%20as%20failed%20although%20they%20have%20the%20latest%20patches%20applied...Is%20there%20anything%20we%20can%20do%20about%20that%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2235554%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-2235554%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20issue.%20While%20the%20devices%20eventually%20show%20as%20Up%20to%20Date%2C%20it%20takes%20weeks%20for%20that%20to%20occur.%20This%20makes%20identifying%20actual%20issues%20during%20a%20rollout%20frustrating%20and%20time%20consuming.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2246411%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-2246411%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20thing%20for%20us.%20Ensuring%20your%20devices%20up%20to%20date%20is%20one%20of%20the%20key%20things%20you%20can%20do%20to%20reduce%20cyber%20risk.%20Having%20this%20issue%20makes%20our%20job%20to%20secure%20our%20organisations%20much%20harder%20than%20it%20needs%20to%20be.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2278775%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-2278775%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20the%20same%20issue%20-%20is%20there%20an%20ETA%20for%20a%20fix%20(or%20a%20workaround%20such%20as%20a%20PowerShell%20script%20to%20run%20on%20the%20clients%20to%20clear%2Fre-sync%20to%20fix%20the%20issue%3F)%3C%2FP%3E%3CP%3EI%20find%20it%20very%20frustrating%20that%20your%20support%20teams%20response%20is%20its%20a%20known%20issue%20but%20we%20can't%20do%20anything%20to%20fix%20it!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%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%3E%3CEM%3E%3CSTRONG%3EUpdated%206%2F3%2F21%3A%26nbsp%3B%3C%2FSTRONG%3ETo%20minimize%20confusion%20about%20the%20update%20state%2C%20(noted%20in%20%3CSTRONG%3EMC254874%3C%2FSTRONG%3E)%20we%20w%3C%2FEM%3E%3CEM%20style%3D%22font-family%3A%20inherit%3B%22%3Eill%20be%20removing%20the%20%3CSTRONG%3EEnd%20user%20update%20status%20report%3C%2FSTRONG%3E%26nbsp%3Bfound%20in%20Devices%20%26gt%3B%20Windows%20%26gt%3B%20Windows%2010%20Feature%20updates%20%26gt%3B%20Select%20a%20Profile.%26nbsp%3BYou%20will%20be%20able%20to%20find%20the%20same%20information%20in%20the%26nbsp%3B%3CSTRONG%3EWindows%20Feature%20Update%3C%2FSTRONG%3E%26nbsp%3Breport%20under%26nbsp%3BReports%20%26gt%3B%20Windows%20Updates%20(preview)%20%26gt%3B%20Reports%20tab%20%26gt%3B%20Generate%20Windows%20Feature%20Update%20report%2C%20%E2%80%9CUpdate%20State%E2%80%9D%20and%20%E2%80%9CUpdate%20SubStates%E2%80%9D%20columns.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EWe%26nbsp%3Bwill%20also%20be%20removing%20the%20%3CSTRONG%3EUpdate%20Status%3C%2FSTRONG%3E%20column%20in%20the%20June%20(2106)%20Intune%20service%20release.%20(Devices%20%26gt%3B%20Windows%20%26gt%3B%20Windows%2010%20update%20rings%20%26gt%3B%20Select%20a%20Profile).%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%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%3EHere%E2%80%99s%26nbsp%3Bthe%20steps%20we%20took%20to%20replicate%20this%20experience%3A%26nbsp%3B%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%3Dv2%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%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%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%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBlog%20updates%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E6%2F3%2F21%3A%20To%20minimize%20confusion%20about%20the%20update%20state%2C%20we%20will%20be%20removing%20the%20Update%20Status%20column%20in%20the%20June%20(2106)%20Intune%20service%20release.%3C%2FP%3E%0A%3CP%3E6%2F30%2F21%3A%20Additional%20note%20that%20in%20the%20in%20the%20May%20(2105)%20service%20release%2C%20we%20have%20also%20removed%20the%26nbsp%3B%3CSTRONG%3EAlert%20details%3C%2FSTRONG%3E%26nbsp%3Bcolumn%20in%20the%20Windows%2010%20Feature%20Updates%20report.%20For%20accurate%20information%20on%20Alert%20details%2C%20you%20should%20use%20the%20operational%20report%20under%26nbsp%3B%3CEM%3EDevices%20%26gt%3B%20Monitor%20%26gt%3B%20Feature%20update%20failures%20(Preview)%20%26gt%3B%20Select%20a%20Profile%3C%2FEM%3E%26nbsp%3Band%20then%20select%20an%20Alert%20Message.%20This%20will%20provide%20a%20pop-up%20with%20the%20description%20and%20recommendation%20to%20resolve.%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
Version history
Last update:
‎Jun 30 2021 01:48 PM
Updated by: