Find out if your music will be turned down by YouTube, Spotify, TIDAL, Apple Music and more. Discover your music's Loudness Penalty score, for free.
Your file will not be uploaded, stored or shared, meaning this process is secure and anonymous.
We all hate sudden changes in loudness - they're the #1 source of user complaints.
To avoid this and save us from being "blasted" unexpectedly, online streaming services measure loudness, and turn down music recorded at higher levels. We call this reduction the "Loudness Penalty" - the higher the level your music is mastered at, the bigger the penalty could be. But all the streaming services achieve this in different ways, and give different values, which makes it really hard to know how big the Loudness Penalty will be for your music...
Until now.
Simply select any WAV, MP3 or AAC file above, and within seconds we'll provide you with an accurate measurement of the Loudness Penalty for your music on many of the most popular music streaming services, and allow you to preview how it will sound for easy comparison with your favorite reference material.
Your file will not be uploaded, meaning this process is secure and anonymous.
Do you have any questions? Get in touch.
Find out how to optimize your music for impactful, punchy playback (and maximum encode quality) for all the online streaming services. Plus, receive a Loudness Penalty Report for your file that explains in detail what all the numbers mean.
Analyze another fileThe most common triggers:
If the troubleshooter fails, manually resetting the update services and clearing the cache is often effective.
If none of the above works:
| Aspect | Detail |
|----------------------|--------|
| Error code | 0x800f0952 |
| Common feature | .NET Framework 3.5 installation |
| Main cause | Group Policy / WSUS blocking access to Windows Update |
| Quick fix | DISM with /Source or bypass WSUS via registry/GPO |
| Complexity | Moderate (requires admin rights) |
Bottom line: 0x800f0952 is rarely a hardware failure. In most cases, it’s a policy or servicing stack issue. The DISM workaround or GPO tweak resolves it in under 10 minutes.
The Windows error 0x800f0952 is a specific installation failure that typically occurs when the operating system is unable to download or install Features on Demand (FOD), such as language packs, handwriting recognition, or Remote Server Administration Tools (RSAT). It is often triggered by conflicts between local update settings and enterprise management tools like Windows Server Update Services (WSUS). The Architecture of the Error
At its core, 0x800f0952 signifies a "Source Not Found" or access-related conflict within the Windows Servicing Stack. When a user attempts to add an optional feature, the system checks its defined "update source." If the computer is managed by a corporate network, it may be programmed to look only at a local WSUS server. If that server does not host the specific feature files (like a Chinese language pack or specialized RSAT tools), the installation fails with this error code. Primary Causes
WSUS/SCCM Conflicts: Many managed environments block clients from reaching the public Microsoft Update servers, but forget to host the necessary Features on Demand locally.
Corrupted Servicing Store: If the local Component Store (WinSxS) is damaged, Windows cannot properly stage the new feature files.
Internet Connectivity/VPN: Attempting to install these features while on a restricted VPN can block the necessary handshakes with Microsoft's content delivery networks. Strategic Solutions
To resolve 0x800f0952, one must typically force Windows to bypass local management and talk directly to Microsoft’s servers for that specific task. Language pack installation fails with error 0x800F0954
The error code 0x800f0952 typically occurs when Windows fails to install a language pack or an optional feature (like Speech Recognition or OCR). It often indicates that the system cannot locate or download the necessary source files, frequently due to network restrictions or configuration issues with Windows Update services.
Below is a complete write-up on diagnosing and resolving this error. Common Causes 0x800f0952 install
WSUS Conflict: If your computer is managed by an organization, it may be trying to fetch files from a Windows Server Update Services (WSUS) server that doesn't have the language pack files.
Corrupted Update Components: Temporary files in the Windows Update cache may be preventing a clean download.
Network Restrictions: Metered connections or firewall settings might be blocking the download of large optional features. Resolution Steps
1. Bypass WSUS via Registry (Recommended for Corporate Devices)
This is the most common fix if your PC is part of a domain. It forces Windows to check Microsoft's servers directly instead of your local company server. Press Win + R, type regedit, and hit Enter.
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU Look for a value named UseWUServer in the right pane. Double-click it and change the Value data to 0.
Restart the Windows Update service (via services.msc) and try the installation again.
Note: Remember to change it back to 1 after the installation is complete to resume receiving company-managed updates. 2. Clear Windows Update Cache
If the installation files are stuck or corrupted, clearing the cache often helps. Open Command Prompt as Administrator. Stop the update services by typing: net stop wuauserv net stop bits
Navigate to C:\Windows\SoftwareDistribution\Download and delete all files inside. Restart the services: net start wuauserv net start bits Retry the language pack installation. 3. Run DISM and SFC Scans
Repair underlying system file corruption that might be blocking the "servicing stack". Open Command Prompt (Admin).
Type DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish. Type sfc /scannow and press Enter. 4. Check Metered Connection Settings The most common triggers: If the troubleshooter fails,
Windows may block optional feature downloads on connections it thinks are limited. Go to Settings > Network & Internet. Select your active connection (Wi-Fi or Ethernet). Ensure Set as metered connection is turned Off. Alternative Method: PowerShell Installation
If the GUI fails, you can try forcing the installation via PowerShell (Admin): powershell
# Replace 'en-US' with your target language tag Install-Language -Language en-US Use code with caution. Copied to clipboard
Are you attempting this on a personal laptop or a work-managed computer? This will help determine if a Group Policy is likely the culprit.
Technical Report: Windows Error Code 0x800f0952 Error 0x800f0952 is a Windows Update or Deployment Image Servicing and Management (DISM) error that typically occurs when the operating system fails to install an optional feature or a specific language pack. It translates to CBS_E_DPX_SETUP_FAILURE, indicating a failure during the file extraction or staging process. 1. Executive Summary
The error is most frequently encountered when users attempt to install Language Packs, RSAT (Remote Server Administration Tools), or .NET Framework 3.5. It signifies that Windows cannot find the necessary source files or that the installation process was interrupted by a network or permission issue. 2. Primary Causes
Missing Source Files: Windows Update cannot locate the payload for the feature you are trying to install.
WSUS Interference: In corporate environments, the system may be looking for the files on a local Windows Server Update Services (WSUS) server that doesn't host optional features.
Corrupt Component Store: Damage within the WinSxS folder prevents new features from being staged.
Network Restrictions: Firewalls or metered connections blocking the download of supplementary files from Microsoft servers. 3. Resolution Strategies A. Bypass WSUS via Registry (Common for Corporate PCs)
If your computer is managed by an organization, it often fails to find optional features because it only checks the local server. Open Registry Editor (regedit).
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU Find UseWUServer and change its value to 0. Bottom line: 0x800f0952 is rarely a hardware failure
Restart the Windows Update service and try the installation again.
Remember to change it back to 1 after the install to receive corporate updates. B. Use DISM with an Online Source
Force Windows to repair its component store and download the feature directly from Microsoft: Open Command Prompt as Administrator.
Run the following command:DISM /Online /Cleanup-Image /RestoreHealth
Once finished, attempt the feature installation again via Command Prompt:DISM /Online /Add-Capability /CapabilityName:Language.Basic~~~en-US~0.0.1.0 (Replace with your specific capability name). C. Enable "Download over Metered Connections" If you are trying to install a Language Pack: Go to Settings > Network & Internet. Select your active connection (Wi-Fi or Ethernet).
Ensure Set as metered connection is toggled OFF, or ensure Windows is allowed to download over metered connections in the Windows Update settings. D. Reset Windows Update Components
If the update agent is "stuck," resetting the folders can clear the error: Stop the wuauserv and bits services.
Rename the C:\Windows\SoftwareDistribution folder to SoftwareDistribution.old. Restart the services and retry the installation. 4. Recommendation
Start by checking if the device is managed by WSUS or Group Policy, as this is the cause of roughly 80% of 0x800f0952 errors. If the device is personal, the DISM RestoreHealth command is the most effective path to recovery.
Here are several short pieces of content about error 0x800f0952 during installation—pick any to use or tell me which style/length you want more of.
Want a longer article, social posts, or a formatted help doc (with commands and logs)? Which tone and length do you prefer?
