Home
%3CLINGO-SUB%20id%3D%22lingo-sub-681919%22%20slang%3D%22en-US%22%3EResolved%20%3A%20Intune%20legacy%20PC%20agent%20stops%20working%20on%20PCs%20updated%20to%20Windows%2010%2C%20version%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-681919%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EUpdate%2009%2F19%2F19%20-%20This%20fix%20has%20now%20been%20rolled%20out%20and%20your%20end%20users%20should%20no%20longer%20see%20this%20error.%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20posted%20IT181632%20to%20a%20limited%20number%20of%20customers%20through%20the%20Service%20Health%20Dashboard%2FTenant%20Status%20Blade%20and%20are%20following%20up%20below%20with%20a%20workaround.%20If%20your%20end%20user%20says%20they%20see%20the%20following%20error%20message%2C%20you've%20likely%20run%20into%20this%20known%20issue%20(learn%20more%20will%20link%20to%20this%20post%2C%20too).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118176i3F50590E110D193A%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22windows10notice.png%22%20title%3D%22windows10notice.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20context%2C%20the%20Intune%20legacy%20PC%20management%20(agent-based%20through%20the%20Silverlight%20legacy%20management%20console)%20does%20not%20support%20automatic%20Windows%2010%20feature%20updates%2C%20such%20as%20RS4%2C%20RS5%20or%201903.%20However%2C%20you%20can%20manually%20update%20an%20Intune%20PC%20agent%20managed%20Windows%2010%20PC%20client%20to%20Windows%2010%2C%20version%201903.%20After%20the%20update%2C%20the%20enrolled%20client%20loses%20communication%20with%20the%20service.%20On%20the%20service%20side%2C%20you%20will%20see%20that%20the%20last%20contact%20time%20for%20the%20client%20becomes%20stale.%20On%20the%20client%20side%2C%20when%20you%20scan%20for%20an%20update%20using%20Intune%20Center%20you%20will%20see%20this%20error%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20304px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F117687i41C7E0979604A2D9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22error0x8007065b.png%22%20title%3D%22error0x8007065b.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EHere's%20the%20workaround%3A%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EFrom%20the%20client%20side%2C%20start%20an%20elevated%20command%20prompt%20and%20run%20the%20commands%20below%3A%3C%2FFONT%3E%3CUL%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Eregsvr32.exe%20%2Fs%20%22C%3A%5CProgram%20Files%5CMicrosoft%5COnlineManagement%5CClient%5CSvc%5COmcSvc.dll%22%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Eregsvr32.exe%20%2Fs%20%22C%3A%5CProgram%20Files%5CMicrosoft%5COnlineManagement%5CUpdates%5CBin%5Comupdsrv.dll%22%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Eregsvr32.exe%20%2Fs%20%22C%3A%5CProgram%20Files%5CMicrosoft%5COnlineManagement%5CClient%5CUI%5Cauinstallwiz.dll%22%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3ERestart%20Intune%20center%20and%20do%20a%20scan.%20You%20should%20no%20longer%20see%20the%20error%20message.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3ENote%20that%20this%20problem%20and%20the%20workaround%20only%20affect%20Silverlight-based%20PC%20managed%20devices.%20Windows%2010%20devices%20managed%20through%20the%20MDM%20channel%20are%20not%20impacted.%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-681919%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20recently%20posted%20IT181632%20on%20the%20Service%20Health%20Dashboard%2Ftenant%20status%20blade.%20Below%20is%20a%20workaround%20if%20you%20see%20Error%200x8007065b%20when%20scanning%20updates.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-681919%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%2010%20Silverlight%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Update 09/19/19 - This fix has now been rolled out and your end users should no longer see this error. 

 

We posted IT181632 to a limited number of customers through the Service Health Dashboard/Tenant Status Blade and are following up below with a workaround. If your end user says they see the following error message, you've likely run into this known issue (learn more will link to this post, too). 

 

windows10notice.png

 

For context, the Intune legacy PC management (agent-based through the Silverlight legacy management console) does not support automatic Windows 10 feature updates, such as RS4, RS5 or 1903. However, you can manually update an Intune PC agent managed Windows 10 PC client to Windows 10, version 1903. After the update, the enrolled client loses communication with the service. On the service side, you will see that the last contact time for the client becomes stale. On the client side, when you scan for an update using Intune Center you will see this error:

 

error0x8007065b.png

 

Here's the workaround:

  • From the client side, start an elevated command prompt and run the commands below:
    • regsvr32.exe /s "C:\Program Files\Microsoft\OnlineManagement\Client\Svc\OmcSvc.dll"
    • regsvr32.exe /s "C:\Program Files\Microsoft\OnlineManagement\Updates\Bin\omupdsrv.dll"
    • regsvr32.exe /s "C:\Program Files\Microsoft\OnlineManagement\Client\UI\auinstallwiz.dll"
  • Restart Intune center and do a scan. You should no longer see the error message.

 

Note that this problem and the workaround only affect Silverlight-based PC managed devices. Windows 10 devices managed through the MDM channel are not impacted.