Windows 10: Updated to version 1703, errors 360 and 37

Hi,
As the title says event viewer errors 360 and 37 have only appeared since installing ver 1703.

Anyone else getting these errors on 1703?





:)

 

Error 0x80D0000A

Hi miki and excuse me for intromission.

I have found this thread because I had same (or analogue) trouble... and I just got solution (for me)

My system is Win10 x64 Pro, Version 1703.

I tried several methods described above... and also in other sites, but no one works.

At last... I downloaded (via browser), from Microsoft site:

Microsoft Update Catalog

LAST Cumulative Update (look your Win10 version!), for my system is the file:

2017-09 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4038788)


... and I updated my system locally, offline.

After this procedure (and subsequent restart), the regular Windows Update has resumed to work, downloading the others updates.

Below, just a "very little part" of my WindowsUpdate.log, where is highlighted the error 0x80d0000a

...

...

2017/09/14 14:37:18.1135813 2504 5040 DownloadManager [0]09C8.13B0::09/14/2017-14:37:18.113 [agent]DO job {83460959-FE92-4462-8246-75495724ACCE} hit a transient error, updateId = A1528492-AF29-4789-BBED-4E0E91BF099A.102 <NULL>, error =
0x80D0000A

2017/09/14 14:37:18.1140718 2504 5040 DownloadManager [0]09C8.13B0::09/14/2017-14:37:18.114 [agent]Error 0x80d0000a occurred while downloading update A1528492-AF29-4789-BBED-4E0E91BF099A.102; notifying dependent calls.

2017/09/14 14:37:18.1144226 2504 5040 DownloadManager [0]09C8.13B0::09/14/2017-14:37:18.114 [agent]Dynamic download data fetcher for ServiceId 7971F918-A847-4430-9279-4A52D1EFE18D does not exist.

2017/09/14 14:37:18.1148940 2504 4596 DownloadManager [0]09C8.11F4::09/14/2017-14:37:18.114 [agent]DO job {AF2E792F-43EB-41C2-8A7A-DA042BBF9C42} hit a transient error, updateId = B68ED419-7C09-4530-9D71-0BF9EE35F1CD.103 <NULL>, error = 0x80D0000A

2017/09/14 14:37:18.1153613 2504 4596 DownloadManager [0]09C8.11F4::09/14/2017-14:37:18.115 [agent]Error 0x80d0000a occurred while downloading update B68ED419-7C09-4530-9D71-0BF9EE35F1CD.103; notifying dependent calls.

2017/09/14 14:37:18.1157154 2504 4596 DownloadManager [0]09C8.11F4::09/14/2017-14:37:18.115 [agent]Dynamic download data fetcher for ServiceId 7971F918-A847-4430-9279-4A52D1EFE18D does not exist.

2017/09/14 14:37:18.1161722 2504 6344 DownloadManager [0]09C8.18C8::09/14/2017-14:37:18.116 [agent]DO job {52C849E8-498C-4974-91B4-EC71EFA4028A} hit a transient error, updateId = E2AC00F9-5E00-4699-81A1-4D93904288D1.104 <NULL>, error = 0x80D0000A

2017/09/14 14:37:18.1167090 2504 6344 DownloadManager [0]09C8.18C8::09/14/2017-14:37:18.116 [agent]Error 0x80d0000a occurred while downloading update E2AC00F9-5E00-4699-81A1-4D93904288D1.104; notifying dependent calls.

2017/09/14 14:37:18.1173153 2504 6344 DownloadManager [0]09C8.18C8::09/14/2017-14:37:18.117 [agent]Dynamic download data fetcher for ServiceId 7971F918-A847-4430-9279-4A52D1EFE18D does not exist.

2017/09/14 14:37:18.1177741 2504 4296 DownloadManager [0]09C8.10C8::09/14/2017-14:37:18.117 [agent]DO job {A3DF467B-89C0-4E2C-9867-BCD11FAE249E} hit a transient error, updateId = 930FA859-79C7-437F-B7F6-124895C6519E.201 <NULL>, error = 0x80D0000A

