Update from 1607 to 1703 returns ...-Ox20017 error and Dism won't work 0x800f081f

[yvessr]

Please help me ...

For several days now I am trying without success to update my Acer travelmate laptop from Win10 Pro v1607 to v1703.
1. when I launch update search I got a message that my computer is fully updated...
2. when I run the suggested Creators I got a final error return 0xc1900101-0x20017 (boot error)
3. SFC command tells me that several files cannot be repaired...
4. DISM restore health command aborts with a 0x800f081f error... I than downloaded the latest Win10 version and tries another Dism repair with a local install.esd setting but it returns the same error !
5. Finally I ran ADWCleaner and Spyhunter but NO bugs were found...

So now I am completely out of ideas... what can I do to repair all the Dism errors and than update to v1703 ???

PLEASE help me... and THANKS a lot !

 

[Regedit32]

Hi yvessr,

Open File Explorer and navigate to C:\

Now in the File Explorer ribbon select the View tab then check the box next to Hidden items

This ought to allow you to see a directory named $Windows.~BT

Open this directory then inside it, open the Sources directory. You should now see another directory named Panther. Open the Panther directory.

Inside the Panther directory you should see a log named setuperr.log

Could you upload that log here for us to take a look at please. You may need to right-click and send to a compress folder so you can upload a zipped folder [ but it may just upload as is too; sorry I'm not sure if .log is clear for a direct upload here ].

Meanwhile, you could also right-click and select Open with and select Notepad to take a look at the log yourself. My assumption is you will find the System is struggling with either .inf or .dll files, which the log ought to identify and that will give us some clues on how to resolve your issue.


The other factor that may be in play here, is you may have some external devices connected to the computer that do not need to be there while you install the update. Printers, external hard drives, thumb drives, etcetera. It often helps to disconnect these before installing a significant update.

Also, if you are running third party security applications like Norton, McAfee, Trend Micro Security, etcetera, it is often useful to disable these while you install the update. Once the update is installed successfully, you can then re-enable the security applications.

 

[yvessr]

Hi yvessr,

Open File Explorer and navigate to C:\

Now in the File Explorer ribbon select the View tab then check the box next to Hidden items

This ought to allow you to see a directory named $Windows.~BT

Open this directory then inside it, open the Sources directory. You should now see another directory named Panther. Open the Panther directory.

Inside the Panther directory you should see a log named setuperr.log

Could you upload that log here for us to take a look at please. You may need to right-click and send to a compress folder so you can upload a zipped folder [ but it may just upload as is too; sorry I'm not sure if .log is clear for a direct upload here ].

Meanwhile, you could also right-click and select Open with and select Notepad to take a look at the log yourself. My assumption is you will find the System is struggling with either .inf or .dll files, which the log ought to identify and that will give us some clues on how to resolve your issue.


The other factor that may be in play here, is you may have some external devices connected to the computer that do not need to be there while you install the update. Printers, external hard drives, thumb drives, etcetera. It often helps to disconnect these before installing a significant update.

Also, if you are running third party security applications like Norton, McAfee, Trend Micro Security, etcetera, it is often useful to disable these while you install the update. Once the update is installed successfully, you can then re-enable the security applications.

 

[yvessr]

THANX so much @regedit for your help !...

I am not allowed to send either .log nor .rar files so I copied the Notepad:

2017-07-04 12:22:15, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104
2017-07-04 12:22:15, Error MOUPG CSetupManager::ExecuteInstallMode(753): Result = 0x800705BB
2017-07-04 12:22:15, Error MOUPG CSetupManager::ExecuteDownlevelMode(396): Result = 0x800705BB
2017-07-04 12:22:18, Error MOUPG CSetupManager::Execute(232): Result = 0x800705BB
2017-07-04 12:22:18, Error MOUPG CSetupHost::Execute(368): Result = 0x800705BB
2017-07-04 12:32:44, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2017-07-04 12:45:33, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2017-07-04 12:46:30, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:46:30, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:46:46, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:46:46, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:46:49, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:46:49, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:46:52, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:46:52, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:00, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:00, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:00, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:00, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:08, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:08, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:08, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:08, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:10, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:10, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:10, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:10, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:18, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:18, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:18, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:18, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:20, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:20, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:20, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:20, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:23, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #156120# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 660072002d00460052000000 })
[gle=0x80004005]
2017-07-04 12:47:29, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:29, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:47:29, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:47:29, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:48:29, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:48:29, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:48:29, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:48:29, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:48:51, Error CSI 00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #233925# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 660072002d00460052000000 })
[gle=0x80004005]
2017-07-04 12:48:58, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:48:58, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:48:58, Error [0x08085e] MIG MigHost: CMigPluginSurrogate::LoadDllServer: Invalid argument: BinaryPath=[C:\WINDOWS\system32\McxDriv.dll] does not exist.[gle=0x00000002]
2017-07-04 12:48:58, Error [0x0808ff] MIG COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\WINDOWS\system32\McxDriv.dll, {0036ED2D-822F-41D0-BF8F-58A4E6774917}, 0) failed, hr=[0x80070002].
2017-07-04 12:49:33, 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-07-04 12:56:05, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get homegroup members with hr=0x8007000D
2017-07-04 12:57:29, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2017-07-04 12:57:29, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]


