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

What a bullshit confusing answer is that? In fact we have found the fix that everybody is so screaming about. It takes exactly 2 min to complete and the system is back to normal. So folks do the following:

Sorry but you are very wrong, 28 people have marked my answer as helpful, it's a hacked or infected kernel file that causes this error, the Windows update tries to update important kernel files but it fails because some have been altered. Uninstalling the update is only a temporary fix.  You need to remove the hacked or infected files and then re-build your BCD.  

You have hacked or infected files on your computer. Try downloading and running rkill.exe, that might confirm that I'm right.

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

You might need to use different drive letters, like D: instead of C: and E: instead of D:

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

"That fix will only work for a short while unless you turn off updates.  The full fix I've already posted."

What a bullshit confusing answer is that? In fact we have found the fix that everybody is so screaming about. It takes exactly 2 min to complete and the system is back to normal. So folks do the following:

1. List the installed updates by date
2. Find the most recent group of updates (likely the date your problem occurred).
3. Open command prompt as Administrator (thank god it still exists in Win 7 & 8)
4. type wusa.exe /uninstall /kb:XXXXXXX

Where XXXXXXX you replace with the respective number of KB for the latest group of installed updates. After each uninstall Windows will ask you to reboot. Say: "Reboot later". Once you are done with the group of recent updates (in my case today sept 27th 2013  there were 5 updates), you reboot the computer. After the restart go strait to Windows update and disable it until those updates are fixed by Microsoft, or you feel comfortable to start updating again.

That's all, done in 2 min. Fuxx Microsoft and the rest of big corporations that put a price tag on everything! Long live the free sharing of data and knowledge.

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

(KB2872339)

That f**cking fixed it. Another devastating update by Windows. Doing a windows update takes a lump of your free time and now we have to worry with it being a mess and have to find a f**cking fix that takes more of our time searching the net. SERIOUSLY MICROSOFT. GET A GRIP!

And a huge kudos to you sir for pointing that out.

That fix will only work for a short while unless you turn off updates,  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

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

(KB2872339)

That f**cking fixed it. Another devastating update by Windows. Doing a windows update takes a lump of your free time and now we have to worry with it being a mess and have to find a f**cking fix that takes more of our time searching the net. SERIOUSLY MICROSOFT. GET A GRIP!

And a huge kudos to you sir for pointing that out.