Windows 10: Windows 10 to "anniversary" update FAILS... no message... no clue

Strangely, I cannot get one of the KB updates to install... KB3172983. It's a cab file.

I used quotes around the packagepath parameter, just as I did with others... throws an Error: 2. An error occurred trying to open C:\downloads\KB3172983.cab ERROR: 0x80070002." "The system cannot find the file specified."

Apparently in the CBS log, it says it can't find the manifest file in the CAB file.

2016-09-11 13:46:46, Info CBS Failed to extract file update.mum from cabinet \\?\C:\downloads\KB3172983.cab [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-11 13:46:46, Info CBS Failed to extract package manifest from cabinet [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-11 13:46:46, Info CBS Failed to initialize internal package [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-11 13:46:46, Error CBS Failed to create internal package [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-11 13:46:46, Info CBS Failed to CreatePackage using worker session [HRESULT = 0x80070002]
2016-09-11 13:46:46, Info CBS Failed to create internal CBS package [HRESULT = 0x80070002]
2016-09-11 13:48:11, Info CBS Session: 30542932_2848495309 initialized by client DISM Package Manager Provider, external

I searched the CAB file... no such file inside. Thanks, Microsoft. How is this CAB supposed to be installed without a manifest?? I checked the other CAB files and "update.mum" is inside.

 

Thank you for trying to help, Steve. But I looked around those files and it's way too technical and cryptic for me to understand...
Example:

2016-09-11 10:00:08, Error CONX Windows::Compat::Appraiser::AssetUtils::GetProgramNameAndRegistryPathFromFile (724): App should have registry path, swallowing error.[gle=0x8007139f]
2016-09-11 10:00:08, Error CONX Windows::Compat::Appraiser:*BiggrinataMigrationOutputter:ullAssetInfoOrDefaults (444): Failed to get program name or arp registry path from application asset: [0x80004005].[gle=0x80004005]
2016-09-11 10:00:08, Error CONX Windows::Compat::Appraiser:*BiggrinataMigrationOutputter:*BiggrinoOutput (213): Failed to pull asset info for file: [0x80004005].[gle=0x80004005]
2016-09-11 10:19:50, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2016-09-11 10:20:45, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: "id" attribute is mandatory. void __cdecl Mig::CMXEMigrationXml::LoadSupportedComponent(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2016-09-11 10:21:54, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #93871# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216 (0x00060000), status = [6]"(null)", value = { type: 40972 (0x0000a00c), bytes ( 12 (0x0000000c) ): 65006e002d00550053000000 })
[gle=0x80004005]
2016-09-11 10:23:22, Error CSI 00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #172345# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216 (0x00060000), status = [6]"(null)", value = { type: 40972 (0x0000a00c), bytes ( 12 (0x0000000c) ): 65006e002d00550053000000 })
[gle=0x80004005]
2016-09-11 10:24:00, 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 *)

 

I suggest you post the error files. I found the trick is to search for "error" towards the end of the file around the time when the installation failed.

 

I did just that. Searched for "ERROR". I don't see anything meaningful. I cannot post the whole log files. Some are just way too large...

Can you tell me what specifically I should look for?

What really concerns me is that this Microsoft MVP support rep has this set of KB files that he says should be installed. I've gotten all of them installed except for one, which is KB3172983. I downloaded the "stand alone" install file from the Microsoft Update Catalog. But there's no manifest inside the CAB file... so it won't install. And there's no "setup.exe" file in it as well. There are two EXE files, but attempting to run them throws errors.

 

I searched for errors around the timeframe of the installation failing. The hard stop was about 11:18am. No ERROR thrown around that time. Only thing I could find prior was this:

2016-09-11 10:43:39, Info CBS Universal Time is: 2016-09-11 18:43:39.417
2016-09-11 10:43:39, Info CBS Failed to find a matching version for servicing stack: C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2016-09-11 10:43:39, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2016-09-11 10:43:39, Info CBS Offline servicing, using stack version from: C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb\cbscore.dll
2016-09-11 10:43:39, Info CBS Loaded Servicing Stack v10.0.14393.0 with Core: C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ecb\cbscore.dll
2016-09-11 10:43:39, Info CBS Setting core mode: CbsCoreModeOffline
2016-09-11 10:43:39, Info CSI 00000001@2016/9/11:18:43:39.558 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff873766c49 @0x7ff873b855bb @0x7ff873b86372 @0x7ff873de21fa @0x7ff873de2b9a @0x7ff873d9fbf8)
2016-09-11 10:43:39, Info DISM DISM Package Manager: PID=1004 TID=420 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-09-11 10:43:39, Info CBS Offline image is writable
2016-09-11 10:43:39, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SOFTWARE' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SOFTWARE'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SYSTEM' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SYSTEM'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SECURITY' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SECURITY'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SAM' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SAM'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/COMPONENTS' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\COMPONENTS'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DRIVERS' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\DRIVERS'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DEFAULT' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\DEFAULT'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Users/Default/ntuser.dat' from path '\\?\C:\$WINDOWS.~BT\NewOS\Users\Default\ntuser.dat'.
2016-09-11 10:43:39, Info CBS Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/system32/smi/store/Machine/schema.dat' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\system32\smi\store\Machine\schema.dat'.
2016-09-11 10:43:39, Info CSI 00000002 CSI Store 1677576337504 initialized
2016-09-11 10:43:39, Info CBS Session: 1004_581734 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2016-09-11 10:43:39, Info DISM DISM Package Manager: PID=1004 TID=420 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-09-11 10:43:39, Info DISM DISM Package Manager: PID=1004 TID=420 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock


2016-09-11 11:06:03, Info CBS Cannot read value for the force canceled current transaction. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2016-09-11 11:06:03, Info CBS CBS force canceled transaction status datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2016-09-11 11:06:03, Info CBS The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-11 11:06:03, Info CBS Unable to gather perf datapoints because there are no active sessions.
2016-09-11 11:06:03, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.



Other log files mentioned in that MSDN article weren't updated on 9/11, so they're not applicable. Mind you, I did run SFC /SCANNOW, to verify integrity... and it passed.

A FEW NOTES:

* When I installed, I opted NOT to do any updates. Just to install from the ISO. I read in numerous places that this is safer.
* I did not think to disconnect my Internet connection while this was running. Based on the "CBS Failed to find servicing stack directory in online store" error message, looked like it couldn't find something. But the messages that followed suggest that the installer process found what it needed offline... does that appear to be the case?

 

Your earlier post had some 0x80004005 errors which I had and solved by this method https://www.tenforums.com/installatio...x80004005.html

This is probably a long shot but from an admin command prompt run bcdedit /export c:\temp\export (or another folder/file of your choice).If the command fails you may have the problem I had, else its something else.

 

Hi Steve, I ran this command and it completed successfully. Couldn't read the LOG file, because it's a binary. I ran the other bcdedit commands and everything seems fine.

My main concern right now is this KB3172983 update. I have a feeling I need it in order to complete the Windows 10 anniversary update, but it is not installed and I cannot get it installed with the standalone method. Windows doesn't seem to recognize that it's needed, as automatic update is not installing it.

 

OK... I tried a few more options, and nothing worked.

So, using my old SQA logic, I used a software tool to download a very specific Windows 10 ISO file. I went back to Threshold 1, build 10240. This was the first "RTM" for Windows 10. I was able to run the install and it went all the way through to completion. No problems. That was a relief.

My next question is... should I allow Windows Update to do its think automatically here? Or would it be better to jump right to the install of ISO 1607 (anniversary)? I'm just wondering if what broke my ability to automatically update was some independent update performed by Windows, somewhere after I'd upgraded to Windows 10.

 

First of all make a full system backup of your current OS - most people on this forum use the excellent free Macrium Reflect backup software. Then you can always go back to the working build 10240.

In theory, you should end up with the same OS version whichever OS upgrade route you use. I used the ISO method, You just right click on the ISO file on your drive, right click to mount then run setup.exe (from an admin account). See https://www.tenforums.com/tutorials/9...-download.html

Be careful to select the right ISO version - e.g. for the UK you need English (International)

 

Hi Steve, after all of the behind-the-scenes updates finish (Windows 10 started them automatically and I can't stop the process), I'll then do a backup. Is Macrium Reflect still preferred over the built-in system backup feature in Windows? I had looked it over and it seems to be pretty comprehensive. You'd think that Microsoft would do the best job of backing up its own product.... but I imagine Reflect provides more features.

I'm wondering if the problem with applying the 1607 update is going directly from 10240... Maybe I should download the Threshold 2 release and apply that first? And yes, I am making sure I have the right bits (x64) and right language to match my current install.

 

1. MRF is far superior. MS have not developed their own tool for years.

2. Use the iso to upgrade - by far the most reliable way to do it. No need to install 10586.

 

I agree with cereberus above. Apart from backing up the current build 10240, I also recommend backing the new installation (Anniversary Upgrade) as soon as Windows has completed the installation & updates. You will then have these builds to fall back on if something goes wrong with further work on the installation.

 

Thanks, guys -- much appreciated. I will use Macrium Reflect now that 10240 updates have settled in.

Part of me thinks I should just wait for Microsoft to finish shaking out all of the installation quirks of the anniversary update before trying again... but I also hate leaving that hanging. Don't want further updates to keep attempting, although I think after doing the full reinstall of 10240, it'll likely wait 30 days before bugging me about the anniversary. Should I hold off? I don't know much about 1607, if there's anything really noteworthy it delivers other than assorted defect fixes.

 

Nah - people only post when they get issues so it is easy to get a jaundiced view. Just look historically at the number of posts about issues when the 10586 upgrade came out. In reality, there have been significantly a lot less post about issues upgrading from 10586 to 14393 than there was from 10240 to 10586.

1607 is vastly superior to 10240. Many new features and reliability fixes.

Best plan as with any upgrade is to make an image backup first, so you can easily revert if things go pearshape.

 

Well, I had deja-vu all over again. Exact same error as I got earlier.





Completely authentic Microsoft sourced Threshold 1 build 10240 ISO... installed just fine, no errors. But trying to upgrade directly to 1607 throws this error. I'm stumped...

Should I try applying the 10586 ISO next, to see if I can upgrade from that?