Surface Pro 2 system issues

Barb, if I could recall I'd go through the same process with the correct BIOS image.  Unfortunately the process I went through eludes me.  I most likely did a search for Surface Pro BIOS updates and loaded the latest version.  According to sites I have visited, you can manually update the BIOS in Pro 3 and Pro 4 units, but not any the precede those models.  I guess that's not entirely true but obviously you shouldn't.  Not sure why I was able to load a Pro 4 BIOS to begin with.  Seems like the loader should have done a simple test before allowing it to happen.  My problem now is to figure how to back out of this situation.

Thanks

Exactly how did you do this?

> I recently did an update to the system BIOS and somehow the BIOS I loaded was for a Surface Pro 4.

somehow the BIOS I loaded was for a Surface Pro 4

Yikes.  I don't really want to even speculate about fixing that.  But in case it will help here is my BIOS details (without the SerialNumber)

wmic:root\cli>BIOS list /format:list

BiosCharacteristics={7,11,12,15,16,17,19,23,24,25,26,28,29,32,33,40,42,43}

BuildNumber=

CodeSet=

CurrentLanguage=en|US|iso8859-1

Description=2.05.0250

IdentificationCode=

InstallableLanguages=1

InstallDate=

LanguageEdition=

ListOfLanguages={"en|US|iso8859-1"}

Manufacturer=American Megatrends Inc.

Name=2.05.0250

OtherTargetOS=

PrimaryBIOS=TRUE

ReleaseDate=20150410000000.000000+000

SerialNumber=<redacted>

SMBIOSBIOSVersion=2.05.0250

SMBIOSMajorVersion=2

SMBIOSMinorVersion=7

SMBIOSPresent=TRUE

SoftwareElementID=2.05.0250

SoftwareElementState=3

Status=OK

TargetOperatingSystem=0

Version=OEMA - 1072009

According to BIOS /?  there is a BIOS Create function but no Set function.  I don't know what that implies exactly but I would be hopeful that Create might have the same effect as a Set (or perhaps Delete + Create would).

HTH

Robert

I think that I'm getting to the bottom of the problem.  I recently did an update to the system BIOS and somehow the BIOS I loaded was for a Surface Pro 4.  If I look at the system information, the system thinks that it is a 4.  Now the unit thinks that it is a Pro 4 but the mounted drivers are for a Pro 2, so when it tries to load a driver I get "Driver not migrated" messages.

My question now is how do I reload the correct BIOS.  I've been to several sites and they all say that you cannot manually load a BIOS image.  I've downloaded the files, just don't know where to go from here.

won't detect an external monitor, but the monitor works.

HDMI?  FWIW since W10 FCU I have had to switch to VGA (actually using an HDMI-VGA converter while keeping the Surface HDMI adapter.)  Also, I switched to using Intel's generic video driver.  However, you have just reminded me that I don't know if either of these are still necessary since 1803 (which only happened recently for my Surface 2 Pro).

can't refresh the drivers because the system indicates that they are up to date. 

That sounds like a better technique should be tried.  E.g. imagine that you have the SP2 drivers still installed, so then you can override Windows 10 choices by using the Browse my computer... Let me pick... method.  Similarly this is the way to go for the Intel generic driver, after downloading and expanding its .zip file (not using an installer).

How did you manage to get your machine looking like an SP4?  That sounds strange.  FWIW this is all I see using WMIC with the Screen cover attached but not operational (because I keep my Tablet always in Portrait orientation).

wmic:root\cli>sysdriver where (Name like "Surface%") list brief

DisplayName                                Name                      Started  State    Status

Surface Accessory Device Service           SurfaceAccessoryDevice    TRUE     Running  OK

Surface Integration Driver                 SurfaceIntegrationDriver  TRUE     Running  OK

Surface Touch Cover Filter Device Service  SurfaceTouchCover         TRUE     Running  OK

This might help too

wmic:root\cli>csproduct get Name, Version

Name           Version

Surface Pro 2  1

FWIW I haven't tried the SDT for a while but the last time I did it would not recognize my SP2.  I remember looking at a .ps2 file and seeing that it explicitly inhibited support.  Maybe your SP4 stuff was a way to fix that issue.  (I had used one much earlier and saw that it would try to update drivers.)  Again, strange.  I may try it again to confirm my recollections.

FYI

Robert Aldwinckle