Problems with Handbrake after Windows updates

ComputerWizKid

Golden Member
Apr 28, 2004
1,188
0
86
I am having problems with Handbrake (It all seemed to happen after the "Patch Tuesday" on 03/12/2013) I can load the program but as soon as I add a project to the queue it crashes with an error
I have tried reinstalling the program and compatibility mode does not work either. Is anyone else having problems with Handbrake since the last "Patch Tuesday"?
I ram memtest and all of my hardware tests out good.
I am stumped at what to do here any suggestions?
Thanks

Here is the error I am getting

OS is Windows 7 Home Premium SP1

HBerr1.jpg



HBerr2.jpg


Here is all of the text in the first box

Code:
An Unknown Error has occured.
System.Exception: An error has occured in the QueryParser Utility. ---> System.FormatException: Input string was not in a correct format.
   at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   at System.Double.Parse(String s, IFormatProvider provider)
   at HandBrake.ApplicationServices.Utilities.QueryParserUtility.Parse(String input)
   --- End of inner exception stack trace ---
   at HandBrake.ApplicationServices.Utilities.QueryParserUtility.Parse(String input)
   at Handbrake.frmQueue.RedrawQueue()
   at Handbrake.frmQueue.UpdateUiElementsOnQueueChange()
   at HandBrake.ApplicationServices.Services.QueueManager.RestoreQueue(String importPath)
   at Handbrake.Functions.Main.RecoverQueue(IQueueProcessor encodeQueue)
   at Handbrake.frmMain..ctor(String[] args)
   at Handbrake.Program.Main(String[] args)
 

ComputerWizKid

Golden Member
Apr 28, 2004
1,188
0
86
OK the problem was apparently caused by the file name of one of my files that I was trying to encode
I changed the name and the file and all of my other encodes finally finished
The name of the file was "Timmy's 2-D House Of Horror" (The Fairly OddParents Rule!) I don't understand how that could cause a problem
 

Charlie98

Diamond Member
Nov 6, 2011
6,298
64
91
Mine has been doing that off and on for about a month. It all has to do with the destination path... or at least it did in my case. It was very frustrating until I got it sorted out.