setuperr.log This is setuperr.log Code: 2016-05-16 09:22:53, Error Number of Enumerated Devices = 10[gle=0x00000103] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=ffffffffx[gle=0x00000003] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=ffffffffx[gle=0x00000003] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=00000002x[gle=0x80092004] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=ffffffffx[gle=0x00000003] 2016-05-16 09:22:54, Error Failed to find driver file path. Error=ffffffffx[gle=0x00000003] 2016-05-16 09:31:03, Error [0x0808fe] MIG Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys, bailing out 2016-05-16 09:46:34, Error CSI 00000009 (F) Manifest parsing failed: Status: STATUS_UNSUCCESSFUL Node: 879 (0x0000036f) Node (ln 218 col 1912) xpath: /#document/assembly/registryKeys/registryKey/registryValue/@operationHint Strings: ([ml:12,l12]"forceReplace")[gle=0x80004005] 2016-05-16 09:46:34, Error CSI 0000000a@2016/5/16:08:46:34.391 (F) d:\w7rtm\base\wcp\manifestparser\pcmc_manifestwalker.cpp(5009): Error STATUS_UNSUCCESSFUL originated in function CMicrodomManifestWalker::CommonReportError expression: (null) [gle=0x80004005] 2016-05-16 09:46:34, Error CSI 0000000b (F) Manifest unparsable. Component: [ml:280{140},l:200{100}]"amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8"[gle=0x80004005] 2016-05-16 09:46:34, Error CSI 0000000c@2016/5/16:08:46:34.438 (F) d:\w7rtm\base\wcp\componentstore\storelayout.cpp(3067): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifest expression: 0 FileHashMismatch on resource [127]"\winsxs\manifests\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.manifest"[gle=0x80004005] 2016-05-16 09:46:34, Error CSI 0000000d (F) HRESULT_FROM_WIN32(14098) #1971761# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80073712] 2016-05-16 09:46:34, Error CSI 0000000e (F) HRESULT_FROM_WIN32(14098) #1971759# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_Analyze(Flags = 1, riid = {f4d9decb-0250-4ad4-9500-85c7f2f281ec}, ppUnk = NULL, disp = 0)[gle=0x80073712] 2016-05-16 09:46:34, Error CBS Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 2016-05-16 09:46:34, Error CBS Failed to perform operation. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 2016-05-16 09:46:34, Error [0x080a82] MIG CCbsContext::Release, ICbsSession::Finalize failed 80073712.
Offline upgrading, which set editions does, can only be done when all installed updates have state "installed". When one integated update has state "install pending" set editions would not work. After offline integrating the updates they will have state "install pending" that's why i have to install the windows image first, after installing they have state "installed" so it's possible to use set edition to the basic/starter win images Offtopic: Only 10.10586 and up, the offline integrated updates will get the state "installed" as long as you didn't offline enabled dotnet35 before integrating the other updates, on the image, that one will always get state "install pending" and all updates after it also will.
I understand the pending status stuff but then why my AIO has all desired editions already set? And why all of them can be installed flawlessly from scratch? Good to know this.
lol for me it is not I've googled for one hour and fast read some hits. I still can't see how to solve this problem and whether it's related to what Enthousiast said about "pending status".
What I learned from this: It's that a wrong registry value caused a similar issue to mine. OP fixed the value manually on his existing Windows 7 installation. However in my case it's an in-place upgrade. I am not an expert to solve this type of problems so I don't know how to change the value with a script or something during installation...
First you'd check if you have the servicing stack update prerequisite installed at all. The registry could be changed on an offline image as well, but messing with the update process this way may not actually be the "right" thing to do.
A hundred thanks to you! Tomorrow I'm going to experiment and run tests and come back with feedback. Meantime it's time to go to bed. Good night mate.
You can't (or not recommended) to offline upgrade same image multible times so after each upgrade operation, you append the image, unmount it, then remount it and start another edition upgrade Code: imagex /mountrw install.wim 1 c:\mount DISM /Image:c:\mount /Set-Edition:HomePremium imagex /commit /append c:\mount HomePremium imagex /unmount c:\mount imagex /mountrw install.wim 1 c:\mount DISM /Image:c:\mount /Set-Edition:Professional imagex /commit /append c:\mount Professional imagex /unmount c:\mount imagex /mountrw install.wim 1 c:\mount DISM /Image:c:\mount /Set-Edition:Ultimate imagex /commit /append c:\mount Ultimate imagex /unmount c:\mount
Confirmed. I offline integrated latest Simplix Pack to Ultimate index into an untouched iso, then grabbed that same install.wim and put it in the USB stick and same issue when doing in-place upgrade or reinstall within Windows 7. So the way I set my editions has nothing to do with that problem and as @100 pointed out on previous posts, it's a matter of a bad M$ servicing stack update. I really wonder why I am the only one who has noticed this issue on these forums. Does anybody in here make in-place upgrade or reinstall Windows without format? Am I alone and no one was aware?
Ok, I must admit you have the reason on this one too. I did the same steps and the parsing issue was gone. Damn M$! What a pita!