Woody Leonhard's no-bull news, tips and help for Windows and Office
RSS icon Email icon Home icon
  • A solution to the MS12-034 0x8007F0F4 problem?

    Posted on May 10th, 2012 at 12:48 woody 3 comments

    A Windows expert I know (thanks again, SB!) claims she found out why she couldn’t get the MS12-034 .NET patch installed on her computer. It kept dying with an Error 0x8007F0F4 error, as described in my earlier post.

    A long, long time ago she re-mapped the Scroll key on her PC, following the advice in “I’ve Hit F12 For the Last Time – Jesper’s Blog“. Since the patch is playing around with keyboard layout files, apparently that was enough to make the MS12-034 installer go kablooey.

    Her advice:

    From a command prompt copy the following:

    reg delete “hklm\system\CurrentControlSet\Control\Keyboard Layout” /v “Scancode Map” /f

    and hit Enter. Reboot your PC, re-install the patch, and it works.

    Anybody else encountering the problem? Does this fix it?

     

    3 responses to “A solution to the MS12-034 0x8007F0F4 problem?”

    1. Doesn’t work for me.

      Error: The system was unable to find the specified registry key or value

      This system has an older IBM click-key keyboard without “Windows” keys.

    2. This worked for me! Thanks.

      I have CapsLock remapped to a control (ctrl) key on all my machines. The patch install was failing.

      I found I was able to reduce the number of reboots by deleting the registry key and then installing the patch without rebooting. Then I put the ScanCode Map entry back. Finally after all three steps I rebooted.

    3. Thanks for the solution. Finally I found your hint!
      Had the same issue with installing security update 2681578 for Windows XP. I had long time ago re-programmed the caps lock key to not interfere with my typing.
      Your solution worked. However not from the command line, but I deleted the Scanning Map key using regedit (after backing up the registry, of course …) . Afterwards the installation went through.
      Ouff!

    Leave a reply