Surface Laptop 7 for Business Intel Driver Pack fails to install after rebooting

[Justin-Swets]

The Surface Laptop 7 for Business Intel driver pack is failing to install after rebooting the device. This is after OSDCloud has been run successfully. Will upload install log.

[MichaelEscamilla]

What OS are you applying when it errors? Does it work a different OS version?

[Justin-Swets]

Hello Michael,

David is aware of this issue as he asked me to open a new issue. He completed adding the driver pack to OSDCloud and asked that I open a new issue for the drivers not installing. This issue is happening on Win 11 24H2. I have uploaded a log and screenshot. Thanks for the help.

SurfaceLaptopforBusiness7thEditionwithIntel_Win11_26100_25.013.32214.0.msi-20250303T141320.log.txt

[MichaelEscamilla]

Ok gotcha, I see from over on Discord. I'll follow up with him.

[OSDeploy]

I worked on this last night. I tried to do an Admin install (msiexec /a) and this ran for about 30 minutes like this

Rebooted to WinPE to review the log and this is the output

So it's not looking great. I'll try again tonight to unpack in OOBE which should work, but please don't expect a solution for days at the earliest, if possible.

[OSDeploy]

I believe the solution may be to just use Microsoft Update Catalog to at least get the Disk and Net drivers and update in OOBE.

[Justin-Swets]

I did test the Microsoft Catalog Update and it installed a bunch of drivers but Keyboard and Mouse still did not work. I updated my OSDCLoud USB drive, is there a way to force it not to use the driver pack if using the Start-OSDCloud command? I will also log a case with my Microsoft Surface Rep. Thanks for all the help, really appreciated.

[Justin-Swets]

I engaged Surface support

[Skeb1ns]

@Justin-Swets

Got an update? Currently having the same issue during a test with a 7th gen that will replace our 6th gens in due time.

[Skeb1ns]

This is also an issue for the Surface Studio 2 laptops btw.

[OSDeploy]

The solution may be to install the MSI during OOBE ... I'll have a solution in a few weeks to test this out

[Skeb1ns]

Check. Is there a way for now to exclude the driverpack install on these devices?

I will modify setupcomplete to install it during OOBE like you suggested. (I'm afraid that I can't wait a few weeks and I totally understand that it can take a while from your side 😄)

[OSDeploy]

If you're using the GUI, then change this to not use the DriverPack.
If you're using the CLI, no.

[everydayintech]

I was able to disable the DriverPack like this using $Global:MyOSDCloud:

$Global:MyOSDCloud = @{
    DriverPackName = 'None'
}
Start-OSDCloud @OSDCloudParams

[Skeb1ns]

I can confirm that installing the driver pack during OOBE works fine.

I've done the following to work around this issue until the OSDCloud module has a proper fix:

• I check the device model during start of the main script (I'm using a custom script with a gui at the front) and add the DriverPackName value "None" to the $global:MyOSDCloud hash table for the affected models to skip the regular Driver Pack installation.
• After the OSDCloud process is finished I copy the preloaded driver pack .msi based on the model to C:\OSDCloud\Temp (I first dropped it in C:\Drivers but that triggers the regular Driver Pack installation).
• Added a Start-Process -FilePath msiexec -ArgumentList "/i ""$pathDriverLocal\$driverPack"" /qn /norestart /L*v ""$pathDriverLocal\$driverPack.log""" -Wait to my SetupComplete script (which is placed in C:\OSDCloud\Scripts\SetupComplete so that OSDCloud can pick it up. Populate the variables with the path and driver pack name.

Done!