This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 13%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
Hello All,
We are having MECM 1910, I am try to deploy Windows 10 1909 OS using Task Sequence. I have Included multiple device model Drivers to Task sequence. Task sequence is deploying successfully.
****But Drivers are installing after First Login, Its taking around 10 mins to install the driver and its prompting for Restart.***
In the Task sequence I have already added the Restart task after driver installation. Still I am facing this problem. Driver should install before user login to the Devices, But its not happening.
Please help me to fix this issue.
May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
How are you applying drivers?
Have you confirmed that the driver that is being installed at first logon is something you were installing during the TS? Or is it a newer one coming down via Windows Update / Windows Store? Perhaps after OSD, disconnect device from network right away to ensure it's not pulling something down in the background. Then logon and see if you have the same behavior.
I am applying driver After OS installation in Task sequence step.
I have imported the SCCM Driver pack of each Device model driver from OEM site and created the Driver package. It’s added in Task sequence individually.
There is Restart Task after driver installation steps.
There should not be a restart step after the "Apply Driver Package" step, the entire process is done while in WinPE. Once in WinPE. there should NOT be a restart until the "Setup Windows and ConfigMgr" Step. (which that step does for you. You do not need to add any restart steps in the TS, unless you're installing an application late in the process that needs a reboot)
Does your TS match the ones in this example:
https://docs.recastsoftware.com/ConfigMgr-Docs/TaskSequence/SCCM-TaskSequence-Step-Apply-Driver-Package.html
Yes, we are installing Applications also after driver installation steps.
Does your TS match the ones in this example:
https://docs.recastsoftware.com/ConfigMgr-Docs/TaskSequence/SCCM-TaskSequence-Step-Apply-Driver-Package.html
Are you following this process:
From what you've been saying, it sounds like you are not following that process if you're adding a restart right after you're applying the driver package.
It would be helpful if you could upload an image of your TS, that would help explain your issues, along with upload a copy of your SMSTS.log.
Task Sequence steps
1) Apply Operating System
2) Join Domain
3) Install Driver Packs
4) Setup Windows and ConfigMgr
5) Install Language Pack
6) Install Additional Drivers like Bluethooth, Hotkeys and vPro Drivers
7) Install Applications and AntiVirus Software
8) OSD Results and Branding
Have you checked the smsts logs for apply driver package step. Does that say step completed successfully.
Yes, It’s showing completed successfully.
@Mahesh Gowda. S As mentioned by @Gary Blok , drivers run during winpe and there should be a reboot step mentioned explicitly in the ts before configmgr client install step. Is it possible to post the smsts logs. You can see more insights on dism logs (%Temp%\SMSTSLOG\Dism.log)
Task Sequence steps we are following.
1) Apply Operating System
2) Join Domain
3) Install Driver Packs
4) Setup Windows and ConfigMgr
5) Install Language Pack
6) Install Additional Drivers like Bluethooth, Hotkeys and vPro Drivers
7) Install Applications and AntiVirus Software
8) OSD Results and Branding
Why is the drivers in step 6 are explicitly installed seperately. This should be part of step 3 itself.
Is there is any specific reason you are installing them seperately. Are they software. If yes ,they might install while users login if active setup is configured and as a behaviour of the setup packages.
I would suggest to include those drivers as inf files in driver packages itself.
If it is required as software( hotkeys per say might be available as a software installer) , such cases please create a machine level silent installer package and use it it the task sequence.
Regards
Aravinth
---------
Please mark this as answer if this is helpful
On step 6) Install Additional Drivers like Bluethooth, Hotkeys and vPro Drivers
These are all added as software packages with silent installer.
@Mahesh Gowda. S , I feel you might have to recheck by manually installing the hotkey,vpro apps on a test device and if that is behaving so, then it's expected behaviour. I m afraid you ll not be able to change that.
However from my earlier experience I have used hotkey app installed for machine without any issues. See if you can get the right installer from vendor. Additional tip, you can add verbose logging for the app you install and see if the logs can help you out
Regards
Aravinth