Windows 10 Creators Update 1703 fails - SP pDUSearchAndDownload: DU search failed. hr = 0x800705b4

Hello,

I installed Windows 10 Creators Update 1703 successfully on 3 PC's.

3 Methods attempted unsuccessfully:
- Windows Update Assistant
- Windows Media Creation Tool
- Update from .iso File

Windows Update is working properly - latest Updates are installed.
SFC /scannow completed without Errors.

Now on the 4th PC the Update is failing with following Errors in:
C:\$WINDOWS.~BT\Sources\Panther\setuperr.lo

2017-04-12 08:25:23, Error                 SP     pDUSearchAndDownload: DU search failed. hr = 0x800705b4
2017-04-12 08:25:23, Error                 MOUPG  DUSetup: Failed to execute DUSetup seach and download  [0x800705b4]
2017-04-12 08:25:23, Error                 DU     Unreleased DUUpdateCollection interface during DUSession release
2017-04-12 08:25:23, Error                 CONX   Windows::Compat::Shared::UtcLogger::SetServiceState (643):   Error starting service: [1058].[gle=0x80070422]
2017-04-12 08:25:23, Error                 CONX   Windows::Compat::Shared::UtcLogger::Begin (112):   Error starting service: [0x80070422].[gle=0x80070422]
2017-04-12 08:25:24, Error                 CONX   Windows::Compat::Appraiser::AppraiserSettings::GetSettingsInternal (228):   Failed to Query OneSettings [0x80070002].[gle=0x80070002]
2017-04-12 08:27:27, Error                 DU     DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2017-04-12 08:29:00, Error                 CONX   Windows::Compat::Appraiser::DriverInventory::MakeAndAppendAssetFromInf (367):   Error getting driver info: [0xe0000100].[gle=0xe0000100]
2017-04-12 08:29:00, Error                 CONX   Windows::Compat::Appraiser::DriverInventory::FindAndAppendDriversFromFolder (298):   Error creating asset from C:\$WINDOWS.~BT\Drivers\DU\5d81600a-b943-4c7a-bef3-146b76279f3c\autorun.inf: [0xe0000100].[gle=0xe0000100]
2017-04-12 08:29:00, Error                 CONX   Windows::Compat::Appraiser::DriverInventory::FindAndAppendDriversFromFolder (283):   Error appending in subdirectory C:\$WINDOWS.~BT\Drivers\DU\5d81600a-b943-4c7a-bef3-146b76279f3c: [0xe0000100].[gle=0xe0000100]
2017-04-12 08:29:00, Error                 CONX   Windows::Compat::Appraiser::DriverInventory::FindAndAppendDriversFromFolder (283):   Error appending in subdirectory C:\$WINDOWS.~BT\Drivers\DU: [0xe0000100].[gle=0xe0000100]
2017-04-12 08:29:00, Error                 CONX   Windows::Compat::Appraiser::DriverInventory::GetInventory (201):   Error finding and appending drivers: [0xe0000100].[gle=0xe0000100]
2017-04-12 08:29:34, Error                 CONX   Failed hashing for syswow64\drivers\asio.sys, 0x80070003

2017-04-12 08:29:34, Error                 CONX   Failed hashing for [syswow64\drivers\asio.sys] 0x80070003

2017-04-12 08:29:34, Error                 CONX   Failed hashing for syswow64\drivers\asupio.sys, 0x80070003

2017-04-12 08:29:34, Error                 CONX   Failed hashing for [syswow64\drivers\asupio.sys] 0x80070003

