Windows 10 will not update anymore; stuck in 1909

Anonymous
2021-05-17T01:54:45+00:00

TLDR: Update page shows "Your device is missing important security and quality fixes." for the last one week. It is still in Version 1909 Build 18363.1556.

Long story: It has been promising Feature update 2004 for quite a long time but did not really deliver. However, I had been getting regular security and quality minor updates. Around a month ago, when I started getting the end of service notifications for 1909 I tried to force updates by hitting "Check for updates" and it tried doing a huge download for 20H2. I think after a long installation process it aborted around 45% and rolled back. Tried a couple of times and the same result.

Now, I did a few methods suggested in various forums and Microsoft support sites like running update troubleshooter, a scan, running commands as administrator, setting right a few registry entries etc. I even rolled the last cumulative update for 1909 KB5003169 and it got reinstalled on the next reboot but the "Your device is missing important security and quality fixes." returned.

I am worried because I will be missing out important security updates given that 1909 has reached the end of service.

UPDATE: The error code against the update 20H2 update is given as 0xC1900101

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

43 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-26T14:24:04+00:00

    Hi Sumit, 

    I gave a chkdsk command but Windows had to do it during a restart. Here is the result. (Chkdsk found some 8 kB of bad sectors, highlighted in red.)

    Log Name: Application Source: Microsoft-Windows-Wininit

    Date: 2021-05-25 21:27:21

    Event ID: 1001

    Task Category: None

    Level:

    Information Keywords:

    Classic User: N/A

    Computer: xxxxxxxxxxxxxxxxx

    Description: Checking file system on C:

    The type of the file system is NTFS.

    Volume label is Windows.

    A disk check has been scheduled.

    Windows will now check the disk.

    Stage 1: Examining basic file system structure ... 1410560 file records processed.

    File verification completed.

    17200 large file records processed.

    0 bad file records processed.

    Stage 2: Examining file name linkage ...

    89082 reparse records processed.

    1763082 index entries processed.

    Index verification completed.

    0 unindexed files scanned.

    0 unindexed files recovered to lost and found.

    89082 reparse records processed.

    Stage 3: Examining security descriptors ...

    Cleaning up 2202 unused index entries from index $SII of file 0x9.

    Cleaning up 2202 unused index entries from index $SDH of file 0x9.

    Cleaning up 2202 unused security descriptors.

    Security descriptor verification completed.

    176262 data files processed.

    CHKDSK is verifying Usn Journal...

    39193840 USN bytes processed.

    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.

    956337151 KB total disk space.

    745734432 KB in 858209 files.

    520996 KB in 176263 indexes.

    8 KB in bad sectors.

    1554007 KB in use by the system.

    65536 KB occupied by the log file.

    208527708 KB available on disk.

    4096 bytes in each allocation unit.

    239084287 total allocation units on disk.

    52131927 allocation units available on disk.

    Internal Info: xxxxxxx

    Windows has finished checking your disk.

    Please wait while your computer restarts.

    Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 1001 0 4 0 0 0x80000000000000 99105

    Application xxxxxxxxxxx

    Checking file system on C:

    The type of the file system is NTFS.

    Volume label is Windows.

    A disk check has been scheduled.

    Windows will now check the disk.

    Stage 1: Examining basic file system structure ...

    1410560 file records processed.

    File verification completed.

    17200 large file records processed.

    0 bad file records processed.

    Stage 2: Examining file name linkage ...

    89082 reparse records processed.

    1763082 index entries processed.

    Index verification completed.

    0 unindexed files scanned.

    0 unindexed files recovered to lost and found.

    89082 reparse records processed.

    Stage 3: Examining security descriptors ...

    Cleaning up 2202 unused index entries from index $SII of file 0x9.

    Cleaning up 2202 unused index entries from index $SDH of file 0x9.

    Cleaning up 2202 unused security descriptors.

    Security descriptor verification completed.

    176262 data files processed.

    CHKDSK is verifying Usn Journal...

    39193840 USN bytes processed.

    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.

    956337151 KB total disk space.

    745734432 KB in 858209 files.

    520996 KB in 176263 indexes.

    8 KB in bad sectors.

    1554007 KB in use by the system.

    65536 KB occupied by the log file.

    208527708 KB available on disk.

    4096 bytes in each allocation unit.

    239084287 total allocation units on disk.

    52131927 allocation units available on disk.

    Internal Info: xxxxxxxxxxxxxxxxxxxxx

    Windows has finished checking your disk. Please wait while your computer restarts.

    Was this answer helpful?

    0 comments
  2. Sumit 44,436 Reputation points Volunteer Moderator
    2021-05-27T02:47:47+00:00

    It is not clear to say if it is behind the cause of the update failure. The options are pretty limited in your case I am afraid - I can't see anything else besides a clean install of 21H1 that removes all installed apps and files(which you can backup before though). If you need instructions, let me know.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-05-27T02:58:43+00:00

    Hi Sumit,

    Thank you again.

    Just to be sure, will a clean install not face this write protection when installing drivers? If so, please provide me the instructions.

    Was this answer helpful?

    0 comments
  4. Sumit 44,436 Reputation points Volunteer Moderator
    2021-05-27T15:16:02+00:00

    Yes, it would not as per my experience.

    Please backup your data as the first step to a different drive.

    Please create a USB installation drive: https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html

    My fellow moderator colleague Greg has written extensively about CI here:

    Clean Install Windows 10 - Microsoft Community

    Before doing a reinstall, appreciate if you log a Feedback Item and share the link with me. I would send it to the Windows team for further investigation. In attach files option in the Hub, attach the setup logs too

    https://answers.microsoft.com/en-us/insider/forum/all/how-to-add-a-feedback-in-the-feedback-hub-and/0c60e72d-d810-40e2-bdc9-50ce5ab3bb9f

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-05-27T15:26:20+00:00

    Can I do this USB in a different computer running windows 10? One of things I have noticed before is that this computer corrupts any USB I try to format or when I try ti create a boot able drive.

    Was this answer helpful?

    0 comments