Multiple errors in Event Viewer: EventID 131 from DeviceSetupManager since September 12, 2014

I have found that it's caused by blocking windows from checking for drivers on the windows update site 

Access to drivers on Windows Update was blocked by policy

I have 256 event ID: 131's in the last 7 days and that ^^^ msg is for all of them 

It happens because I don't want MS messing with my device drivers like replacing the new AMD Catalyst driver 15.11.1 with an older version  which it quite happily does if left unchecked and I don't know why it keeps trying to check when it been told not to

To reassure you, the event id 131 is not caused by turning off windows updates for device drivers.  It is caused by a timing issue on the Microsoft server.  Microsoft are aware of this. 

Turning this off will only raise more errors because as you say you are blocking the updates.

If updates are turned on they do actually run but a few milliseconds too late to prevent id 131 being logged.

If they are turned off then you will see more errors such as 'Windows Update has been blocked by Policy'  

You may also see event id 200, 201 and 202.  In this instance the process doesn't complete at all because you have blocked it.

Fix for Event ID: 131 Metadata staging failed Error:

This error is occurring in Windows 10 (and probably previous versions of Windows) because of an incorrect URL in the Registry for the key:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata. The URL should be: http://dmd.metaservices.microsoft.com/dms/metadata.svc .

Fix:

1.  Open Registry Editor (Run*>regedit>*Enter or type regedit in the search box and press Enter).

2.  Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata by just opening the folders sequentially or going to Edit>Find and typing in DeviceMetadataServiceURL and then pressing Enter.

3.  On the right side of the screen, right click on DeviceMetadataServiceURL and click Modify. Highlight or delete the current URL and paste the following URL in: http://dmd.metaservices.microsoft.com/dms/metadata.svc. Press OK and close the Registry Editor.

4.  Reboot and these Metadata errors should be gone.

This is a timing issue on the Microsoft Server not forwarding the url fast enough.  The task to refresh the metadata does actually complete if you follow it through in your event log. However it is completing g a few milliseconds too late to atop the OS reporting ' Metadata staging Failed'   This started happening on 6th May 2015 and a lot of us have been using the temporary fix you suggest since then.

Microsoft are fully aware aware of this issue and did fix it in October but after a week the url stopped forwarding again.

The history of this issue goes back as far as September 2014 when it first started - Microsoft fixed the issue but it returned in 2015.   

If you follow all the comments through uou will note I have been working with Microsoft on the issue since May.  However, they appear to have stopped responding.

What we need is for more users to report the issue to get them moving.  It needs reporting at level 2 to get a response.

Hope this helps. 

http://www.eightforums.com/bsod-crashes-debugging/53670-continues-errors-startup-metadata-staging-failed.html