Windows 10 No Post-Setup When Installing On SSD

S

slYx

New Member
Hello guys,

I am using NTLite to deploy Windows 10 unattended. In the past, everything worked fine. But now I got to install some new laptops.
They all have a SanDisk M.2 SSD 256 GB drive. My problem is now, that everythings works fine but the post-setup.
I want to install Firefox, WinRar and some more tools after the Windows 10 installation. But none of these tools are installed afterwards.
I am installing from a USB-Drive. I already tested my Install-USB-Drive on other laptops with a normal HDD, there everything works as wished.

Now I am really confused and I don't know how to resolve this problem. I hope someone in this forum can help me with my issue.

Greetings,
slYx
 
Hi,

is it just skipped or the setup gets stuck at the end?

If skipped, make sure the files are actually there, that it is the same USB stick that worked (.\Sources\$OEM$ folder on it with content deeper).
If you now use an OEM product key, it can skip the setupcomplete.cmd execution by MS design, to workaround that under the Unattended page enable "OEM SetupComplete" in the toolbar.
And lastly if it gets stuck, here is how to debug it.

Let me know how it goes.
 
Hi,

it just skipped the setup. No warning, no error, nothing. It just didn't anything for the post-setup.

I already checked the files, everything is there, I am using the same USB-Drive.
 
Use a PE boot disk or other method to check SMART on the drive. I usually use CrystalDiskInfo. Look for Current Pending Sectors or Uncorrectable Sectors. I had similar "strange" issues with SanDisk drives and data not being written / erased, bad flash or controller. Really strange stuff with those drives! A few of the drives I was able to change the flash (low-level) and it fixed the problem. You just have to identify the flash controller and NAND / FLASH type & layout. You can get the config files and software from here: http://www.usbdev.ru/f/index.php?board=11.0
 
@slYx please read the rest of my message, OEM SetupComplete option might be the solution, it's a known Windows limitation.
 
This issue may also happen on Western Digital ssd's because they own sandisk and are prolly using WD branded sandisk hardware.
 
You must log in or register to reply here.
Back
Top