Monthly Archives: April 2017

Debian apt-get update failing to reach internet sources “W: Failed to fetch”

The Scenario

I have a Debian Jessie 8.3 server on the company network that requires updates/patches installing for the first time. The server is configured to use online sources rather than the ISO/DVD.

The Problem

Every time I run “apt-get update” I get source connection errors “W: Failed to fetch…”

The Solution

My problem was the proxy – I had not yet defined the proxy settings the server should use.

  • vi /etc/apt/apt.conf – create this file if needed
  • Type the following (altering for your specific proxy settings of course):


  • Save the file (:wq!) and retry the “apt-get update” command which now worked, i.e the response was similar to “Hit jessie/main Sources..” and “Get:4 jessie/updates/main Sources [189 kB]”

Disclaimer: provided “AS IS” with no warranties and confer no rights


MBAM Event ID 2: Error code:0x80310052

The Scenario

I have amended the disk partition configuration on my computer, now I need to run the MBAM (Microsoft BitLocker Administration and Monitoring – the enterpise implementation of BitLocker) client in order to encrypt the C drive.

The Problem

The MBAM client launches OK and I can set a PIN, but when I click proceed with the encryption of my C drive it fails with the following error:


Reviewing the MBAM event logs (Event Viewer > Applications and Service Logs > Microsoft > Windows > MBAM > Admin logs). There is the following associated event:


Event ID: 2

Error Code: 0x80310052

Details: The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again.

The Solution

In my case this is a result of me changing the size of the system partitions, so Windows becomes confused about where it should store the BitLocker BDE files. To repair this complete the following:

  1. Open an elevated command prompt and type: bcdboot %systemdrive%\Windows (requires a reboot but do not do so yet).
  2. Open Explorer, Go to C:\Windows\System32\Recovery and rename REagent.xml to eg. REagent.old.xml.
  3. Reboot computer.
  4. Rerun MBAM client.



Disclaimer: provided “AS IS” with no warranties and confer no rights