How to fix E: Malformed line in preferences file /etc/apt/preferences in APT

APTINTERMEDIATEMEDIUMUpdated Dec 29, 2025· 132 views

This error occurs when APT encounters invalid syntax in the /etc/apt/preferences file. The preferences file must follow strict formatting rules with required Package, Pin, and Pin-Priority headers separated by blank lines.

Quick fix

Fixes APT_PREFS_MALFORMED

sudo nano /etc/apt/preferences
  1. Check the /etc/apt/preferences file syntax
  2. Fix common syntax errors
  3. Validate the file format
  4. Test the preferences file
apt — error
sudo nano /etc/apt/preferences
E: Malformed line in preferences file /etc/apt/preferences

What this error means

The /etc/apt/preferences file controls package pinning and version prioritization in Debian-based systems. APT parses this file to determine which package versions to prefer during installation and upgrades. When APT detects a line that doesn't conform to the required format—such as missing required headers, incorrect field names, or malformed entries—it reports this error and refuses to continue. Common issues include using 'Priority:' instead of 'Pin-Priority:', using '#' for comments instead of the 'Explanation:' field, leaving the file empty except for comments, or mixing in unrecognized configuration syntax.

Typical symptoms

  • apt update, apt upgrade, or apt install commands fail with the error message
  • System cannot perform package management operations
  • Error message includes the line number or specific malformed content
  • Previously working package management suddenly stops working after editing /etc/apt/preferences
  • apt-cache policy command may also fail to parse preferences

Common causes

  1. Using 'Priority:' field instead of 'Pin-Priority:' in a preferences record
  2. Using '#' for comments instead of the 'Explanation:' field
  3. Missing required 'Package:' header in a preferences block
  4. Missing 'Pin:' or 'Pin-Priority:' fields in a preferences record
  5. Incorrect blank line separation between multiple preference records
  6. File contains only comments or is empty, which is not permitted
  7. Whitespace or indentation issues in field definitions
  8. Typos in field names (e.g., 'Packge:' instead of 'Package:')

How to fix "E: Malformed line in preferences file /etc/apt/preferences"

1Check the /etc/apt/preferences file syntax

Open the file and review its contents carefully:

bash
sudo nano /etc/apt/preferences

Ensure the file follows the required structure:
- Each record starts with 'Package: <package-name>' or 'Package: *'
- Followed by 'Pin: <pin-specification>'
- Followed by 'Pin-Priority: <priority-number>'
- Multiple records are separated by blank lines
- No other content should appear between these fields

2Fix common syntax errors

Correct these frequent mistakes:

Incorrect Priority field:

bash
# WRONG
Priority: 900

# CORRECT
Pin-Priority: 900

Using # for comments:

bash
# WRONG
# This is a comment

# CORRECT
Explanation: This is a comment

Missing Package header:

bash
# WRONG
Pin: release a=stable
Pin-Priority: 700

# CORRECT
Package: *
Pin: release a=stable
Pin-Priority: 700
3Validate the file format

A valid preferences file should look like:

bash
Package: nginx
Pin: release a=stable
Pin-Priority: 900

Package: *
Pin: release a=testing
Pin-Priority: 700

Key points:
- Each record starts on a new line with 'Package:'
- All three fields (Package, Pin, Pin-Priority) are required
- Records are separated by exactly one blank line
- No spaces or special formatting between lines

4Test the preferences file

After fixing syntax errors, test the file with:

bash
sudo apt-cache policy

If the error persists, check for hidden characters or whitespace issues:

bash
cat -A /etc/apt/preferences

This shows all special characters, including tabs and carriage returns that might cause parsing issues.

5Remove the file if necessary

If the file is not needed or corruption is severe, remove it entirely:

bash
sudo rm /etc/apt/preferences

Then verify package management works:

bash
sudo apt update

You can also check /etc/apt/preferences.d/ directory for additional preference files:

bash
ls -la /etc/apt/preferences.d/

Fix or remove any corrupted files in that directory as well.

Advanced notes

The /etc/apt/preferences file uses a strict record-based format. Each record must be complete with all required fields. APT also supports a preferences.d directory (/etc/apt/preferences.d/) where you can place multiple preference files with .pref extension. These files are processed in alphanumeric order.

For pin specifications, use 'apt-cache policy <package>' to verify that your pinning rules are correctly applied. The output shows the available versions and their priorities.

When dealing with distribution-based pins, use 'apt-cache policy' output to identify the correct release attribute names (release codenames like 'focal', 'jammy', 'bookworm', or archive names like 'stable', 'testing').

Note that APT reads these files sequentially, so more specific package entries should come before general wildcard entries to ensure proper precedence.

Frequently asked questions

What does "APT_PREFS_MALFORMED" mean?
The /etc/apt/preferences file controls package pinning and version prioritization in Debian-based systems. APT parses this file to determine which package versions to prefer during installation and upgrades. When APT detects a line that doesn't conform to the required format—such as missing required headers, incorrect field names, or malformed entries—it reports this error and refuses to continue.
How do I fix "APT_PREFS_MALFORMED"?
This error occurs when APT encounters invalid syntax in the /etc/apt/preferences file. The preferences file must follow strict formatting rules with required Package, Pin, and Pin-Priority headers separated by blank lines.
What causes "APT_PREFS_MALFORMED"?
Using 'Priority:' field instead of 'Pin-Priority:' in a preferences record Using '#' for comments instead of the 'Explanation:' field Missing required 'Package:' header in a preferences block
Is the "APT_PREFS_MALFORMED" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading