Unable to Load PowerShell Handler for VSBuild
Explains how to resolve the "Unable to load task handler PowerShell for task VSBuild" error in TFS vNext builds, covering PowerShell versions and …
TL;DR; If you are testing the new vNext build agent on Windows Server 2012 R2 with Visual Studio 2015 Preview, you may encounter a “Could not load file or assembly” error due to a DLL version mismatch and strong name validation. This issue only occurs with the Preview version and should resolve in future releases. As a temporary fix, disable strong name validation by running “sn -Vr ,” on the server, but only do this in test environments, not in production.

If you are using Windows Server 2012 R2 to test out the new vNext build agent then you may run into an error where it could not load file or assembly while configuring Build vNext Agent.
Microsoft has released a CTP of TFS 2015 that includes the vNext build system. You can download TFS 2015 and try it out today. Remember that this is not a go-live version and you should not install it in production.
I have been playing around with the new Build vNext Agent that Microsoft has been developing and I found that I was not able to register the Agent on Windows Server 2012 R2 when I had Visual Studio 2015 Preview installed. Before I installed Visual Studio I had no issues, but once on I got a “Could not load file or assembly” when trying to run the registration.
It looks like there is a version mismatch on the DLL.
1Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.Services.Client, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
2
3--- End of inner exception stack trace ---
4
5at VsoAgent.Program.Main(String[] args)
6
7WARNING: UnConfigure agent finish with Error, you can check logs under _diag folder, determine whether you can ignore the error.
I am fairly sure that this is a time limited error and once VS 2015 comes out of Preview, or the DLL versions settle down this will not be an issue, however to fix it for now we need to turn of Strong Naming for .NET at the command prompt.
You need to run “sn -Vr *,*” on the server to disable strong signing. This should only be the case as part of the current preview program. I would expect this issue to go away with the next release, at least on Server 2012 R2.
This is only required when you are running Visual Studio 2015 Preview on the Build vNext Agent.
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.

Kongsberg Maritime

Lockheed Martin

DFDS

Healthgrades

Boeing

ProgramUtvikling

Higher Education Statistics Agency

Flowmaster (a Mentor Graphics Company)

Workday

Brandes Investment Partners L.P.

Big Data for Humans

Jack Links

Genus Breeding Ltd

SuperControl

Schlumberger

Xceptor - Process and Data Automation

Capita Secure Information Solutions Ltd

Qualco

Department of Work and Pensions (UK)

New Hampshire Supreme Court

Royal Air Force

Washington Department of Enterprise Services

Ghana Police Service

Nottingham County Council

Freadom

Boeing

Higher Education Statistics Agency

Epic Games

Sage

Microsoft