Windows 10: Windows 10 failed update 2004 error 0xc1900101/0xc1900101-0x20017

Lenovo Ideacentre 310s-08asr amd a9-9245 radeon r5 compute cores 2c+3G

8Gb Memory

879Gb free on hard drive

Razer Chroma keyboard

Windows Defender used no 3rd party

Have tried all the below and every occasion I get error 0xc1900101 or 0xc1900101-0x20017 when media creation tool is used

Have installed windows 10 to a bootable usb device 16gb

bios set so that usb is primary boot device over hard drive

Reset computer

screen momentarily shows windows logo then there is a flicker and the normal lenovo boot screen is displayed

then computer tried the usb again and the same flicker and back to the lenovo screen again

computer keeps this loop going until the usb is removed and computer then boot normally.


Previously tried windows update to no avail constantly getting error 0xc1900101 but using windows media creation tool I get error 0xc1900101-0x20017. I have installed build 2004 on my 5 year old HP and 7 year old HP laptop both times on the first occasion.

I am wondering now if I it could be the secure boot in the BIOS that could be the problem.


Have run lenovo vantage and it reports system up to date

Have run lenovo system update and it updated the AMD onboard graphics driver, that reported no other updates are required.

Ran the AMD drivers and supported and that updated drivers and AMD software

System has Office, Canon drivers and software for TS8351 installed, Google Earth, Firefox, Chrome, Thunderbird and IMVU installed.

The computer has been taken back to 1903 its original format and even with nothing added resulted in error 0xc1900101 and 0xc1900101-20017 using media creation tool. The system has successfully updated to 1909.

Update troubleshooter this time reports an issue has been detected. When you look at the details it says "check for windows update issues"

Then says "resolve windows update issues - completed

Then WaaSMedicService

Issues remediated by: EnableUUPScanPlugin.

Then detection details

IsPostback_RCUpdates : IsPostback: False

WaaSMedicService: Issue found by: EnableUUPScanPlugin

IsPostback_RC_PendingUpdates: IsPostback: True

Service Status

Problem with BITS service: The requested service has been started. More help is available by typing NET HELPMSG 2182

BITS troubleshooter reports that it cannot find a problem

Have tried a clean install but computer did not boot from usb, found out boot order in BIOS had to be changed so made usb number 1 in priorty

Then tried the clean install again and although the computer tried to boot from usb I got the windows symbol but then before startup could start I get a "flicker" and then the computer tries to boot from the hard drive before trying the usb and so on in a loop. Removal of usb and the computer boots as normal.

I even tried to update from recovery to 1903 to 2004 via media creation tool and that failed but did not give an error, here I used the "download tool now" option, then chose to "upgrade this pc now". When the windows update assistant downloaded is run I am told that the computer is compatable.

The install starts does everything it should but on restart the computer tries to load windows again and again before I am dumped to the lock screen after at least 8 minutes and back to 1909.

It seems having watched a video on You Tube that I need to change in BIOS that secure boot was on and to change that to off. I was wondering if the secure boot being on could be part of the update problem?

Have tried Lenovo support but they insist that "this is out of our support scope."

:)

 

Windows 10 Upgrade Failed - Error: 0xC1900101 - 0x20017

There is a log missing





Setuperr


Maybe it holds the clue.


Did you try the list of quick fixes which include removal of third party AV.

 

Windows 10 Upgrade Failed - Error: 0xC1900101 - 0x20017

Your code





Try running the setupdiag exe listed on this page. Hoping it id's drivers.

https://docs.microsoft.com/en-gb/win...dy_UpgradeTips

 

0xC1900101 - 0x20017 happens every time I install.

If I recall correctly, this worked for most people.
Windows 10 upgrade fails with 0xC1900101-0x20017 -- Steps to Fix - Microsoft Community