the application is unable to start correctly 0xc0000005 after windows update

Anonymous
2013-08-14T17:47:16+00:00

Sorry my english :)

Hello, today, after windows 7 x64 update itself and reboot most of all my applications cant start and crash with error 0xc0000005. 

In "installed updates" I see a lot of Security update for Microsoft .Net Framework Client profile installed today, but I cant Uninstall them, click Uninstall, then I see "Setup.exe *32" in the task manager, then receive an error "An error occurred while trying to uninstall <update name>. It may have already been uninstalled" :(

Also I make a system restore, but without any result :(

Any ideas?

How can I manually remove this updates? Registry cleaning or something else?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-08-15T12:53:44+00:00

You have hacked or infected files on your computer.

Check your BCD and do the below fix if necessary (at your own risk) 

In Windows open CMD as Administrator and type BCDEdit and enter,  if your Windows Boot Loader Path is xOsload.exe then you need to remove some files and repair your BCD.

NOTE:  you will need to re-activate Windows afterwards, so make sure you have your Windows 7 key handy.

Boot to Windows Repair - Command

Del D:\Windows\System32\xOsload.exe

Del D:\Windows\System32\xNtKrnl.exe

Del D:\Windows\System32\Drivers\oem-drv64.sys

attrib c:\boot\bcd -h -r -s

ren c:\boot\bcd bcd.old

bootrec /rebuildbcd

Was this answer helpful?

1500+ people found this answer helpful.
0 comments No comments

172 additional answers

Sort by: Newest
  1. Anonymous
    2013-09-30T18:09:07+00:00

    Of course it is hacked, all activated with WL are, so what? I have other computers that were also activated the same way, they report the "problematic" changes as you indicate above and they have the 2 offending kb updates plus all other updates applied and they work like a charm. So it has absolutely nothing to do with "hacked " files, but is just hardware related.

     

    Of course it is hacked”???????? why "of course"?

     

    OK, so it just happens that I was correct and you do have hacked files on your computer but you are telling me it has nothing to do with them?  

    0xc0000005 is a common error code that can be caused by many different things, but for most people that recently got the error after updating it is because of a hacked or infected kernel file/s.   If it was hardware then why is my fix above curing the problem? 

     

    You might have other computers that did the updates without failing because their ntoskrnl.exe and winload.exe files where not hacked or infected.

     

    If you are happy with your temporary fix of simply uninstalling the kernel update then, then that’s fine.

     

     

     

     

     

    You are right man, common don't overheat. However it is a long fix for the legit and even bigger headache for the WL activated folks, the other solution on the other hand is a matter of seconds for everybody and is nothing temporary, as you keep repeating. Soon Microsoft will pull out the offender and that will be the end of it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-09-30T17:39:01+00:00

    Please remove or skip this updats (KB2872339) and (KB2859537), mark like hidden!!!

    "MS13-077 / KB2872339 – Vulnerability in Windows Service Control Manager Could Allow Elevation of Privilege

    This update fixes one privately reported flaw in Microsoft Windows. The threat is minimal because the attacker must either have valid logon credentials and be logged on locally to the vulnerable system, or trick a user into running a specially crafted application that triggers the exploit. If an attack is successful, the attacker could gain elevated privileges on the compromised system."

    Don't just uninstall this update because it will leave your computer vulnerable, do the full repair that I've posted above, if you need any help then ask me, and I will see if I can help.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-30T16:42:00+00:00

    Alright, upon further investigation it is clear now, as Aras Jac kindly pointed out. The latest broken KB update is (KB2872339), by uninstalling it the system will be back to normal. You might have, or not the other broken offender (KB2859537). If you have it get rid of it, if not you will be ok, it has been pulled out by Microsoft and is not showing up in the updates anymore. So block also KB2872339 until Microsoft pulls that thing out too. The rest of updates are working ok. Keep in mind that those same updates do no harm 32bit systems. Only the 64bit are affected.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-30T16:04:20+00:00

    Of course it is hacked, all activated with WL are, so what? I have other computers that were also activated the same way, they report the "problematic" changes as you indicate above and they have the 2 offending kb updates plus all other updates applied and they work like a charm. So it has absolutely nothing to do with "hacked " files, but is just hardware related.

    Of course it is hacked”???????? why "of course"?

    OK, so it just happens that I was correct and you do have hacked files on your computer but you are telling me it has nothing to do with them?  

    0xc0000005 is a common error code that can be caused by many different things, but for most people that recently got the error after updating it is because of a hacked or infected kernel file/s.   If it was hardware then why is my fix above curing the problem? 

    You might have other computers that did the updates without failing because their ntoskrnl.exe and winload.exe files where not hacked or infected.

    If you are happy with your temporary fix of simply uninstalling the kernel update then, then that’s fine.

    Was this answer helpful?

    0 comments No comments