PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Win 10 - Problem: Side by Side Konfiguration ungültig


Voodoo6000
2016-09-02, 20:34:17
Ich bekomme unter Win 10 immer die Fehlermeldung "Die Anwendung konnte nicht gestartet werden,da Side by Side Konfiguration ungültig" wenn ich z.B. Firefox starten möchte.
Hat jemand eine Idee bzw. wird aus der Fehlermeldung schlauer? Einige Beiträge die ich zu "Side by Side Konfiguration ungültig" unter Win7 in Forenen gelesen habe, deuteten auf eine fehlende Runtime hin. Ich habe die vermeintlich fehlende Visual C++ 2010 Redistributable und ein ganzes Paket mit verschiedenen Runtimes(All in One Runtimes) herunter gelanden, kann die exe des Installers aber nicht ausführen, da dann auch die Side by Side Konfiguration ungültig Fehlermeldung kommt.

Über Hilfe würde ich mich sehr freuen.

Hier die genaue Fehlermeldung
Fehler beim Generieren des Aktivierungskontextes für "System Default Context". Fehler in Manifest- oder Richtliniendatei "C:\Windows\WinSxS\manifests\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.1 0240.17071_none_d1539302af73ebbf.manifest" in Zeile 0. Ungültige XML-Syntax.



CBS Log nach sfc /scannow mit Fehler
2016-09-01 22:25:06, Info CBS TI: --- Initializing Trusted Installer ---
2016-09-01 22:25:06, Info CBS TI: Last boot time: 2016-08-29 17:33:44.485
2016-09-01 22:25:06, Info CBS Starting TrustedInstaller initialization.
2016-09-01 22:25:06, Info CBS Ending TrustedInstaller initialization.
2016-09-01 22:25:06, Info CBS Starting the TrustedInstaller main loop.
2016-09-01 22:25:06, Info CBS TrustedInstaller service starts successfully.
2016-09-01 22:25:06, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2016-09-01 22:25:06, Info CBS Startup processing thread terminated normally
2016-09-01 22:25:06, Info CBS Idle scavenging initiated
2016-09-01 22:25:06, Info CBS Starting TiWorker initialization.
2016-09-01 22:25:06, Info CBS Ending TiWorker initialization.
2016-09-01 22:25:06, Info CBS Starting the TiWorker main loop.
2016-09-01 22:25:06, Info CBS TiWorker starts successfully.
2016-09-01 22:25:06, Info CBS Universal Time is: 2016-09-01 20:25:06.974
2016-09-01 22:25:06, Info CBS Loaded Servicing Stack v10.0.10240.17020 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.17020_none_1152834562020692\cbscore.d ll
2016-09-01 22:25:06, Info CSI 00000001@2016/9/1:20:25:06.990 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe42528889 @0x7ffe5f679323 @0x7ffe5f63ca89 @0x7ff6df5e2ee0 @0x7ff6df5e4521 @0x7ffe7f1ab0b3)
2016-09-01 22:25:06, Info CBS NonStart: Set pending store consistency check.
2016-09-01 22:25:06, Info CBS Maint: starting/resuming idle maintenance
2016-09-01 22:25:06, Info CBS Session: 30540942_3990871598 initialized by client CbsTask, external staging directory: (null)
2016-09-01 22:25:06, Info CBS Maint: processing started. Client: CbsTask, Session: 30540942_3990871598
2016-09-01 22:25:06, Info CBS Maint: launch type: ScheduledTask
2016-09-01 22:25:07, Info CBS Reboot mark set
2016-09-01 22:25:07, Info CBS Winlogon: Registering for CreateSession notifications
2016-09-01 22:25:07, Info CBS Winlogon: Loading SysNotify DLL
2016-09-01 22:25:07, Info CBS Winlogon: Starting notify server
2016-09-01 22:25:07, Info CBS Maint: begin archive logs
2016-09-01 22:25:11, Info CBS Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20160901202506.cab.
2016-09-01 22:25:11, Info CBS CAB compressed log file: C:\Windows\Logs\CBS\CbsPersist_20160901202506.log
2016-09-01 22:25:11, Info CBS Maint: end archive logs, archive time so far: 4 seconds
2016-09-01 22:25:11, Info CBS Maint: begin scavenge
2016-09-01 22:25:11, Info CBS Scavenge: Start CSI
2016-09-01 22:25:15, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x75fe81fb40
2016-09-01 22:25:15, Info CSI 00000003 Creating NT transaction (seq 1), objectname [6]"(null)"
2016-09-01 22:25:15, Info CSI 00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x2bc
2016-09-01 22:25:15, Info CSI 00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2016-09-01 22:25:15, Info CSI 00000006@2016/9/1:20:25:15.428 Beginning NT transaction commit...
2016-09-01 22:25:15, Info CSI 00000007@2016/9/1:20:25:15.428 CSI perf trace:
CSIPERF:TXCOMMIT;1190
2016-09-01 22:25:15, Info CSI 00000008 CSI Store 506767304544 (0x00000075fdaf6760) initialized
2016-09-01 22:25:15, Info CSI 00000009@2016/9/1:20:25:15.428 CSI Transaction @0x75fdafabb0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id [26]"TI6.30540942_3990871598:1/"

2016-09-01 22:25:15, Info CBS Scavenge: Begin CSI Store
2016-09-01 22:25:16, Info CSI 0000000a Performing 1 operations as follows:
(0) Scavenge: flags: 00000037
2016-09-01 22:25:16, Info CSI 0000000b Scavenge: Begin processing lists
2016-09-01 22:25:16, Info CSI 0000000c Scavenge: Setting maximum delta file size limit to 31 MB.

