Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I recently installed a new 60GB SSD as my primary hard drive and re-installed Windows 7 Professional 64-bit. I then installed SSD Fresh from Abelssoft to optimize Windows to run on the SSD. It seemed to install okay, but when I try to run the utility, its splash screen appears briefly before it quietly closes. No errors are displayed; the utility just fails to launch. I have run SSD Fresh on another SSD-equipped Windows 7 Pro x64 computer in the past without any problems.

Does anyone know what might be preventing the program from running? I tried running sfc /scannow from the command line (with administrator privileges), shutting down the Spybot Resident, and disabling the firewall and virus scanner. I also tried running the tool as administrator; I even tried reinstalling it, running the installer as administrator. No luck.

Every time I try to launch the program the Event Viewer logs this same set of errors:

Error   4/2/2012 11:35:44 PM    Application Error   1000    (100)

Faulting application name: SSDFresh.exe, version: 1.0.0.0, time stamp: 0x4f2a45d8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007ff0016dbba
Faulting process id: 0x994
Faulting application start time: 0x01cd11fd9fe978df
Faulting application path: C:\Program Files (x86)\SSD Fresh\SSDFresh.exe
Faulting module path: unknown
Report Id: dfeed551-7df0-11e1-a2c7-002522c47ec0

Error   4/2/2012 11:35:43 PM    .NET Runtime    1026    None

Application: SSDFresh.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
   at AbBugReporter.BugForm.InitLanguage()
   at AbBugReporter.BugForm..ctor(AbFlexTrans.LanguageInfo, AbBugReporter.BugReportManager, Boolean)
   at AbBugReporter.BugReportManager.Show(System.Exception)
   at SSDFresh.App.App_DispatcherUnhandledException(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
   at System.Windows.Threading.Dispatcher.CatchException(System.Exception)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run()
   at SSDFresh.App.Main()

Error   4/2/2012 11:35:39 PM    SideBySide  59  None

Activation context generation failed for "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe".Error in manifest or policy file "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe.Config" on line 0. Invalid Xml syntax.

Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None
Error   4/2/2012 11:35:39 PM    SideBySide  59  None

For those who are interested, here is my system configuration:

share|improve this question
1  
What are the details provided in those SideBySide events? They usually tell you what the assembly it is trying to use (and the version it's expecting). Often it's non-existent/wrong version/corrupted runtime libraries (like the VC++ Redistributable Package), but you'll need to tell us what it's telling you it's looking for before we can tell you what you need. :) –  Ƭᴇcʜιᴇ007 Apr 3 '12 at 17:50
    
I'll post the error details when I get home this evening, so please stay tuned... –  Jim Fell Apr 3 '12 at 17:58
3  
Fresh installation of the Windows 7 does not require any tweaks for ssd. –  crea7or Apr 3 '12 at 21:48
    
I've added the error details. –  Jim Fell Apr 4 '12 at 1:00
    
@crea7: Check out this post on gHacks: ghacks.net/2011/10/15/ssd-fresh-optimize-windows-for-ssd-usage –  Jim Fell Apr 5 '12 at 15:30

2 Answers 2

up vote 0 down vote accepted
+100

Wouldn't it be easier to contact the company who wrote the program? Jim's suggestion about the C++ redistrubutable is great except the program is CLEARLY written in C#. This is clearly a bug in the application itself.

It might not be solvable by you, it might have to be solved by the company, who wrote the program.

share|improve this answer
    
Your answer was closest to the mark. I did a repair of the .NET Framework 4 Client, and the problem seems to have resolved itself. I can only assume that the framework somehow became corrupted. Start > Control Panel > Programs and Features, select Microsoft .NET Framework 4 Client Profile, click Uninstall/Change. From the Maintenance screen that opens, choose "Repair .NET Framework 4 Client Project to its original state." –  Jim Fell Apr 10 '12 at 23:09

Some ideas on what you could try :

  1. Look for a missing Microsoft Visual C++ Redistributable Package (examining the manifest embedded in csc.exe or present in its folder will indicate the required version)
  2. Using the System Update Readiness Tool sometimes solves problems
  3. Turn off Hardware DEP for csc.exe
share|improve this answer
    
Thanks for the tips! These were good suggestions, which I'll be sure to keep in mind for future debugging. –  Jim Fell Apr 10 '12 at 23:09

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.