Share via

SCCM Windows 10 in place upgrade stuck at 44% Build 21H2

Mario Alves 26 Reputation points
2022-01-13T09:23:44.39+00:00

Hello,
We are running some inplace upgrade tests from the build 1909 to 21H2, and with some of our models the OS update gets stuck at 44%.
After some research it seems to be a know issue, the Conexant driver blocks the process and we need to remove the driver before starting the update:

https://learn.microsoft.com/en-us/answers/questions/292086/upgrade-to-windows-10-2004-feature-update-issues-d.html

https://learn.microsoft.com/en-us/answers/questions/419914/sccm-windows-10-in-place-upgrade-stuck-at-44.html

This issue was solved on the build 20H2 but seems to be back on 21H2... strange, here are the logs:

SMSTS.log
164668-smsts-log.jpg
Volatile Reg key
164686-volatile-key.jpg
C:\$WINDOWS.~BT\Sources\Panther\setupact.log
164658-setupact.jpg
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
164669-setuperr.jpg

The problem seems to be back, for the moment the only solution I find is to remove the driver before the OS update, sadly there is no new conexant driver available.
Does anybody know if it's possible to solve this issue another way?
For the moment it seems the problem was not solved with the KB packages... and we don't really know if it will be...

Thank you in advance & has a nice day

Microsoft Configuration Manager
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jarno Tuisku 6 Reputation points
    2022-02-10T07:30:51.347+00:00

    I can also confirm this same issue. I opened a ticket to MS support, but they said that no one has reported this "stuck" with the 21H2 In-Place upgrade. I'm afraid there is no other way than to remove the problematic drivers before running the upgrade.

    I have hundreds of 1909 workstations to upgrade, so I don’t have time to wait for official MS fix. So my solution is to do a PowerShell script which is run in the upgrade TS before the IPU and that searches for drivers, which are using uci64*.dll and a file version of 7.231.3.0 or lower. After searching is done it will delete those drivers. After removing these problematic drivers, the installations are no longer stuck at 44%.

    0 comments
  2. Mario Alves 26 Reputation points
    2022-02-10T07:51:02.897+00:00

    Hello,
    Thank you for your feedback, I found out there is another driver with the same issue : HP Dock Audio, also from Synaptics....
    173054-1.jpg
    I created a ticket with HP but they don't care and asked me to update the driver & the bios...

    Now I am facing another issue, since 2 weeks... the task sequence can randomly stop with any error, sometimes I have this error code, even better there is a spelling mistake on it....
    173055-2.jpg
    Of course, no error on the SMSTSLog, it's not even up to date:

    1. C:\windows\CCM\logs\SMSTSLOG.log
    2. C:\Windows\CCM\Logs\SMSTLS\SMSTSLOG.log
    3. C:_SMSTaskSequence\Logs\SMSTSLOG.log

    It seems to come after a PS or Bat script on the task sequence...

    I don't know if it's related to the newest build from January or if there is another issue...

    I hope they will be solve soon...

    0 comments
  3. Jarno Tuisku 6 Reputation points
    2022-02-10T07:57:36.847+00:00

    I'm also having problems with this same driver:

    173081-image.png

    Because this driver includes the same problematic uci64*.dll file, my PS script will also delete this driver if it is found on the workstation.

    Edit:
    I also noticed that sometimes, for example, running a PS script crashes with an error 8004005 / 8007045b. Fortunately, there are not many of these cases. What these have in common is that the workstation has an old ConfigMgr client. Updating it to a new one (in my case 2111) will solves the problem.