Surface SMF Core Driver not loading (Error Code 31)

Question

Surface SMF Core Driver not loading (Error Code 31)

Jay Gourley 61

Surface SMF Core Driver not working properly. Possibly a result of August (2025) update bug or corruption during install.

My Surface Pro 9 (Windows 11 build 25H2, Insider Preview) operates normally. It might generate more heat than expected when CPU levels are low. I'm not sure. In any case, I don't want to see the yellow triangle in my Device Manager. I did not notice this until after the August Surface firmware update, though it's possible the problem existed earlier.

Does anyone above my paygrade know if this driver might be related to thermal regulation or if it's failure to load properly could be taxing my system?

I've done the usual troubleshooting:

Uninstalled the device in Device Manager. It reinstalled with the same failure.
Tried downloading the .msi for the August driver updates. It abofts aborts with an error message saying it's not for my hardware.
Tried unpacking the .msi file to get the SMF Core Driver. The .msi package is not a driver package. It's just a Microsoft supervisor package that collect the files and installs them.
Tried the Surface Diagnostic Toolkit. It also rejected my hardware, which is undoubtedly a Surface Pro 9. The hardware is also a fairly plain vanilla Surface Pro 9. I'm the original owner and the only OS changes have been done by Windows Update. Nothing esoteric that I can think of.
I opened a case with Surface Support that returned a confidence-depleting and spectacularly vacuous statement, "callback times may vary," suggesting someone at Microsoft believes Surface owners might value that information.

User's image

2 answers

Your answer

Answer 1

Hello @Jay Gourley

It sounds like you're dealing with the Surface SMF Core Driver issue on your Pro 9. That yellow triangle in Device Manager can be annoying, and I appreciate that you've already gone through extensive troubleshooting steps to try and resolve it.

Looks like this started after the August update, especially since you're on the Insider Preview. This driver handles stuff like keeping your device cool, managing power, and tracking performance.

Error code 31 usually means the driver's messed up or not made for your system. Since you've tried reinstalling and the Surface Toolkit didn't work, it's likely something with the Insider build or the update itself. That .msi file doesn't install the driver directly.

Try downloading a version from a safe source like v1.173.2.0. Manually install it through Device Manager by selecting Update Driver and pointing it to the extracted folder. Also, I suggest switching back to the regular Windows 11 build.

Are you seeing any real problems, like the fan running crazy, battery draining fast, or device slowing down? Or is it just the warning bugging you? Have you thought about trying the Release Preview channel to see if the driver installs there?

Let me know if the manual install works. If not, we'll find another solution.

All the best,

Rez

Answer 2

HK 0

@Jay Gourley

Hi there

I am in the exact same situation with my Surface Pro 9

I bought it second hand last year

The device SKU was displaying as Surface Pro 9

I had some wifi issued and decided to do Reimage last week.

To my surprise after the reinstall was complete , the device SKU changed to OEMLO .

Now I can't run Surface diagnostic tool and device manager show Surface SMF Core Driver not working properly , same like your case.

Have you had any luck finding a solution?

and I am wondering what are the possible consequences on the system down the road with this OEMLO device?

Thx

Jay Gourley 61 Reputation points

2025-11-28T20:16:13.11+00:00

Hi, HK. I have not found a solution. So I plan to send my computer to Microsoft for an exchange in a couple of weeks when my school situation allows me to be without it. From my research and failed efforts to find an alternative, sending your computer in for an exchange (assuming it's under warranty) is the only option I've found. Reinitializing the SKU can only be don't with physical access to the computer by Microsoft engineers. Hopefully, you can find a time to be without your computer for a week or two. If are not under warranty, you're in a different situation. I don't know what you should do.
HK 0 Reputation points

2025-11-28T20:46:01.16+00:00

Thank you Jay for the quick response

Unfortunately my Surface Pro 9 is not under warranty so I am kind of stuck with it.

it is quite puzzling that the SKU changed after the re-image from Surface pro 9 to OEMLO !!

Despite the error with Surface SMF Core Driver , the device is running normally and didn't notice anything odd

I am hopping that the device will keep receiving all the critical updates in the future, that is my only concern

I don't see an issue with Surface diagnostic tool app not running , I guess as long as there is no issue with the device.

Please post here any info you may think may help

Thank you
HK 0 Reputation points

2025-11-30T02:28:04.5633333+00:00

@Jay Gourley

Hi Jay

Has your device always showed "OEMLO SKU Number i7" as model ID? The clue is if you were able to run Surface Diagnostic Tool in the past , it means it was ID'd as "Surface Pro 9"

in my case the tool functioned normally until i did re-image to the device last week.

thx
Jay Gourley 61 Reputation points

2025-11-30T02:51:17.8666667+00:00

No, HK. My device did not always show the "OEMLO SKU Number i7" in the Surface app or "OEMLO Product" in system information. It only lost its correct initialization shortly before I started this thread, long after I bought it new. Until then drivers could be updated and the Surface Diagnostic Tool did not return the false error message saying my computer was not a Surface device.
HK 0 Reputation points

2025-11-30T04:22:29.0366667+00:00

Jay

Interesting that both our devices experienced the same thing , went from Surface Pro 9 to OEMLO!!

Happy that you will be able to fix yours through the warranty.

On my side , I will live with it . for now the only issue seems the Surface SMF Core Driver that is not working properly and have no idea how this swill affect the device.

Hopping it will get fixed in the next major update?

Thanks for sharing your experience and happy to hear from you on this in the future

Good luck
Jay Gourley 61 Reputation points

2025-11-30T14:40:13.9333333+00:00

Thanks, HK. It will probably be a waste of time, but the payoff might make it worth the gamble to contact Microsoft support about the cost of just reinitializing your SMBIOS. I'm told that's about a 10-minute job that's as simple as running an SFC.

Share via

Surface SMF Core Driver not loading (Error Code 31)

2 answers

Your answer