2017/09/14 14:37:18.1183666 2504 4296 DownloadManager [0]09C8.10C8::09/14/2017-14:37:18.118 [agent]Error 0x80d0000a occurred while downloading update 930FA859-79C7-437F-B7F6-124895C6519E.201; notifying dependent calls.

2017/09/14 14:37:18.1190350 2504 4296 DownloadManager [0]09C8.10C8::09/14/2017-14:37:18.119 [agent]Dynamic download data fetcher for ServiceId 7971F918-A847-4430-9279-4A52D1EFE18D does not exist.

...

...

 

I can't update to windows version 1703 because of error 0x8007001f

I can share mine.

Auto update every night failed since 6/18/2017. Same error code:

Feature update to Windows 10, version 1703 - Error 0x8007001f

Ran the Windows Update Troubleshooter and it fixed a few errors but still get the same error. E.g. Setuperr.log:

2017-07-12 08:40:40, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104

2017-07-12 08:40:40, Error MOUPG CSetupManager::ExecutePreDownloadMode(6844): Result = 0x800705BB

2017-07-12 08:40:40, Error MOUPG CSetupManager::ExecuteDownlevelMode(388): Result = 0x800705BB

2017-07-12 08:40:40, Error MOUPG CSetupManager::Execute(232): Result = 0x800705BB

2017-07-12 08:40:40, Error MOUPG CSetupHost::Execute(368): Result = 0x800705BB

2017-07-12 09:28:04, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057

2017-07-12 09:37:26, Error IBSLIB Failed to bind with firmware. Flags: 0x0 Status: c0000001[gle=0x00000003]

2017-07-12 09:37:27, Error MOUPG CDlpActionDiskSpaceReq::CalculateRequiredDiskSpaceInstallReq(1739): Result = 0x8007001F[gle=0x000000ea]

2017-07-12 09:37:27, Error MOUPG CDlpActionDiskSpaceReq::ExecuteInstallReq(1267): Result = 0x8007001F

2017-07-12 09:37:27, Error MOUPG CDlpActionDiskSpaceReq::ExecuteRoutine(489): Result = 0x8007001F

2017-07-12 09:37:27, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IDiskSpaceAction> > > >::Execute(441): Result = 0x8007001F

2017-07-12 09:37:27, Error MOUPG CDlpTask::ExecuteAction(3243): Result = 0x8007001F

2017-07-12 09:37:28, Error MOUPG CDlpTask::ExecuteActions(3397): Result = 0x8007001F

2017-07-12 09:37:28, Error MOUPG CDlpTask::Execute(1631): Result = 0x8007001F

2017-07-12 09:37:30, Error MOUPG CSetupManager::ExecuteTask(2083): Result = 0x8007001F

2017-07-12 09:37:30, Error MOUPG CSetupManager::ExecuteTask(2046): Result = 0x8007001F

2017-07-12 09:37:30, Error MOUPG CSetupManager::ExecuteInstallMode(745): Result = 0x8007001F

2017-07-12 09:37:30, Error MOUPG CSetupManager::ExecuteDownlevelMode(396): Result = 0x8007001F

2017-07-12 09:37:52, Error MOUPG CSetupManager::Execute(232): Result = 0x8007001F

2017-07-12 09:37:52, Error MOUPG CSetupHost::Execute(368): Result = 0x8007001F

 

Getting the same events here on a clean install of CU as well.

 

for warning eventID 360 (Windows Hello) there is probably no real fix so far, we have to wait for MS to fix it... but you can temporarily disable logging for this kind of event directly via event viewer - just navigate to Application and Services logs - Microsoft - Windows - User Device Registration - Admin and Disable Log in Actions... this should stop it

for error 37 similar recommendation via registry:
Small issue after upgrading to creator's update - Solved - Windows 10 Forums

 

The same with me - after clean install of CU yesterday got many errors 37, I'm accepting it as normal.