Event ID 122 Access to Drivers on Windows Update Blocked by Policy - Fix Here


Access to drivers on Windows Update was blocked by policy


EventID:122 errors appearing on Windows Server 2012 Hyper-V host.  “Device Setup Manager” service.

There is a scheduled task that runs each night in “Microsoft | Windows | Device Setup” called “Metadata Refresh”. When that task runs it causes the “Device Setup Manager” service to start, and that’s what is causing the messages. 
If you look in the Event Viewer under “Application and Services Logs | Microsoft | Windows | DeviceSetupManager | Admin” and filter on Event ID 122 then you can see the entries.

The “policy” that is causing the block is actually the Device Installation Settings. 



SOLUTION
Use the search in the Control Panel window and look for “device installation”
When that window opens, you will see the settings that define the “policy”
If you change the setting to “Always install the best driver software from Windows Update.” then the Event ID 122 errors will go away.
If you *also* select the “Automatically get the device app and info provided by your manufacturer” then the whole setting will change itself to the first “Yes, do this automatically” option (so the first option is the same as selecting both the bottom ones)
The other option is to disable the “Metadata Refresh”  scheduled task.

Comments

  1. AnonymousJune 9, 2014 at 9:21 AM

    I'm more interested in silencing the events than enabling this setting - Where is the scheduled task to which you are referring?

    Thanks

    ReplyDelete
  2. WilkyJune 11, 2014 at 12:51 AM

    To silence the error.
    Open Task Scheduler, Navigate to Microsoft > Windows > Device Setup, and have a look at the Metadata Refresh Task. By triggering this task, the event 122 can be generated each time.

    The task could be disabled but it is not clear from the Task's Actions what other functions this task performs. My best guess is this task runs Plug in Play looking for devices without drivers.

    Mark

    ReplyDelete
  3. AnonymousFebruary 10, 2016 at 8:46 AM

    I would agree that this is looking for devices without drivers. I have three Windows 2012 servers and all have their Device Installation Properties set to "No" and "Never". All three also have the "Metadata Refresh" task and it's running every day. However, only 1 gets Event 122 in the Application Log. I went into Device Manager and there were yellow exclamation icons beside some devices that had missing drivers.

    ReplyDelete

Post a Comment

Popular posts from this blog

Server Manager Refresh completed with one or more warning

The system cannot access one or more event logs because of insufficient rights The Problem: Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server. Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered. The Solution: Following the event logs leads to a few registry keys. You can eliminate the messages by: 1. Export the following registry keys (for safety) 2. Delete the following keys: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DxpTaskRingtone/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-Roaming/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-SCDICCOMPILER/Analytic HKLM\SOFTWARE\Mic
Read more

Shrewsoft VPN client - can't open Access Manager

Shrewsoft VPN client - can't open Access Manager Problem Access Manager is not visible Occurred after adjusting using dual monitors. Reinstall does not fix the issue. The Fix Use regedit to rename or delete the following key: HKEY_CURRENT_USER\Software\ShrewSoft\vpn\user Had a look around the Shrewsoft support site - nothing useful in there to fix this problem.
Read more

Hyper-V could not replicate changes for virtual machine as replication is suspended on the Replica server

Image
EVENT ID 32088 for all VMs After running out of disk space on the Replica host server, all VMs stopped replicating.  Replication cannot simply be started by right clicking on the source VM and selecting Resume Replication. No console error message just the event log event 32088.  I considered removing replication and re-replicating but this seemed an awful lot of work for simple problem. Tried stopping the Hyper-V service on the replica host and restarting, but this also did not work. THE FIX 1. Go to the destination replica server, right click each VM and select Resume Replication.  2. Now you can go to the source server, right click each VM and select Resume Replication. For some strange reason this works. Just trying one end or the other will fail without a console error message (but shows in the event log).
Read more