Uable to Update to 1803 - where to start?

Hi,


I am currently trying to update to 1803 which results in a rollback.

I have read the setuperr.log but am lost on how to identify the error that resuts in a rollback.

Is there a way to identify critical errrors? Ones that lead to an unsuccessfull update?

Here the setuperr.log:


2018-11-03 10:16:46, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2018-11-03 10:17:38, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

2018-11-03 10:17:44, Error CONX Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514): App Inventory returned duplicate file c:\windows\syswow64\rdrleakdiag.exe.[gle=0x8007000d]
2018-11-03 10:19:44, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2018-11-03 10:20:03, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{52776FBF-403C-49cc-b7cb-dd557f36096A} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2018-11-03 10:21:55, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get preferred homegroup with hr=0x80070490
2018-11-03 10:22:24, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2018-11-03 10:22:24, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2018-11-03 10:28:05, Error MOUPG Finalize: Error reading narrator reg key: [0x80070002]
2018-11-03 10:28:08, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot (kd_*_*.dll). Last Error = 0x6[gle=0x00000006]
2018-11-03 10:28:08, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot (kdstub.dll). Last Error = 0x6[gle=0x00000006]
2018-11-03 10:35:03, 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 *)
2018-11-03 10:37:39, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] shell\shmig\propsysschema.cpp(29)\shmig.dll!00007FF8B8E73B47: (caller: 00007FF8B8E7344A) LogHr(1) tid(4f4) 80070002 Das System kann die angegebene Datei nicht finden.

2018-11-03 10:37:39, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] shell\shmig\propsysschema.cpp(34)\shmig.dll!00007FF8B8E73B8C: (caller: 00007FF8B8E7344A) LogHr(2) tid(4f4) 80070002 Das System kann die angegebene Datei nicht finden.

2018-11-03 10:37:39, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: offline key (new) = '$OFFLINE_RW_003ADB7E$SYSTEM\Setup\Upgrade\Bridge'
2018-11-03 10:37:39, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
2018-11-03 10:37:40, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment}. Error: 0x80070002
2018-11-03 10:37:40, Error SP Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
2018-11-03 10:37:49, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{52776FBF-403C-49cc-b7cb-dd557f36096A} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2018-11-03 10:37:54, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-TabletPC-CoreInkRecognition[@version="10.0.16299.15" and @arch="amd64" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
2018-11-03 10:38:05, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="%windir%\system32\migration\CntrtextMig.dll", CLSID={dedf860b-4cd6-4d6b-9823-f656a2b2462b}, ThreadingModel=Apartment}. Error: 0x80010105
2018-11-03 10:38:05, Error SP Error READ, 0x80010105 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Work\MachineIndependent\Working\agentmgr\CCSIAgent,%windir%\system32\migration\CntrtextMig.dll,{dedf860b-4cd6-4d6b-9823-f656a2b2462b},Apartment. Will return 2[gle=0x000000cb]
2018-11-03 10:38:10, Error SP SPRecordOSFootprint: Opening setupcl request key failed. Error: 0x00000002



Thanks

Weiterlesen...

 

Hi,

In my experience I've been able to fix failed updates like this using the update assistant. Rather than Windows update itself. Since it's also intended for updates from the older Windows versions. It assumes nothing about the current installation and doesn't
try to reuse files which may be corrupt causing the update to fail.

Afterwards mine worked flawlessly everytime. If you want to try this it's available from the update now button on the Windows 10 download page. I can't link it from mobile unfortunately.

I hope that helps.

 

ja, der Hund liegt tiefer begraben. Jetzt finde ich die Seite nicht mehr, wo ich das gelesen habe. Das Startmenü ist mit einer neuen speziellen internen Applikation (bzw. Code) programmiert und ist scheinbar noch generell problematisch im Verhalten zu standardmäßigen Ausführungen. Da es hier zu so gehäuften identischen Problemen kommt, ist hier wohl noch ein Entwicklungsschritt zur Kompatiblität seitens Microsoft notwendig.

Es gibt dazu folgende außer der einfachen genannten Reparaturmöglichkeiten:

Startmenü reparieren Windows 10 Deskmodder Wiki
Has your Windows 10 Start menu stopped working? Here are four ways to fix it - BT
Reparatur des Store

 

You should upgrade to 1803 by manual method. Execute below steps -

1. Right click on Windows Start > Windows Powershell (Admin)

Type following (or copy and paste following) one by one and Enter

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Ren C:\Windows\System32\catroot2 Catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

2. Type following in Windows Start Search box and hit Enter %systemroot%\Logs\CBS > Rename CBS.Log to something else.

If it doesn't allow you to rename - Type services in Windows Start Search box > Click Services > Scroll down to find the Windows Modules Installer service and double-click on it > Set its startup type to Manual > Reboot your computer

Go to C:\Windows\Logs\CBS > Rename CBS.Log > Reboot your computer > Then go back into the Services App and set Windows Modules Installer Service back to Automatic Startup (Note CBS log files contain information about windows update, SFC etc)

(Source -
https://partnersupport.microsoft.com/en-us/par_...)

3. Uninstall any third party Antivirus (After update is successful, you can install it again)

4. You can go to
https://www.microsoft.com/en-us/software-downlo...

You can download the latest Windows 10 package from this link (media creation tool) and follow the instructions there to upgrade. Use the very simple instructions given under Using this tool to upgrade this PC to Windows 10

If above is not successful and the update errors out - Download SetupDiag which is Microsoft's standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.

https://go.microsoft.com/fwlink/?linkid=870142

The log generated will be having the name of SetupDiagResults.log. Zip the log generated and upload to Onedrive and share the link here.

Need Setuperr.log and Setupact.log from

C:\$Windows.~BT\Sources\Rollback\

or

C:\$Windows.~BT\Sources\Panther

Note - These folders are hidden, so you will have to do File Explorer > View > Options > View tab > Select Show hidden files, folders and drives.

 

https://www.borncity.com/blog/2011/0...h-und-deutsch/
https://www.computerbase.de/forum/th...glisch.921671/
https://www.win-10-forum.de/windows-...ram-files.html