2017-04-12 08:35:39, Error                 SP     Failed to get driver info from external driver package C:\$WINDOWS.~BT\Drivers\DU\5d81600a-b943-4c7a-bef3-146b76279f3c\autorun.inf. Error: 0xE0000100[gle=0x0000007a]
2017-04-12 08:35:45, Error                 SP     pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2017-04-12 08:36:11, Error                 CSI    00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #91817# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })
[gle=0x80004005]
2017-04-12 08:36:13, Error                 CSI    00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #154614# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })
[gle=0x80004005]
2017-04-12 08:36:28, Error                 CSI    00000003 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #231640# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })
[gle=0x80004005]
2017-04-12 08:36:40, Error      [0x080831] MIG    CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2017-04-12 08:38:11, Error      [0x0808fe] MIG    Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get homegroup members with hr=0x8007000D
2017-04-12 08:38:37, Error                        CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2017-04-12 08:38:37, Error                 SP     CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2017-04-12 08:38:40, Error                 IBSLIB BcdCopyObjectEx: Failed to enumerate source elements. Target: {0f63a800-3c9e-11e5-a316-f2e80a0db779} Flags: 0x4 Status: c0000022[gle=0x00000002]
2017-04-12 08:38:40, Error                 IBSLIB Failed to clone store. Status: c0000022[gle=0x00000002]
2017-04-12 08:38:40, Error                 IBSLIB BcdExportStore: Failed delete existing file at \??\C:\$WINDOWS.~BT\Sources\Rollback\Boot\BCD. Status: c0000022[gle=0x00000002]
2017-04-12 08:38:40, Error                 IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: Failed to backup BCD database from "F:\Boot\BCD" to "C:\$WINDOWS.~BT\Sources\Rollback\Boot\BCD".[gle=0x00000005]
2017-04-12 08:38:40, Error      [0x064199] IBSLIB SetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(5), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000005]
2017-04-12 08:38:40, Error      [0x06418a] IBSLIB RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(5), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CCheckpointImpressario::SetCheckpoint(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)
void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000005]
2017-04-12 08:38:40, Error      [0x06414e] IBSLIB RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint) failed. Disabling Rollback.[gle=0x00000005]
2017-04-12 08:38:40, Error                 SP     Error setting OS Switch Rollback checkpoint[gle=0x00000005]
2017-04-12 08:38:40, Error                 SP     Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]
2017-04-12 08:38:40, Error                 MOUPG  MoSetupPlatform: Finalize reported failure![gle=0x000000b7]
2017-04-12 08:38:40, Error                 MOUPG  MoSetupPlatform: Using action error code: [0x80004005][gle=0x000000b7]
2017-04-12 08:38:40, Error                 MOUPG  CDlpActionFinalize::ExecuteSetupPlatformFinalize(1018): Result = 0x80004005[gle=0x000000b7]
2017-04-12 08:38:40, Error                 MOUPG  CDlpActionFinalize::ExecuteRoutine(435): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CSetupManager::ExecuteTask(2083): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CSetupManager::ExecuteTask(2046): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CSetupManager::ExecuteInstallMode(833): Result = 0x80004005
2017-04-12 08:38:57, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(396): Result = 0x80004005
2017-04-12 08:39:01, Error                 MOUPG  CSetupManager::Execute(232): Result = 0x80004005
2017-04-12 08:39:01, Error                 MOUPG  CSetupHost::Execute(368): Result = 0x80004005
2017-04-12 08:39:03, Error                 CONX   Windows::Compat::Shared::UtcLogger::SetServiceState (643):   Error starting service: [1058].[gle=0x80070422]
2017-04-12 08:39:03, Error                 CONX   Windows::Compat::Shared::UtcLogger::End (274):   Error starting service: [0x80070422].[gle=0x80070422]

Please Advise

 

Question Info


Last updated April 23, 2019 Views 3,529 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,

To assist you with your concern, you can follow these steps to isolate/fix the issue on updating to the Creators Update:

1st Method:

  1. Perform a clean boot to start Windows using minimal set of drivers and startup programs.
  2. Then perform System File Check using the Command Prompt (Admin).
  3. Reboot Machine.
  4. Try to install again.

2nd Method:

  1. Download the Windows Update Troubleshooter tool.
  2. Click Next to continue.
  3. Click the Try troubleshooting as an administrator option (if applicable).
  4. Select Windows Update again.
  5. Click Next to start the troubleshooting process.
  6. Click Close.
  7. Reboot your machine.
  8. Try to install again.

We will wait for your response.

Regards.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Jay Jap,

first thanks for your Reply.

Unfortunately I already went through those 2 Options as they were mentioned in official Microsoft Windows Help Articles in Context with common Windows Update Troubleshooting.

Unfortunately I forgot to mention that though in my Help Request.

The Update Troubleshooter Tool did not even find anything wrong.

All Checkmarks were green & previous Updates installed all well - they went through without Issues.

The sfc /scannow System File Check I have performed as well - didn't I mention that in my initial Post ?

Probably you overlooked that.

I did not mention that I ran this System File Check with & without Clean Boot though.

Both Attempts did not find anything to be fixed at all.

I even used DISM against an ISO-Image based on Release 1607, which finished successful without Fixing Results as well.

One additional Detail I should have mentioned is that all Drivers installed are well maintained to latest available Versions.

Please advise on how to proceed ?

Thanks & Regards

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You can try this: https://www.thegeneralistit.com/blog/2015/10/02/fixing-windows-10-update-error-0x800705b4/

Worked for me and I hope it works on your problem

Sincerely

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

@ Gina Coleman

Unfortunately the Link you provided is not helpful since the Problem I reported has a different Context.
I did not try to update via Windows Update, since the Update is not provided via that Path for me yet.

Instead I used the Windows Update Assistant to force the Update & I also used the Media Creation Tool Option to force the Installation of the Update.

By the way the described Process there is basically a well known Way of starting Windows Update Troubleshooting.
As I said before in this Thread I already went through that path and the check Result was green - nothing to fix.

