Cannot get bootable usb windows 10 2004 to work

Anonymous
2020-09-13T20:35:32+00:00

Have rest the computer yet again for the umpteenth time

Have had one advisor on here saying my pc might not be compatable but it is only 1 year old

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

8Gb Memory

875Gb free on hard drive

Razer Chroma keyboard

Windows Defender used no 3rd party

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

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. These proved not to be a problem as my 5 year old HP computer updated to 2004 without any problems.

Tried again and error 0xc1900101 occurred yet again.

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.

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

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

44 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-17T05:05:54+00:00

    OK. But I don't know why you delete them. It kills Shift+Restart to delete them.

    Anyway, here's hoping turning off Secure Boot &/or Fast Boot will get OP to boot. I've seen it mentioned before, but never had to do it myself. Then, afterwards, he should turn at least Secure Boot back on, which is a security advantage of a UEFI install. I think it fights off root kit viruses.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-17T03:59:10+00:00

    Hi,

    You are correct about the size of the Recovery.. I must be cross-eyed from lack of sleep..

    Mine are all in the area of 500mb-550mb.. I just deleted one created by today's new Insider Build..

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-17T01:55:38+00:00

    His recovery partition is only 1000 MB near as I can see through my cataracts. Mine is 848 MB.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-17T00:21:46+00:00

    Hi,

    Your screenshot shows a huge Recovery partition of 1000GB at the end of your OS drive...

    This is not normal.. They are normally around 500mb or so.. This may have happened due to the drives configuration at installation.. This is unrelated to your current issue though..

    In addition to Secure Boot, you might look for Fast Boot and disable it as well..

    Was this answer helpful?

    0 comments
  5. Igor Leyko 112.4K Reputation points Independent Advisor
    2020-09-16T21:30:25+00:00

    The screenshots show typical picture and say nothing about problem.

    Try to turn off secure boot but use UEFI boot.

    Was this answer helpful?

    0 comments