search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
629 stars 282 forks source link

Bug - Surface 6 - Suggested solution #265

Open viriio opened 3 years ago

viriio commented 3 years ago

Running script version:4.0.2

When creating the Surface 6 Driver package it looks to create a linebreak within the driver package causing it to detect on all Surface devices are the driver package.

Example a Surface Pro 5 doing a check on the Surface Pro 6 driver package.

If you want to replicate create a Surface Pro 5 and Surface Pro 6 driver pack. The 6 in particular seems to have a weird character.

Around line with "foreach ($SystemSKUItem in $DriverPackageInputArray) {" may need to detect if its not blank or contains some characters.

Output of: $SystemSKUTable

Name Value

Surface_Pro_6_1796_Commercial False Surface_Pro_6_1796_Consumer False True

Last entry is blank but returns true causing it to detect as a false-positive.

shaikh441 commented 3 years ago

Hi, Currently having issues with Surface Pro 6 and 7 using the latest tool and script. Log attached, shows the driver tool is detected all the Surface packages as a match and then as a result can't install.

Thinking it may be to do with what you have stated above. Can I ask where do I need to make changes?

Thanks ApplyDriverPackage (1).log

Ar5had07 commented 3 years ago

Hi, Currently having issues with Surface Pro 6 and 7 using the latest tool and script. Log attached, shows the driver tool is detected all the Surface packages as a match and then as a result can't install.

Thinking it may be to do with what you have stated above. Can I ask where do I need to make changes?

Thanks ApplyDriverPackage (1).log

We are all in the same boat. We are all having the same issue with Surfaces. And we are all waiting for a fix.

Jabbaxx commented 3 years ago

The new version 4.1.1 fixes it here. It was the empty driver which i also see with the new one if i debug it, here you see that drivers list sometimes is empty