Windows 10 update killed HandBrake

VidMus wrote on 11/18/2015, 3:38 PM

Windows 10 update kills HandBrake

HandBrake no longer runs on my system. I will download the latest version and see if that does not fix it.

Starting HandBrake I get a blank window with a grey area in it.

Starting HandBrake with Vegas to HandBrake I get the following:

An Unknown Error has occured.
Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate HandBrake.ApplicationServices.Services.LibScan --->

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Management.ManagementException: Provider load failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at HandBrake.ApplicationServices.Utilities.SystemInfo.get_GetGPUInfo() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices\Utilities

\SystemInfo.cs:line 133
at HandBrake.ApplicationServices.Utilities.GeneralUtilities.CreateCliLogHeader() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices

\Utilities\GeneralUtilities.cs:line 121
at HandBrake.ApplicationServices.Services.LibScan..ctor() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices\Services\LibScan.cs:line 106
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.FastCreateInstance(Type implType, Object[] arguments, Type[] signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance(CreationContext context, Object[] arguments, Type[] signature)
--- End of inner exception stack trace ---
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance(CreationContext context, Object[] arguments, Type[] signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.Instantiate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context)
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context)
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.ResolveServiceDependency(CreationContext context, ComponentModel model, DependencyModel dependency)
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.Resolve(CreationContext context, ISubDependencyResolver contextHandlerResolver, ComponentModel model, DependencyModel

dependency)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArgumentsCore(ConstructorCandidate constructor, Object[] arguments, CreationContext context, Type[]

signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArguments(ConstructorCandidate constructor, CreationContext context, Type[]& signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.Instantiate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context)
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context)
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments)
at Castle.MicroKernel.DefaultKernel.Resolve(Type service)
at Caliburn.Micro.IoC.Get[T](String key) in c:\Users\Rob\Documents\CodePlex\caliburnmicro\src\Caliburn.Micro.Silverlight\IoC.cs:line 32
at HandBrakeWPF.App.OnStartup(StartupEventArgs e) in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrakeWPF\App.xaml.cs:line 78
at System.Windows.Application.<_ctor>b__0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Either way, closing HandBrake gives me:

An Unknown Error has occured.
Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate HandBrakeWPF.Services.EncodeServiceWrapper --->

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Management.ManagementException: Provider load failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at HandBrake.ApplicationServices.Utilities.SystemInfo.get_GetGPUInfo() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices\Utilities

\SystemInfo.cs:line 133
at HandBrake.ApplicationServices.Utilities.GeneralUtilities.CreateCliLogHeader() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices

\Utilities\GeneralUtilities.cs:line 121
at HandBrake.ApplicationServices.Services.Base.EncodeBase..ctor() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrake.ApplicationServices\Services\Base

\EncodeBase.cs:line 59
at HandBrakeWPF.Services.EncodeServiceWrapper..ctor(IUserSettingService userSettingService) in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrakeWPF\Services

\EncodeServiceWrapper.cs:line 84
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.FastCreateInstance(Type implType, Object[] arguments, Type[] signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance(CreationContext context, Object[] arguments, Type[] signature)
--- End of inner exception stack trace ---
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateInstance(CreationContext context, Object[] arguments, Type[] signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.Instantiate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context)
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context)
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.ResolveServiceDependency(CreationContext context, ComponentModel model, DependencyModel dependency)
at Castle.MicroKernel.Resolvers.DefaultDependencyResolver.Resolve(CreationContext context, ISubDependencyResolver contextHandlerResolver, ComponentModel model, DependencyModel

dependency)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArgumentsCore(ConstructorCandidate constructor, Object[] arguments, CreationContext context, Type[]

signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.CreateConstructorArguments(ConstructorCandidate constructor, CreationContext context, Type[]& signature)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.Instantiate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context)
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context)
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments)
at Castle.MicroKernel.DefaultKernel.Resolve(Type service)
at Caliburn.Micro.IoC.Get[T](String key) in c:\Users\Rob\Documents\CodePlex\caliburnmicro\src\Caliburn.Micro.Silverlight\IoC.cs:line 32
at HandBrakeWPF.ViewModels.ShellViewModel.CanClose() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrakeWPF\ViewModels\ShellViewModel.cs:line 196
at HandBrakeWPF.Views.ShellView.OnClosing(CancelEventArgs e) in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.10.0\win\CS\HandBrakeWPF\Views\ShellView.xaml.cs:line 152
at System.Windows.Window.WmClose()
at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Comments

