There is no problem with the OSD task sequence of 23H2, but the same problem occurs in 24H2. If the laptop has its own network card, the deployment of 24H2 can be successful, but if the system is deployed using a Type-C adapter, the failure rate is extremely high. There are no clues in the deployment log of the task sequence, and this problem cannot be solved at present.I have a task sequence with 23H2 working fine.
Now 23H2 is replaced with 24H2 and task sequence process is stopped randomly ‘after’ a restart step.
Anyone have similar issues?
Sometimes task sequence completes fine, but most of the time random failures.
For us also the onboard adapter caused random issues.There is no problem with the OSD task sequence of 23H2, but the same problem occurs in 24H2. If the laptop has its own network card, the deployment of 24H2 can be successful, but if the system is deployed using a Type-C adapter, the failure rate is extremely high. There are no clues in the deployment log of the task sequence, and this problem cannot be solved at present.
I found the solution, we need to find the Type-C network card driver. Windows 11 24H2 system does not have the network card driver for Type-C devices. This leads to deployment failure.For us also the onboard adapter caused random issues.
I have a case open for it, but that also does not provide any help :-(
Does this lead to random failures also?I found the solution, we need to find the Type-C network card driver. Windows 11 24H2 system does not have the network card driver for Type-C devices. This leads to deployment failure.
By importing the driver into the corresponding device driver package, my deployment os problem was solved.