... hope you can solve my problem !

 

[Regedit32]

What processor does your computer have?

Is it an Intel processor?

e.g. Intel G3258


From the looks of the log it appears its attempting to load a non-existent driver named McxDriv.dll

Back in Windows 7 days errors like that usually pointed to the MIG Upgrade Service and you could manually block this temporarily while you installed an update. However the DLL you blocked, no longer exists in Windows 10, so we cannot take that approach.

 

[yvessr]

YES it's an Intel Core 2 Duo processor T7700

 

[Regedit32]

The reason I asked about that was because there were some Intel Processors that triggered errors like you have been having. There was a guy who manually slowed his processor down, just to install the creator update, then resurrected the standard processor speeds after getting through the installation.

I'm not sure your particular version though falls into that category.

I'll see if I can find some more information on the specific hardware issues related to that error code for you so we can confirm one way or the other.

 

[yvessr]

Thank you very much @Regedit32, I appreciate !... but... Windows10 v1603 is well running with that dll ...???

 

[Regedit32]

Oh do you have the McxDriv.dll on your computer?

If yes, where is it currently located?

 

[yvessr]

... and I feel I have to mention a very, very strange behaviour of my laptop after each attempt to install/upgrade to v1703:

at the end of the 'installation' I find my computer complete switched OFF (battery light OFF, just mains light on); than when I push the start button NOTHING happens (battery light doesn't come on and pc doesn't restart !!!...
The ONLY way (I found) to have my computer responding again is to REMOVE the battery for some seconds and push it back in place ... than the laptop is starting up normally again !!!

This NEVER happened before !...Incredible !!!

 

[Regedit32]

How old is this computer?

What was the original Windows OS running on it?

 

[yvessr]

It's an ACER Travelmate 6592G, originally with Windows Vista !

... 40 min ago I launched a search on my C-disk for McxDriv.dll-file but still nothing was found... still running !

 

[Wolfie]

Try the following:

https://www.windows10forums.com/thr...ws-10-to-the-latest-version.13015/#post-64095

 

[yvessr]

Hi @Regedit32,

I ran I full overnight detailed search on the C:-disk of my PC any NO such McxDriv.dll -file was found !!!....
What about the setuperr.log ?????????



.................................

Hi Wolfie,

ALL of these update methods have been tested but NONE was successfull ... all end with a 'power locked' computer and same error issue 0xc1900101-0x20017 (boot error)...

 

[Wolfie]

HI yvessr,

do you have a recovery partition on your computer?, if you do; you can do a full system fresh install but make sure you have all your data backed up before you start!.

When you boot your PC, look at the boot screen and press (most likely) F11 for any recovery options!.

The other option is to use a fresh version of W10 on a USB stick or DVD and when you get to the first window, look at the bottom left for "Repair your computer" and see what you can with that!:

 

[Saltgrass]

About all I can pass along is for the extended error code you show. Below is an explanation of what is happening at the time such and error would have been seen.

I haven't looked through the log entries you posted but I normally like to look at the setupact.log since it shows the entire process, not just the error codes. The problem with that log is it might contain some entries you would not want to make public.

Safe OS phase: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed.

• Example error codes: 0x2000C, 0x20017

 

[yvessr]

Thank you @Saltgrass for your reply... but in the meanwile the situation changed significantly...

My Win10 finished completely locked up... NO booting at all anymore... and therefore I decided to reinstall a new version of win10.
Ofcourse I had to reinstall numerous applications but at least my computer 'worked' and I got again access to my mailbox and internet.
BUT... 'winver' tell me I am now on Version 10.0 number 10240 !!!...
I made all updates, ran DISM and checked SFC and that was all OK; however when I try to update my win10 using Mediacreationtool evrything starts well but after the final restart I am brought back to 10240 with the same (damned) error ...-Ox20017 !!!

I do not at all what to do now ... can you help ?

Thanks a lot !

 

[Saltgrass]

How about using the snipping tool to get us a picture of your Disk Management window. Try to expand it enough so we can see the descriptions of the partitions.

You can do a clean install with the current build. I don't know your situation regarding any OEM software or recovery options, but it might be best to go straight to the last upgrade. The one caveat is your system may have some device which is not compatible with the newer builds.

 

[yvessr]

Here is a snapshot of my disk management: you'll see it is in french... sorry, that's my install language

 

[Saltgrass]

You only have 44 GB available on your primary drive. This should be enough but you might think about moving something off and making more room if nothing else seems to work.

The 5BB error you are getting at the start of the log means the application must be restarted. It may eventually restart but you would not see that on this log. If it doesn't restart maybe some of the other errors are related. But since I can't get good info from the log I will go a different direction.

You stated in a recent post that SFC finished without errors, is that still correct?

I have a Dell system which came with Vista and now seems to run earlier Win 10 builds fine. I have not tried a recent one but I had replaced some components in the system. Mainly the Wi-fi/Bluetooth adapter. If you can disable anything in the Bios prior to doing the upgrade you might try that. If you have the install media, you can do an upgrade without the network connection or Bluetooth or sound or whatever might not be needed to complete the upgrade. External USB devices not need can certainly go. There have been some updates which had problems with certain types of Wireless mice.