Also the Problem there was Error Code 0x800705b4
The one I encountered was 0x80004005 which seems to be quite unspecific / very generic according to its Explanations by Microsoft.


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you for the feedback. Try to disable your antivirus and firewall and try to perform the update.

You can refer this article on how to turn off your Windows Firewall.

Note: You should not turn off Windows Firewall unless you have another firewall enabled. Turning off Windows Firewall might make your computer (and your network, if you have one) more vulnerable to damage from worms or hackers.

Let us know how it goes.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

@Jay Jap

Hey Man are you serious ?

Of Course I did that as I did with all major Windows Upgrades.

This is not a Hint but rather a Step of Common Sense to be recommended to Windows / IT Rookies, isn't it ?

No seriously if you read the Log File I provided:
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log

This rather reads / seems to point to a Problem with collecting installed Drivers during for the Windows Upgrade !?
Unfortunately like often in such Cases the Error Logs are so cryptic - lacking clear Information which Driver or Software is causing the Problems !?

I really appreciate the attempts of People here trying to provide help, but so far it seems the People responding so far were willing to Help as well as they could but no one had the technical Knowledge to really analyze the Upgrade Error Log File I provided ?

Well I am IT Professional - but the Problem is I don't quite understand the Upgrade Error Log either.

It really seems to be a Driver Problem - but the Log is lacking a clear Statement of which one is causing the Problem !?

Why the Heck is Microsoft not capable to write better Installation Routines which at least log the Errors during Setup in clear-Text instead of such cryptic Error Codes which seems to be readable by Microsoft Professional Personnel only ?

Since I already tried all the Options documented by Microsoft Support Paqes & suggested by People here (thanks to Everyone willing to help) - I guess a MS Professional capable to translate the Error Log into Common Sense is needed to get down to the Root Cause of the Problem ?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Based on the logs, it contains information about setup error during the installation.

It seems you have tried everything on your end.

I would suggest that post this in TechNet to get a more help from qualified IT's.

Pretty much it's already out of scope of the community forum.

I'm interested in this scenario and I hope some veteran members can help you out.

By the way, you can also post it in Microsoft TechNet just to make it visible with the IT masters.

Sorry, not much help.

La flatulencia se azules

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

thanks for your Attitude / Attempt in trying to help - however MS Technet is from where I initially came from - they sent me to here ....

From the Community here I really appreciate that you Guys here truly tried to help.

However from Microsoft -> Not even 1 Serious Attempt to analyze the Installation Log or any other Attempt to help with the Problem.....

Very disappointing ....
Makes me even more convinced to replace Microsoft Windows with Linux.
So far I had it as a second OS but the Experience in Support Issues is by far much better on Linux !
Guess I will go for Linux Mint Distribution then.

I may possibly run a Windows as a Virtual Machine then but not as a primary OS anymore !

As I say I value the Community Attempt here - Thanks to you Guys here.
However I am quite pissed about the Attitude of Microsoft as they did not even attempt to provide any help at all !!!

11 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

From my talks with Micro$oft support and other techs, its a hardware related "incompatibility" problem; usually a chipset.  Funny thing is that if I install the software on a machine, clone the drive, then clone it back to the machine, it usually works fine.  I have mainly seen this error with Intel Atom Processors.  The creator update checks for the chipsets / processor for certain "magical" conditions.  I haven't yet found an easy way around this, Microsoft told me that "At this time some Atom processors are not supported under the creator update".  The Anniversary update 1607 and before seem to work still on it.  When these voodoo magical conditions are detected with the hardware, the updates to creator update are detected and blocked.  Processor was Atom Z3775, I have seen this on other machines with different models of Atom as well.

https://social.technet.microsoft.com/Forums/windows/en-US/6a42b9db-2495-4df7-acd9-66480ce2abb5/creators-update-windows-10-is-no-longer-supported-on-this-pc-uninstall-this-app?forum=win10itprogeneral

On the machines I cloned if there were issues with the processor / video chipset, the tiles acted funny, sometimes crashed the machine and the text was absent from the tiles.  I used Clonezilla to copy the drive.

I really wish the installer would give better feedback of what was going on in the GUI for the installer instead of "Something went wrong", etc

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello WyoComputers,

with all Respect - that Statement of Hardware-Incompatibility is complete **** !!!

The Statement of Reason is such simple:

If it really was a Hardware-Problem it would have been not resolved by a complete Re-Installation of Windows 10.

But on one Aspect you are totally right - I fully agree that the Installer Error Messages are complete useless.

Anyways - after Re-Installation I am quite pissed about Microsoft - planning to move to LINUX for productive Work soon.
Please don't get me wrong - I appreciate any Users who tried to help with this Issue.

However in the End it was in vain.

Thanks anyway

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.