Toshiba C50-H-103 SCCM OSD issue Win 10 x64

[Tinribs]

Hi all

Firstly I have searched and found (and read) this thread:

Toshiba C50 :Laptops will not boot PXE - Page 3 (edugeek.net)

 

My issue is similar but annoyingly different. I can get the laptops to PXE and start the WINPE bit. Everything runs fine until the first reboot. Once that happens I get the Dynabook logo and the spinning circles then nothing. I left the laptop like this overnight and no change the next morning. If I go into the safe mode options and choose any version of safe mode the same thing happens except that the spinning circle doesn't appear. I tried debugging and bootlogging but no logs appear and no change in the boot. If I choose to disable signed driver enforcement the circle stops spinning and then nothing happens.

The laptop is set for UEFI boot and the drive is formatted OK (going via Diskpart whilst the first bit of the TS is running). All of our other laptops (different makes) use UEFI and work fine with the same image

I could change our DHCP to do a non-UEFI boot and format the drive as legacy but that would mean chopping and changing the DNS settings whenever this laptop model needs rebuilding - annoying as everything else in the school uses UEFI.

I have read that there is a way to set DHCP up so that you can boot to both at the same time but the changes it suggests never worked for me.

Toshiba no longer provide dedicated SCCM driver packs to download so I've had to cobble drivers together. I first got the drivers from a working (OEM) Windows installation using this method:

"Go to C:\Windows\System32\DriverStore\FileRepositorySort by date.All of the most recent folders (there should be a group) contain the drivers that Windows itself doesnt include.Copy these folders and import them to SCCM."

 

I then manually downloaded the latest drivers from the Toshiba support site and imported those...

 

Still no joy.

 

So with a laptop that will not boot into Windows in normal or safe mode, will not log debugging or boot logging how do I go about troubleshooting the problem. The only thing I can see is that the SMSTS.log file suggests this is all failing before the driver packs are installed so that makes this even more odd....

Any help would be nice!!