2/17 firmware update installed, but when I look in Device Manager in the firmware section, I get Code 10

Anonymous
2016-02-20T02:36:42+00:00

Split from this thread.

You may THINK that you have the updates installed but you may NOT:

BUT:

I tried reboots, re-installs, and everything else, but the updates fail to start.

Surface | Surface Book | Power and battery

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

47 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2016-02-20T15:08:15+00:00

    I am running Win 10 Pro, Version 1511 OS Build 10586.104 and have the exact same problem following Feb 17 update.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-20T06:37:50+00:00

    I have 3 SBs: 2 run Win10 Enterprise Build 10586.104.  These two have the problem with getting the firmware update to install.

    The third one Win 10 Pro also 10586.104.  This one installed and started fine.

    Hope this helps.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-19T20:05:54+00:00

    Hi ReSurfaceMan, can you let me know what your version of Windows is. Run winver and let me know what it says there for your version and OS build. Can also see this through Settings> System> About.

    Thanks,

    Greg

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-02-19T10:40:47+00:00

    Well the way it works for Surface, is that when you update the firmware, a new driver is installed.  You can see this in Device Manager Firmware section.  Then you are requested to do a reboot.  Once you do this, a firmware update is triggered which loads the firmware you just installed to the chips.  This last part fails.  The system tries to load the drivers in the chip but it fails and after multiple reboots goes into a shutdown state.  You can then boot by pressing the power key, and the boot process will proceed but the new firmware is not loaded into the chips.  When you finally get into windows you might see "reboot required" in device manager.  You can reboot and repeat the process but the load still fails.  Finally after 2-3 reboots, in device manager you see:

    "This device cannot start. (Code 10)

    Indicates a revision number encountered or specified is not one known by the service. It may be a more recent revision than the service is aware of."

    This indicates that the new firmware could not be installed.  At the same time, the firmware update shows as successful in Windows Update - which is of course bogus. If you boot into the bios by a two finger reboot, you see the old versions of the firmware installed..

    No fix or useful suggestion from Microsoft yet.

    Was this answer helpful?

    0 comments