Download failed for content under context System, error 0x80091007 . Package hash matching for the package failed. Workaround It turns out that the system file thumbs.db was causing this problem within these packages. Thumbs.db is a system file created by windows when browsing a folder in thumbnail view. If I remove this file from my packages source directory, and update my distribution points, the package installs first time without error. Please make sure you uncheck the option "Hide Protected System Files" while searching for the Thumbs.db .
Posts
ConfigMgr 2012 update scan fails with 8007000E and causes incorrect compliance status. Root Cause Because Configuration Manager does compliance reporting, it has extremely broad scan criteria to determine what is applicable. This is different from a typical scan performed by the Windows Update agent which requires a smaller subset of criteria. If an update is on WSUS and in a non-declined state, the Configuration Manager scan criteria will cause the Windows Update agent to try to evaluate it. Windows x86 clients have a much smaller addressable memory range than 64-bit clients. With enough updates, the data returned to Configuration Manager is large enough that RPC can’t allocate the shared section used to return the data. This is because overall memory usage of the svchost.exe process hosting the Windows Update Agent process is extremely high. The result is that there is either not enough memory available to satisfy the request or there is not a large enough contiguous bloc
SCCM client installation with Windows 10 Devices failing with 1603. Recently faced an issue with SCCM client installation with Windows 10 Devices with 1603. The scenario was the machines got migrated from Win 7 to Win 10 (in place/ task sequence) and the SCCM client evaluation was failing for those and appearing to be as inactive in the console. Even the 1606 client Hotfix installation was also failing on those. After a lot of r&d and troubleshooting. Workaround - The schedule task for Configuration Manager found to be causing this and we had to delete "HKEY_LOCAL_MACHINE\SOFTWA RE\Microsoft\Windows NT\CurrentVersion\Schedule \TaskCache\Tree\Microsoft\ Configuration Manager" from the registry for those affected systems . Once that entry got deleted , client installation / evaluation / reporting all were going on smoothly as expected.