-
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 .

Comments

Post a Comment

Popular posts from this blog

SCCM: Determining installed applications last use time_ SQL Query.

-
ConfigMgr will definitely be able to let SCCM admins know what are installed in the environment regardless if it is a server or workstation. SCCM by default comes with a set of reports that SCCM admins can utilize to gather information. The one that I am going to mention today is , "Computers that has a metered program but have not run the program since a specific date". What is so special about this report you may think, I had the same thinking as you but it is pretty interesting to know how is this data derived. The data set for this is based on Software Inventory and this means gathering file types that are on machines. The last used time is gathered asp art of software metering. This report will provide the information based on the files inventoried and their respective last used date. Nothing unique right? Here comes the interesting part, picture the scenario as below. All of us will know that in order for Microsoft Office to be used, it has to be inst...
Read more

Unable to read existing WUA Group Policy object. Error = 0x80004005.

-
Image
Wanted to share.. It will be helpful to achieve maximum rate of patching compliance. As we often face issues to troubleshoot the systems with  "Enforcement Status Unknown" state. Issue Some of the servers / workstations are appearing as “ Enforcement Status Unknown ” in Patching Deployment Report. Logs mentioned below. Unable to find or read WUA Managed server policy. Unable to read existing WUA Group Policy object. Error = 0x80004005. Failed to Add Update Source for WUAgent of type (2) and id ({6219E813-D37D-4D15-ADA7-3E4DADF55C9E}). Error = 0x80004005. Resolution Issue appears to be with corrupt policy info locally on the machine.  Please go to c:\windows\system32\grouppolicy\machine and delete the registry.pol  file.  Run GPUpdate /force command after that .
Read more

Configmgr OnSearchComplete – Failed to end search job Error 0x80244022 WUAHandler.log

-
WSUS POOL in IIS getting stopped frequently, causing scan  failures from client end     So why does the WSUS App pool crash and how to fix it? The WSUS App pool “private memory limit” setting is by default configured to 1.7 GB, the pool crashed because it couldn’t keep up. In order to fix that, people increase the memory on the Software Update Point and also configure the WSUS App pool memory limit with 8-12 GB. After that App pool should be started and let the clients flood the network for a couple of hours and everything was back to normal. So why couldn’t the WSUS App pool keep up? This is due to the larger number of updates in the catalog which continues to grow over time.  After the Patch Tuesday sync from Microsoft, clients started scanning successfully at first, but the Update catalog reached a size that increased the load on the Software Update Point. Due to the default memory limit of the app pool the server ran out of memory caus...
Read more