Windows feature update to 20H2 failed error code 0xc19001e1

Aman Saha 21

I am using i3 4150, 4gb ram, 1tb hdd. Windows update shows that My pc is upgradeable to 20H2. Currently I am running 1909 64 bit. Time of update all are fine but when start install works still fine till 90% then suddenly it stop, staying that you're up to date, no restart showing.

Answer accepted by question author

Anonymous

2020-10-24T20:11:09.553+00:00

As far as I know 20H2 hasn't officially released so I'd suggest asking for help in dedicated insiders forum here.
https://answers.microsoft.com/en-us/insider/forum/insider_wintp

--please don't forget to Accept as answer if the reply is helpful--
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

9 additional answers

Aman Saha 21 Reputation points

2020-10-25T15:58:30.647+00:00
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
k b 1 Reputation point

2021-02-10T18:03:15.583+00:00
Thanks for the answer, JoyQiao-MSFT. Your solution almost solved my problem, but not completely :( It used to be stuck at 61% through the native windows update, now it's stuck at 99% (been 14-16 hours).

A few comments:

Before the 0xc19001e1, my update was stuck at 61% forever.

winver did show that I was running the 1909 version.

Troubleshoot update did not find anything wrong.

I did not run scannow or restore health, and did not have a firewall.

I did not know how to do a "clean boot"

When I downloaded the updater from the link that you highlighted and ran it, it took a while to download and start updating. At - I think around - 70%, it said it could not install, as another update process was running. I did a bit of searching on the net, and ran the following commands (in admin cmd line) to stop the running update:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

(the first one didn't succeed in stopping the service on its first try. Then I tried the second command, which was successful, and then the first, and this time it was successful. The last two lines said that the service was not running).

Then I again ran the stand-alone updater that you linked to and highlighted.

Its progress went from 0-94% relatively quickly, and then it was stuck for a long time at 94%. Very slowly it went up to 99%, but then stuck there.

Any help would be appreciated.

Thanks!
Please sign in to rate this answer.
B. Day 1 Reputation point

2021-03-25T07:35:50.387+00:00

I have had the same problem for over a week now. Can someone please help with finding a solution... please... Thanks!

pauliom 1 Reputation point

2021-03-26T08:56:58.06+00:00

Same for me too, this update is terrible. Even if I accept that after 30 years of Windows we still can't have a seamless update, what I can't accept is why there isn't any useful progress & diagnostic information to help resolve these problems. The upshot is that after a week of trying various workarounds I still can't upgrade and the only solution seems to be a clean install of Windows - well that's not good enough, it will take ages to install and then ages, if you're lucky, to find all the apps/keys/licenses/etc . "Sorry we can't repair the puncture in your car you'll have to wait a month for a replacement car and you'll be without a car too".

Vit 1 Reputation point

2021-03-29T14:35:17.723+00:00

Similar problem ....errors 0xc19001e1 and 0X080078652 while trying to instal windows update version 20H2.
Installation stops at 61%...another recommended method stopped at 90% of installation preparation
I have also tried: "net stop wuauserv, net stop bits, rd /s SoftwareDistribution, net start wuauserv, net start bits" and no result.......................
Can anyone help?
THX

zazoucsh 31 Reputation points

2021-04-05T14:26:31.95+00:00

Hello,
I have had the same issue with 61% stuck (error 0xc19001e1) installing version 20H2 since 1909.
I have a 6 years old ASUS Zenbook laptop that comes with Conexant Audio HD oem.
While browsing the forums I discovered that the Conexant Audio HD drivers could be the cause of the crash.
I downloaded SetupDiag.exe from Microsoft: https://learn.microsoft.com/fr-fr/windows/deployment/upgrade/setupdiag#text-log-sample
After a new attempt to update the 'setupact.log' file was interrupted on Conexant Audio HD and therefore confirms the origin of the blockage.

The solution was to replace the Conexant drivers with those from Microsoft: High Definition Audio Peripherals (which also work well)

I then directly relaunched the update from version 1909 to 20H2 and everything went well.
The Conexant drivers were reinstalled and work fine on the 20H2!

What had no effect:
Uninstall Conexant Audio HD because it recharges at least on restart
Disable Conexant Audio HD Drivers

BlinOnze 1 Reputation point

2021-04-10T14:11:23.247+00:00

Hi Zazoucsh-8159

I have a 7 year-old ASUS Netbook so have high hopes of your fix solving my long time problem. I'm another 61 percenter. But I would be most grateful if you could explain "REPLACE the Conexant drivers" if uninstall has no effect. I'm probably just being thick!

Thanks

zazoucsh 31 Reputation points

2021-04-11T13:31:51.957+00:00

Hi BlinOnze-7223,
In the Device Manager open the line 'Sound, video and game controllers'.
Update the drivers of 'Conexant SmartAudio HD':
Select 'Go through my workstation to search for drivers' and then 'Choose from a list of drivers available on my computer'.
Then select the 'Hight Definition Audio Device' model.
Ignore the update warning and validate the driver's intallation.
After a restart the new drivers (from Microsoft) remain and work for me.
Thus Conexant drivers are no longer used for sounds, games but also audio inputs and outputs.
After this drivers update the 61% installation blockage disappeared and the switch to the 20H2 version was done without any problems.

Ms 1 Reputation point

2021-04-11T18:51:06.987+00:00

Hat funktioniert!!!!!!!!!!!!!!

SmilePls 1 Reputation point

2021-04-12T02:13:49.223+00:00

Hi BlinOnze-7223,,

i have same issue of 61% stuck in lenovo ideapad 310 laptop. i also have same conexant audio drivers

i am trying to replace drivers as above, but have following doubts (i am new in this)

should i change drivers for both microphone and speakers ?

i have options of following drivers 1. audio endpoint 2. generic software device . i do not see any high definition audio device driver option here.
what to do now ?

can you please guide.

BlinOnze 1 Reputation point

2021-04-12T16:29:20.553+00:00

Thanks greatly for your help zazoucsh-8159. Subtle differences of course. The audio drivers on my ASUS X200CA appear in Device Manager under the heading “Audio Inputs and Outputs” and there were no alternative drivers to the “Audio Endpoint” showing, that were found in the search of my device..

I therefore downloaded a “Microsoft High Definition Audio Device” from the internet. This turned out to be Realtek (which I have on my desktop). I uninstalled Conexant, installed Realtek, and updated the driver to “High Definition Audio device”. (Incidentally, there was a huge improvement in audio quality). After restarting to set off the W10 updates, a quick check showed that Conexant had re-installed (as you said) and Realtek had vanished. I repeated, this time deleting Conexant from the Program Library. This appeared to work.

BlinOnze 1 Reputation point

2021-04-12T16:30:46.21+00:00

zazoucsh-8159 (continued).

This time, three W10 updates, which had failed for weeks, were successful, but the 20H2 update stalled on “installing = 0%”. This lasted all day despite numerous restarts and shutdowns. Eventually a pop-up appeared saying something like “this version was about to expire, you must restart”. Clicking the <Restart> button offered, set off the update immediately . . . . . . then there were six hours of my life that I will not get back! But it was successful.

However, checking now shows that Conexant has returned. The “Audio Endpoint” driver has resurfaced (but also “Generic software device” has been added) . . . . AND there are FOUR new W10 updates “pending” ARGHHHHH!

BlinOnze 1 Reputation point

2021-04-12T16:31:46.51+00:00

Hi SmilePls-6079. Very much a case of the blind leading the blind, I fear. I found that changing the driver on speakers automatically changed it for the microphone. I now have (see above/below?) both Conexant and Realtek installed on my netbook. Previously only Conexant and only “Audio Endpoint” was offered. Now with both installed, I am being offered both “audio endpoint” and “generic software device”. I am guessing the latter IS Realtek (delivered to me as “Microsoft’s HD audio device”) although it was shown in the update driver dialogue as “ high definition audio device” when first installed. After the hassles of the last couple of days, I am loathe to change to the generic to see what happens – audio is working!

SmilePls 1 Reputation point

2021-04-12T16:32:32.017+00:00

@zazoucsh your solution perfectly worked. thanks for detailed reply.

joseph oliver 1 Reputation point

2021-05-02T02:20:17.637+00:00

Thank you, thank you, thank you and again thank you. I have been having the same problem for at least 2 weeks and after many attempts to fix it, I stumbled across your entry. My attention was grabbed by the Asus/Connexant combination and I thought, what the hell, I'll give it a try. After doing exactly as you said, the new build installed no problem. Great job and detailed instructions.

Rasta Kingdom 1 Reputation point

2021-06-02T21:32:45.607+00:00

@zazoucsh

Hello Zazoucsh, you're a true hero and I really mean it. You nailed it down with one single word: "REPLACE". Honestly, I've been through hundreds of pages about the stuck at 61% from 1909 to 20H2 and there is so much nonsense written compared to your simple "tip", I could get so mad at all those so called "M$ Experts". It's always the same that comes up ... sfc, DISM, safe mode, resetting the Update components, stop/start the Update service, clean boot etc. ... that's all so useless, but still, they all keep repeating themselves. Surely, the "Media Creation Tool" option will work, but I was just not willing going that way.

OK, than well they also come up with the root cause which is that buggy "Conexant Audio" driver. But they all say uninstall and/or disable, but none of them says that this crazy driver somehow always manages to re-install itself automatically after reboot.

Rasta Kingdom 1 Reputation point

2021-06-02T21:38:36.977+00:00

@zazoucsh (continued)

When I did my first run after removing that driver, I passed the 61%, but in the final stage of the upgrade it got re-installed again and the upgrade failed and set my Windows back to 1909.

I was looking out on how to permanently delete that driver, but that seemed tricky & including some registry hack. I thought, that can not be it, there must be something more simple. Than I came across your post and when I read: "REPLACE" and ... "What had no effect: Uninstall Conexant Audio HD because it recharges at least on restart & Disable Conexant Audio HD Drivers", I thought, oh hey, that sounds promising and indeed, it worked like a charm. Even after some 4-5 reboots, the generic driver is still in place. Fingers crossed.

So really thank you a million times for being simple and having shared your solution. Well done. Good Job. Really amazing. Just the way I like to see solutions. Take good care and only the best.

zazoucsh 31 Reputation points

2021-06-07T15:05:36.45+00:00

Hello,
Thank you for those friendly answers.
Just for information: after installing the 20H2 I found for my ASUS laptop, on the manufacturer's website, an update for Conexant Audio Driver dated April 22, 2021 - Version V8.66.95.70. I don't know if this version would have avoided the problem of blocking updates to 20H2 but, after so many hard days, if so, its release is very late!

Подосенин Алексей Александрович 161 Reputation points

2021-07-12T10:41:47.617+00:00

works like a charm
many thanks

Dutchy 1 Reputation point

2021-07-14T17:42:13.903+00:00

really big thanks to you!!! finally i was updated my windows 10 20h2 after try and try many videos from youtube and found your comment. Thanks alot
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
SmilePls 1 Reputation point

2021-04-12T16:29:30.533+00:00

zazoucsh-8159 your solution perfectly worked. thanks for detailed reply.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
BjornW14 1 Reputation point

2021-04-20T13:00:56.093+00:00

Before the 0xc19001e1 error, my update (from 1909 to 20h2) was also stuck at 61%. (running Lenovo G505s)
I also tried with setting soundcard to microsoft, but I got the errorrmessage "no speakers found."

Here I found a second workaround: I inserted an USB-speaker/mic-adapter connected to an old headset.
Then it worked to replace the conexant driver with Microsoft HD-driver. The headset automatically become
the primary soundchannel when connected.

Now I am running 20H2.

Just one minor problem: I didnt get the "Whats new walk through" for Windows 10 v2004
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows feature update to 20H2 failed error code 0xc19001e1

9 additional answers

Your answer