Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall0x87D00607 (decimal -2016410105) means Content not found in Microsoft Configuration Manager. The client cannot find usable application content, obtain a valid distribution point (DP) location, or reach a DP that has the content.
This is normally a content-location or distribution problem—not an installation command-line or detection-rule problem. Fix the path from the application deployment to the client’s cache first, then investigate the installer only if the content downloads successfully.
What 0x87D00607 means
Microsoft defines 0x87D00607 as application content being unavailable to the client. The application may be deployed correctly while its deployment type content is missing from a distribution point, incompletely distributed, assigned to an unsuitable boundary group, or unreachable from the client.
Do not confuse it with these separate results:
| Code | Meaning | What to investigate |
|---|---|---|
| 0x87D00607 | Content not found | Content distribution, DP location, boundary groups, network access, and client content transfer |
| 0x87D00324 | Application was not detected after installation | Detection method and whether the installer completed |
| 0x87D00329 | Application requirement evaluation or detection failed | Requirements and detection configuration |
| 0x87D01201 | Insufficient cache or disk space | Client cache and free disk space |
| 0x87D01202 | Client cache is smaller than the requested content | Maximum cache size and content size |
The troubleshooting steps below apply to Configuration Manager current branch. Microsoft’s application-download technical reference was updated March 27, 2026, and its application-deployment troubleshooting reference was updated March 30, 2026.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
1. Confirm that the application content is distributed
Start at the site server. Do not change the install command or detection rule until you know that the deployment type’s content exists on a DP.
- Open the Configuration Manager console.
- Go to Monitoring and expand Distribution Status.
- Select Content Status.
- Select the application’s content.
- On the Home tab, select View Status.
- Review the distribution state, failed DPs, pending distributions, and compliance rate.
The content status must show that the relevant deployment type content is successfully distributed to a DP the client can use. Check every deployment type involved, including dependencies. A common failure is distributing the main application while a dependency’s new content remains absent from the DP.
Redistribute failed content
If the target DP appears under an error state:
- In Content Status, open the Error tab.
- In the Asset Details pane, right-click the failed distribution.
- Select Redistribute, then select Yes.
For a graphical view of the distribution path, state, DP type, and status messages, use View Content Distribution. This action is available starting with Configuration Manager version 2203.
Distribute missing content from the deployment wizard
If the content was never distributed:
- Go to Software Library → Application Management → Applications.
- Select the application and choose Deploy in the ribbon.
- On the Content page, select Add.
- Select the required distribution point or distribution point group and complete the wizard.
If dependencies are configured, the deployment wizard includes Automatically distribute content for dependencies on the General page. Enabling it distributes dependency content with the deployment. However, updating a dependent application later does not automatically distribute the dependency’s new revision, so verify dependency content after updates.
2. Check the client’s boundary and boundary group
For an intranet client, the client’s current network location must match a configured boundary. That boundary must belong to a boundary group that supplies usable site systems, including a DP containing the requested content.
Check the following in the console:
- Open Administration → Hierarchy Configuration → Boundaries.
- Confirm that the client’s IP subnet, IP address range, Active Directory site, IPv6 prefix, or VPN location matches a boundary.
- Open Boundary Groups and confirm that the boundary is associated with the expected group.
- On the boundary group’s references, confirm that a suitable DP is associated with the group.
- Confirm that the application content is distributed to that DP.
VPN boundaries are supported beginning with Configuration Manager version 2006. A laptop connected through a VPN may therefore need a VPN boundary rather than the office LAN’s IP range.
Overlapping boundaries can produce confusing results. If a client matches multiple boundary groups, Configuration Manager returns site systems from all matching groups; it does not apply a deterministic precedence order among those groups. For a content request, only DPs containing the requested content are included.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
Do not look for an old generic “enable boundary group” switch in DP properties. The current model is to associate DPs with boundary groups and define relationships between boundary groups.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems3. Understand which content source the client should use
Configuration Manager evaluates content sources in this order:
- DP on the same computer
- Peer source on the same subnet
- DP on the same subnet
- Peer source in the current boundary group
- DP in the current boundary group
- DP in a configured neighbor boundary group
- DP in the default site boundary group
- Windows Update cloud service
- Internet-facing DP
- Content-enabled cloud management gateway
Neighbor-boundary fallback is not automatic merely because two boundary groups exist. The current boundary group needs a defined relationship with the neighbor group, including a fallback time.
If the deployment type is allowed to use a neighbor or default-site DP, open the deployment type’s properties and select the Content tab. In the section for a DP from a neighbor boundary group or the default site boundary group, set Deployment options to Download content from distribution point and run locally. The default is Do not download content.
“Preferred distribution points” and the old “fast” and “slow” DP classifications are outdated terminology for current-branch content location. The old Allow fallback source locations for content settings are no longer available or enforced.
4. Read the client logs in the right order
On the affected client, use a ConfigMgr log viewer such as CMTrace and search for the application’s Content Unique ID. The important logs are normally in C:\Windows\CCM\Logs.
| Log | Purpose | What to look for |
|---|---|---|
| LocationServices.log | Obtains DP locations | Boundary-group results, content location requests, and whether a DP is returned |
| CAS.log | Content Access | Content lookup, cache handling, and content-location processing |
| ContentTransferManager.log | Persists the location and creates the transfer | Persisted location, CTM and DTS job IDs, or Received empty location update |
| DataTransferService.log | Performs the transfer | BITS job creation, transfer errors, authentication, and connection failures |
| AppEnforce.log | Application enforcement | Whether enforcement started and what happened after content became available |
A useful diagnostic sequence is:
- In LocationServices.log, determine whether the client receives a DP for the content ID.
- In ContentTransferManager.log, find the persisted location. If it says Received empty location update, the client has no usable DP location and may remain at 0%.
- Find the CTM and Data Transfer Service job IDs.
- Follow those IDs in DataTransferService.log to determine whether BITS can download the content.
- Only after a successful download, use AppEnforce.log to troubleshoot installation execution.
If LocationServices.log contains no Distribution Point= entry, inspect boundary membership, boundary-group DP references, content status, and fallback relationships before editing the application command line.
Rank #3
- Capacity Display Variance: 500GB external ssd often appears as around 465GB on Windows. MacOS can show full 500 GB capacity. This is binary calculation difference and doesn’t affect SSD hard drive actual physical storage
- 1050 MB/s Speed: Instantly access to your files with blazing-fast 10Gbps external SSD read up to 1050MB/s and write up to 1000MB/s. LED Light indicates USB SSD instant activity
- Data Security: Solid state drives S.M.A.R.T. health diagnostics and adaptive TRIM optimizing data block management ensures consistent write speeds and extends the longevity of the portable SSD
- USB-C & USB-A Cable: Both cables featuring rapid USB 3.2 Gen2, this USB SSD effortlessly bridges devices, enabling seamless cross-platform file transfers and backup between computers, smartphones, tablets and iPhone
- Always Fast: No slowdowns for large file transfers. With SLC caching (25% of current available capacity allocated as high-speed cache), this external SSD delivers steady 10Gbps for transfers within the cache capacity
5. Refresh machine or user policy
A newly distributed application or changed boundary assignment is not necessarily visible to the client immediately. The default client policy polling interval is 60 minutes.
From the Configuration Manager console
- Go to Assets and Compliance → Devices.
- Select the affected device.
- On the Home tab, in the Device group, select Client Notification → Download Computer Policy.
From the client
- Open the Configuration Manager Control Panel applet.
- Open the Actions tab.
- Select Machine Policy Retrieval & Evaluation Cycle.
- Select Run Now, then OK.
For a user-targeted deployment, also run User Policy Retrieval & Evaluation Cycle.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The documented WMI trigger for machine-policy retrieval is:
$trigger = “{00000000-0000-0000-0000-000000000021}”
Invoke-WmiMethod -Namespace root\ccm -Class sms_client -Name TriggerSchedule $trigger
Reducing the policy interval can make deployments appear faster, but it also increases site load. Refresh policy manually while troubleshooting rather than changing the interval globally unless there is an operational reason.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →6. Check cache and disk-space edge cases
Cache errors have different error codes, but cache conditions can still complicate content troubleshooting. The client stores temporary application-installation files in its cache.
Rank #4
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Review the client setting under Administration → Client Settings → the applicable policy → Client Cache Settings. If Configure client cache size is set to No, the default cache size is 5,120 MB. If it is set to Yes, the effective limit is whichever is smaller: Maximum cache size (MB) or Maximum cache size (percentage of disk).
The default Minimum duration before cached content can be removed is 1,440 minutes, or 24 hours. The maximum is 10,080 minutes, or one week. Do not manually delete the cache during an active deployment unless you understand the effect on the transfer and enforcement state.
If the logs show 0x87D01201 or 0x87D01202, increase the cache limit or free disk space as appropriate. Those codes do not explain a genuine 0x87D00607 location failure.
7. Test the installer only after content downloads
If the client receives the content and the download completes, but installation still fails, then test the deployment type’s command line separately. Configuration Manager runs application installs in the Local System context, so a command that works for an administrator may fail for the client.
- Download PsExec from Microsoft Sysinternals.
- Open an administrative Command Prompt and change to the directory containing PsExec.exe.
- Start a Local System command prompt with: psexec -accepteula -s -i cmd
- In the new window, run whoami to confirm the context.
- Change to the local directory containing the application content.
- Run the exact deployment-type command. For example: msiexec /i “My App.msi” /q
Missing files, incorrect quoting, mapped-drive dependencies, user-profile paths, and permissions commonly appear in this test. A bad executable or command line is a separate problem and is associated with 0x87D01106, not 0x87D00607.
8. A practical diagnosis order
- Record the application, deployment type, content unique ID, client name, and exact error.
- Check Monitoring → Distribution Status → Content Status.
- Verify the content exists on a DP the client should use, including dependencies.
- Verify the client’s boundary and boundary-group membership.
- Verify the boundary group has a suitable DP association and any required neighbor fallback relationship.
- Refresh machine or user policy.
- Read LocationServices.log, CAS.log, and ContentTransferManager.log using the content ID.
- Follow the transfer in DataTransferService.log.
- Check cache and disk space if the logs show a cache-related code.
- Test the installer in Local System only after content is available locally.
This order prevents a common waste of time: changing detection rules or silently modifying the install command when the client has never received the application files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common mistakes to avoid
- Treating 0x87D00607 as detection failure: detection has separate error codes.
- Checking only the application object: the deployment type’s content and dependencies also need distribution.
- Assuming a DP is usable because it exists: it must be returned for the client’s boundary group and contain the requested content.
- Assuming neighboring boundary groups provide automatic fallback: a relationship and fallback time must be configured.
- Using the old Application Catalog instructions: the old Application Catalog and previous Software Center are unsupported. Current clients use the new Software Center, enabled by default.
- Relying on “preferred DP” or “fast/slow” terminology: those concepts do not describe current-branch content-location behavior.
For additional reference, see Microsoft’s application install error reference, application download technical reference, application deployment troubleshooting guide, and documentation for boundaries and boundary groups.
Best Value
- MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to back up any endeavor; Build your video editing empire, file your photographs or back up your blogs all in an instant
- SHARE IDEAS IN A FLASH: Don’t waste a second waiting and spend more time doing; The T7 is embedded with PCIe NVMe technology that brings fast read and write speeds up to 1,050/1,000 MB/s¹, making it almost twice as fast as the T5
- ALWAYS MAKE THE SAVE: Compact design with massive capacity; With capacities up to 4TB, save exactly what you need to your drive – from large working files to game data and everything in between
- ADAPTS TO EVERY NEED: Whether using a PC or mobile phone, count on the T7 for extensive compatibility²; It’s a true team player when it comes to heavy-duty application usage or file-saving
- HI RESOLUTION VIDEO RECORDING: Record Ultra High Resolution (4K 60fs) videos directly onto the T7 Portable SSD with your favorite camera or mobile devices; Supports iPhone 15 Pro Res 4K at 60fps video and more³
FAQ
What does SCCM error 0x87D00607 mean?
It means “Content not found.” The Configuration Manager client cannot obtain usable content for the application from a distribution point. Check content distribution, boundary groups, DP accessibility, and the client’s content-location logs.
Is 0x87D00607 caused by a bad detection rule?
Usually no. Detection failures use separate codes, including 0x87D00324 and 0x87D00329. Check whether the client received and downloaded the content before changing detection settings.
Why does the application stay at 0%?
The client may have received an empty content-location reply. Check LocationServices.log and ContentTransferManager.log for missing DP entries or “Received empty location update.”
How do I redistribute an application in SCCM?
Open Monitoring → Distribution Status → Content Status, select the content, open the Error tab, right-click the failed distribution in Asset Details, choose Redistribute, and confirm.
Recommended Free Tools
What should I check if the DP is in a neighboring boundary group?
Confirm that the client’s current boundary group has a defined relationship with the neighbor group and a fallback time. Also check the deployment type’s Content tab and, when appropriate, choose “Download content from distribution point and run locally.”
Can a full cache cause 0x87D00607?
Cache problems generally use different codes: 0x87D01201 indicates insufficient cache or disk space, while 0x87D01202 indicates that the total cache is smaller than the requested content. Check cache settings and disk space, but do not use those codes as an explanation for a missing DP location.
The Bottom Line
0x87D00607 is a content-access failure. Verify that the deployment type and dependencies are distributed, confirm that the client belongs to the correct boundary group, check that the group returns a DP containing the content, and follow the request through LocationServices.log, CAS.log, ContentTransferManager.log, and DataTransferService.log. Only troubleshoot the installer command or detection method after the content has successfully reached the client.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →
