I am trying to build a machine but it only gets as far as loading WinPE and “Initializing hardware devices..” then it falls over with the message:
“Unable to read task sequence configuration disk. For more information, please contact your system administrator or helpdesk operator.“
The weird thing is I’ve used the same USB key to build other machines without any issues.
Make sure you are not plugging a USB 2.0 key into a USB 3.0 port which was the issue in this case. Even though you can plug a USB 2.0 key into a USB 3.0 port and boot from it to load WinPE, when it comes to accessing the key once WinPE is loaded it’s unable to recognise the key so it fails.
If you look in the “smsts.log” you’ll see the following:
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\devicepath.cpp,159)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\devicepath.cpp,115)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\bootsystem.cpp,111)
ConvertBootToLogicalPath failed (0x80070003). Retrying (0)...
It then retries 29 times before you see this:
ConvertBootToLogicalPath failed (0x80070003). Retrying (29)...
bGotPath, HRESULT=80070003 (e:\nts_sms_fre\sms\client\tasksequence\bootshell\configpath.cpp,41)
GetConfigPathFixedDisk(sArcPath, sWinPEFolder), HRESULT=80070003 (e:\nts_sms_fre\sms\client\tasksequence\bootshell\configpath.cpp,206)
Failed to find the current TS configuration path
ConfigPath::FindConfigPath(sConfigPath), HRESULT=80070003 (e:\nts_sms_fre\sms\client\tasksequence\bootshell\bootshell.cpp,550)
Failed to find the configuration path.
The system cannot find the path specified. (Error: 80070003; Source: Windows)
Execution failed with error 80070003.
Different hardware vendors mark their USB 3 ports in different ways.
In this case it was a HP laptop. The USB 3.0 ports have a “SS” as part of the standard USB logo on the port marking. Plugging the key into a port without the “”SS” marking and rebooting resolved the issue.