ddm wrote on 11/18/2015, 3:45 PM

I just tried launching hb from vegas, no problem. Latest w10 update installed and version 10.2... of hb.

GeeBax wrote on 11/18/2015, 3:55 PM

I have been using that latest version of Handbrake along with Windows 10 for some time, no problem.

VidMus wrote on 11/18/2015, 4:20 PM

I installed the latest version and it now works but Vegas to HandBrake still does not work properly.

The batch file shows a repeated "Error: Provider Load Failure" and will not finish. So it cannot goto stop and finish the entire process.

I remember a previous thread about updating files but I cannot remember what they were. Will updating those files solve this?

Thanks for the replies.

VidMus wrote on 11/19/2015, 10:44 AM

I abandoned Vegas to HandBrake and went back to the method I previously used. :(

Marco. wrote on 11/20/2015, 3:56 AM

The website VegasVideo.de includes the updated current files for the Vegas2HandBrake workflow. You might give it a try. Be sure to use the latest PFM version then (or the one from the updated link on the Vegas2HandBrake website).

ushere wrote on 11/20/2015, 5:12 AM

forgive my ignorance, but....

my normal practice has always been to render out a 'master' file from the tl (usually hd or hd422 mxf) to both archive and use in handbrake. i have never felt that the quality was at question.

what advantage does frame serving actually achieve?

VidMus wrote on 11/20/2015, 5:29 AM

@ Marco.

Thanks much for the reply. My main concern is, what is to prevent a future update or whatever to cause this to break again? And then I will have more down time?

My editing system was up and ready when I noticed that it was being re-started. I was working on my other computer at the time. The editing system had been updated and that is when all the problems happened. In the past I always had my editing system off-line to prevent this but I now need it online to network with my other system. I will not try to explain the reasons here. I just simply need it online all of the time. And yes, I need the auto-update on as well.

So I need something that is reasonably future proof and will not break with certain updates and combinations of file versions. Others did not have the problem I had because the file versions they have do not break with the Windows update I got or they might not have gotten that update yet or at all. But what will happen in the future?

There is a clear reason why Vegas gets broken on one system and not another.

While it is a bit counterproductive, the old method with an intermediate is future proof and reliable. Also, it does not require all of those other whatever's to be installed. I am always concerned about installing stuff on my system because there is no telling what might lurk in those installations.

DebugMode FrameServer works fine with other apps, why can't they just make HandBrake such that it can also work and not need all of that other stuff?

I think that until they do, I will stick to the old method for now. Or am I missing something on this subject?

Anyway, I am getting great results with the old method and while slower it reliably works.

If I get tired of the old method, I can either update the current files or use my cloned backup which does not have the problems. And then when the next Windows update happens?

Thanks again,

Danny Fye
www.dannyfye.com

Grazie wrote on 11/20/2015, 5:33 AM

@Leslie: " what advantage does frame serving actually achieve?"

I've understood that if you are wanting the type of output that HB gives, then you do not need to make an interim DI. FS allows us to use the frameserving without needing to do a pre-render.

G

Marco. wrote on 11/20/2015, 5:45 AM

You are right. Unfortunately this certain workflow involves so many single tools which depend on each other, that one little change/influence could break the whole thing and - even worse - will start the need of kind of trial&error-investigating which of the tools causes the break and spending (sometimes too much) time solving it.

It's comfortable only if it works without worring too much about the influences around.

VidMus wrote on 11/22/2015, 3:14 AM

I went back to Windows 7 64 bit Ultimate.

ushere wrote on 11/22/2015, 4:06 AM

@grazie - thanks for the reply. is that the only advantage?

my workflow / clients always want a 'master quality' file for future use (be it for re-editing / voicing or simply chopping up for reuse in other projects). so, if i have a high quality file to feed hb am i missing something else?

Grazie wrote on 11/22/2015, 4:15 AM

@Leslie: In respect of your question, I have two workflows:

1] Using VP2HB for clients wanting HB output which is both acceptable for the web and internal comms. They don't want masses of storage being used. I always find it's nice to be able to give clients what they want, quickly.

2] Non HandBrake output for my future editing which I keep on behalf of the client.

G