2016-09-01 22:25:17, Info CSI 0000000d Scavenge: Begin planning
2016-09-01 22:25:26, Info CSI 0000000e Skip up level servicing stack: [l:188{94}]"amd64_microsoft-windows-msmq-installer_31bf3856ad364e35_10.0.10240.16384_none_831216e19ae1de55"
2016-09-01 22:25:42, Info CSI 0000000f Skip up level servicing stack: [l:184{92}]"x86_microsoft-windows-msmq-installer_31bf3856ad364e35_10.0.10240.16384_none_26f37b5de2846d1f"
2016-09-01 22:25:44, Info CSI 00000010 Scavenge: Planning Complete.
The following actions will be performed:
Regeneration Candidates: 133
Removal Candidates: 14566
Superseded/LDR (Delta Compression) Candidates: 862
Null-Delta Compression Candidates:
Mutable file Candidates: 4
Boot-Recovery Candidates: 72
Deletion Candidates (Non Driver): 0
Driver Deletion Candidates: 14

2016-09-01 22:25:45, Info CSI 00000011 Creating NT transaction (seq 2), objectname [6]"(null)"
2016-09-01 22:25:45, Info CSI 00000012 Created NT transaction (seq 2) result 0x00000000, handle @0x135c
2016-09-01 22:25:45, Info CBS Idle scavenging stop signaled.
2016-09-01 22:25:45, Info CSI 00000013@2016/9/1:20:25:45.773 Beginning NT transaction commit...
2016-09-01 22:25:46, Info CSI 00000014@2016/9/1:20:25:46.273 CSI perf trace:
CSIPERF:TXCOMMIT;959232
2016-09-01 22:25:46, Info CSI 00000015 ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=5
2016-09-01 22:25:46, Info CSI 00000016 Creating NT transaction (seq 3), objectname [6]"(null)"
2016-09-01 22:25:46, Info CSI 00000017 Created NT transaction (seq 3) result 0x00000000, handle @0x30c
2016-09-01 22:25:46, Info CSI 00000018 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2016-09-01 22:25:46, Info CSI 00000019@2016/9/1:20:25:46.336 Beginning NT transaction commit...
2016-09-01 22:25:46, Info CSI 0000001a@2016/9/1:20:25:46.429 CSI perf trace:
CSIPERF:TXCOMMIT;178162
2016-09-01 22:25:46, Info CBS Scavenge: Incomplete, disposition: 0X20001
2016-09-01 22:25:46, Info CBS Scavenge: Ending scavenging early. Either a client connected or shutdown has begun.
2016-09-01 22:25:46, Info CSI 0000001b@2016/9/1:20:25:46.429 CSI Transaction @0x75fdafabb0 destroyed
2016-09-01 22:25:46, Info CBS Maint: end scavenge, scavenge time so far: 35 seconds
2016-09-01 22:25:46, Info CBS Maint: TransientManifestCache disabled in config.
2016-09-01 22:25:46, Info CBS Maint: incomplete, interruptions: 1, (this pass: time: 39 seconds, used space change: -16512 KB, hr: 0x00000000, source: N/A)
2016-09-01 22:25:46, Info CBS Reboot mark cleared
2016-09-01 22:25:46, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2016-09-01 22:25:46, Info CBS Winlogon: Deregistering for CreateSession notifications
2016-09-01 22:25:46, Info CBS Maint: processing complete. Session: 30540942_3990871598. [HRESULT = 0x00000000 - S_OK]
2016-09-01 22:27:46, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2016-09-01 22:27:46, Info CBS TiWorker signaled for shutdown, going to exit.
2016-09-01 22:27:46, Info CBS Ending the TiWorker main loop.
2016-09-01 22:27:46, Info CBS Starting TiWorker finalization.
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: ManifestCacheFinalize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2016-09-01 22:27:46, Info CBS Ending the TrustedInstaller main loop.
2016-09-01 22:27:46, Info CBS Starting TrustedInstaller finalization.
2016-09-01 22:27:46, Info CBS Winlogon: Stopping notify server
2016-09-01 22:27:46, Info CBS Winlogon: Unloading SysNotify DLL
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2016-09-01 22:27:46, Info CBS Ending TrustedInstaller finalization.
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CoreResourcesUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: SessionManagerFinalize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: WcpUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: DrupUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CfgMgr32Unload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: DpxUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: SrUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CbsEsdUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: CbsEventUnregister
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: AppContainerUnload
2016-09-01 22:27:46, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2016-09-01 22:27:46, Info CBS Ending TiWorker finalization.

kruemelmonster
2016-09-02, 21:57:24
Probier mal
DISM /Online /Cleanup-Image /CheckHealth und anschließend
DISM /Online /Cleanup-Image /RestoreHealth

Voodoo6000
2016-09-03, 00:47:53
Danke für deine Antwort

Braucht man dafür Netz? Bei mir ist es jedenfalls ohne fehlgeschlagen.
DISM /Online /Cleanup-Image /CheckHealth
"Es wurde keine Komponentenbeschädigung erkannt"
DISM /Online /Cleanup-Image /RestoreHealth
Nach Stunden kam die Meldungen"Die Quelldatei konnte nicht heruntergeladen werden"

Davor hatte ich es noch mit "Diesen PC zurücksetzten" versucht aber auch dies ist fehlgeschlagen.

Gibt es noch weitere Ideen?

edit:
Nun habe ich Win10 neu installiert und es läuft wieder

Gast
2016-09-03, 08:03:50
Ja, dazu braucht man Netz. Man kann aber auch ein Offline-Abbild einbinden.
https://technet.microsoft.com/de-de/library/dd744382(v=ws.10).aspx
http://www.borncity.com/blog/2015/12/01/allesknner-das-windows-tool-dism-im-berblick/