So I have a friend who builds multiple systems and he told me that when he is in sysprep mode / OOBE and tries to run any executables, nothing happens, he even tried the latest cumulative update today but no luck. if he exits sysprep mode and creates a normal account, everything works fine he want to deliver these PCs to people so he'd prefer to do it in sysprep mode to give them the Out Of Box Experience any suggestions to solve this?
I've had no issues in Audit mode. As per every other build, drivers & software install fine. Recovery & Sysprep work fine. Has your friend made any mods/integrated anything? Something with his setup sounds broken...
thanks for the confirmation, I will tell him to create the installer USB with the media creation tool this time rather than burning the ISO he downloaded from MSDN using Rufus
If he's downloaded the ISO from MSDN & made no mods then it should be all good. Installation media wouldn't make a difference either. Don't know what the issue could be. Is he putting in a motherboard drivers DVD? Perhaps something from there is stuffing it up...
What has the used method for creating the bootmedia to do with the "problem". Me thinks the "butchering" of the install is the cause of the "problem".
If it is succesfully installed, the method of creating the install media is unimportant. The "problem" is what is put on the usb stick.
after clean instillation of windows 10 15063, i have the same problem can’t run some executables in built-in administrator account when the pc not connected to internet,
Installed 15063 in a vm, went into audit mode, disabled LAN and ran Office 2016 setup.exe and it installs just fine.