If you want to upgrade your system to Windows 10, but it does not work fine and you have an error code 00000A58, this article will help you to fix this problem.
As you might remember, the sequence of tasks for in-place upgrade will appear only in the new version of SCCM vNext, but right now System Center Configuration Manager Team rolled out the scripts and made the task sequence for migrating from Windows 7/8/8.1 to Windows 10. You can read about it here: https://blogs.technet.microsoft.com/configmgrteam/2015/06/16/revised-content-for-the-windows-10-in-place-upgrade-via-task-sequence-for-configuration-manager/
There is nothing complicated about it. It is important to use an original image from your MVLSC. Just import a task sequence from the archive, deliver to distribution points, deploy to the collection and enjoy the result.
But the story is not about that. When you start the update, you have encountered an error like this:
Failed to run the action: Recover from Setup Failure. Unknown error (Error: 00000A58; Source: Unknown)
Failed to run the last action: Recover from Setup Failure. Execution of task sequence failed. Unknown error (Error: 00000A58; Source: Unknown)
There is the same error described in the ConfigMgr Team blog comments section, but nobody there knows how to fix it.
So in our case we have to open smsts.log (this log can be found in WindowsCCMlogs).
Hash could not be matched for the downloaded content. Original ContentHash =
DownloadContentAndVerifyHash() failed. 80091007.
DownloadContentAndVerifyHash ( pszPackageID, L»SMSPackage», saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L»», 0, dwPackageFlags, mapNetworkAccess ), HRESULT=80091007
DownloadContentLocally (pszSource, sSourceDirectory, dwFlags, hUserToken, mapNetworkAccess), HRESULT=80091007
Failed to resolve the source for SMS PKGID=ASD000FA, hr=0x80091007
Install Software failed to run command line, hr=0x80091007
Process completed with exit code 2148077575
In the Monitoring –> Content Status section you can see a package with PKGID=ASD000FA log and 100% status, but you can see that there is a problem with package size.
Now you should go back to Software Library –> Packages and open up Windows vNext Upgrade Media properties. Check mark on Copy the content in this package to a package share on distribution points. Wait until the package will arrive at the distribution point.
Now run the sequence of tasks for migration on the client side. As you can see, it’s easy to upgrade from Windows 8.1 to Windows 10.
In-place Upgrade restrictions
If you are using key /Auto:Upgrade for migration from Windows 7/8/8.1 to Windows 10 (including applications, user files, system configuration), you can’t:
- use custom images;
- change the architecture;
- change system language;
- switch from BIOS to UEFI;
- edit the disk partitions;
- downgrade edition (from Enterprise to Professional, for example).
In all other cases (Wipe-and-Load) you can use the usual way using Configuration Manager, MDT or USMT.