Home > Uncategorized > SOLVED: STOP: C0000135 The program can’t start because %hs is missing. Try resintalling the program

SOLVED: STOP: C0000135 The program can’t start because %hs is missing. Try resintalling the program

September 14th, 2011 Leave a comment Go to comments

Update 21 Jan 2012: I have noticed that this consrv.dll virus is back again this week. It also seems to have some friends, make sure you do a scan with TDSSKiller and, once you’re up and running, that your Base Filter Engine Service, Windows Firewall Service and Security Center Service are running. If they aren’t, take a look at my blog entry on fixing a missing BFE in Windows 7. Also, if you are clueless on how to edit the registry from the recovery console, take a look at Web Traffic’s post from 4 Dec 2011 or Nick’s comments below from 20 Jan and my comment from 24 Jan 2012, this may help (and remember to unload the hive when you are finished with the edit).

This was a Windows 7 machine that had caught a virus. The virus was removed while the drive was out of the machine but upon subsequent boot to either safe mode or normal mode, the blue screen error “STOP: C0000135 The program can’t start because %hs is missing. Try resintalling the program” would appear. No error logs and no help on The Google (the computer does not have AVG installed).

The fix for this problem requires a registry edit to remove a reference to the consrv.dll file that was a virus and was removed. Using regedit from the repair console, the following keys required editting:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\SubSystems

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager\SubSystems

Under theses keys, edit the data in the Value Name “Windows”, changing the text “consrv” to “winsrv”. This is a long string so just parse through it and make the one change, here is what a good entry looks like:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

I have bolded the entry that previously said “consrv”.

Alas, there are apparently (many?) other reasons for this error, if this doesn’t fix yours, you may want to give up early and reinstall because there do not appear to be any other solutions out there.

  1. Brian
    June 24th, 2013 at 19:49 | #1

    Sir, how would I “import my system hive from my target drive?”

    • June 24th, 2013 at 20:26 | #2

      That question is the computer equivalent to “which end of this chain saw should I be holding?” It’s a very valid question, but if you have to ask it, you should not be messing with it (the registry). The link above gives a very clear description of how to load a slaved registry file.

  2. Brian
    June 25th, 2013 at 19:49 | #3

    Well evidently sir I haven’t seen the “consvr” in the “value data” in the Registry even when I proceeded to “load hive” on my recovery drive and the “Os drive”, would you by chance know of any other suggestions of what may be causing the problem if it’s not that, Or clearly what I haven’t done to locate the “consvr?”

  3. Raffae
    October 15th, 2013 at 23:33 | #4

    Hi sir, i got the same problem here. I already do all the thing like load hive and i had the controlset001 and controlset002 but still it state “winsvr” instead of “consvr”. What should i do? This is an office comp there is so many data in there.
    pardon for my broken english.

  4. November 23rd, 2013 at 20:04 | #5

    Thank you. I wouldn’t have thought to remove that edit. Got it all fixed and up and running again. Take care.

  5. Deborah
    March 29th, 2014 at 00:54 | #6

    Oh My Gosh, thank you, thank you so much!!!!! I know nothing about computers and got this frustrating virus. Read your article and I fixed it. So beautiful to see my desktop again. You are marvelous! xo

    • March 29th, 2014 at 12:45 | #7

      We live for feedback like this, thanks. Glad you’re up and working.

  6. oscar
    September 12th, 2014 at 08:44 | #8

    Well, for some people it worked but not for me. I followed the directions to the letter. I finally decided to reinstall, well, guess what it didnt work either. I think the final answer would be to buy a new hard drive.

Comment pages
1 2 3 4 245
  1. February 14th, 2013 at 01:03 | #1