Windows 10: Windows Update is corrupt

Discus and support Windows Update is corrupt in Windows 10 Updates and Activation to solve the problem; Hi all, My windows update was working fine until recently it became stuck on 0% for a bunch of updates while downloading. I've tried many things to... Discussion in 'Windows 10 Updates and Activation' started by shotta287, Oct 16, 2015.

  1. shotta287 Win User

    Windows Update is corrupt


    Hi all,
    My windows update was working fine until recently it became stuck on 0% for a bunch of updates while downloading. I've tried many things to resolve this:
    - Tried stopping and restarting the windows update service, but the service remains stuck on 'stopping' so I have to force kill it in cmd prompt then restart it
    - Emptied the downloads folder in software distribution
    - Ran the Windows Update troubleshooter tool, which says 'service registration is missing or corrupt'

    I'm assuming my Windows Update service has become corrupt somehow, is there any way in which I can solve this?

    Thank you in advance.

    :)
     
    shotta287, Oct 16, 2015
    #1
  2. Anne Ros Win User

    Directory is corrupt

    Hi,

    The error that you've experienced can be caused by virus infection, or physical or hardware-related issues such as hard drive corruption. As we can see from the results of the SFC and DISM scan, and even the on the result of disk check, it shows that your
    operating system is already corrupted and you need to reinstall Windows to resolve the issue. You also need to delete all the existing partitions and create new ones to remove the corrupted files.

    Backup all your important files before doing the reinstallation. Once done with the reinstallation, create two different user profile accounts. One is main user account, the other one is for backup. On the backup profile account, move all the backed up files
    there first to check and test for corruptions. If there are no corrupted files, then you can safely move all the files to the main user profile.

    Feel free to post back if you need further assistance.
     
    Anne Ros, Oct 16, 2015
    #2
  3. Directory is corrupt

    Hello, I've come across a very serious problem and would appreciate any help. I resetted my computer and used it normally, but occasionally it dies due to a BSOD. Then one day I found out that I can't use my start menu and it gives my the error: Critical
    error your start menu isn't working. we'll try to fix it the next time you sign in.

    I thought it was because of some update, then I checked for possible updates to the system. Sure enough, there is a problem there, which doesn't allow me to install the update. I followed guides online and tried the SFC /scannow and DISM /restorehealth but
    to no avail. The error states: The file or directory is corrupted and unreadable.

    I need some serious help, I don't want to reset my PC because I have a lot of apps on it and reinstalling them would be a big pain in the ass. Thank you.

    This is my logfile for the chkdsk C: /f:

    TimeCreated : 11/9/2017 8:50:40 PM

    Message :



    Checking file system on C:

    The type of the file system is NTFS.





    One of your disks needs to be checked for consistency. You

    may cancel the disk check, but it is strongly recommended

    that you continue.

    Windows will now check the disk.



    Stage 1: Examining basic file system structure ...

    Attribute record of type 0x80 and instance tag 0x3 is cross linked

    starting at 0xf70a5d for possibly 0xa46 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x3

    in file 0x9bfa is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x9BFA.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf70968 for possibly 0x1e5 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x15245 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x15245.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf7067b for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x1679e is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x1679E.

    Attribute record of type 0x80 and instance tag 0x3 is cross linked

    starting at 0xf72e85 for possibly 0x6 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x3

    in file 0x1974a is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x1974A.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf72e5c for possibly 0x29 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x19bba is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x19BBA.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf723b6 for possibly 0x1ac clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x1e423 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x1E423.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf72dd8 for possibly 0x7f clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x1e4be is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x1E4BE.

    Attribute record of type 0x80 and instance tag 0x3 is cross linked

    starting at 0xf72d1c for possibly 0xaf clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x3

    in file 0x20949 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x20949.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xeb2bfc for possibly 0x2 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x21a2f is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x21A2F.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xeb2938 for possibly 0x260 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x232d2 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x232D2.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xff4264 for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2387c is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2387C.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xff4265 for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2387d is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2387D.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xff4266 for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2387e is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2387E.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xff4267 for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2387f is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2387F.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf70667 for possibly 0x10 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x23a25 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x23A25.

    Attribute record of type 0x80 and instance tag 0x3 is cross linked

    starting at 0xf72dcb for possibly 0x5 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x3

    in file 0x23bdd is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x23BDD.

    Attribute record of type 0x80 and instance tag 0x3 is cross linked

    starting at 0xeb30c0 for possibly 0x138 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x3

    in file 0x23c56 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x23C56.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xeb7290 for possibly 0x84 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x23d3e is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x23D3E.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf70677 for possibly 0x2 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x28f49 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x28F49.

    Attribute record of type 0x80 and instance tag 0x1 is cross linked

    starting at 0xff43ba for possibly 0x3 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x1

    in file 0x2a657 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2A657.

    Attribute record of type 0x80 and instance tag 0x1 is cross linked

    starting at 0xff43bd for possibly 0x3 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x1

    in file 0x2a65b is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2A65B.

    Attribute record of type 0xa0 and instance tag 0x4 is cross linked

    starting at 0xf7643c for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0xa0 and instance tag 0x4

    in file 0x2abda is already in use.

    Deleting corrupt attribute record (0xA0, $I30)

    from file record segment 0x2ABDA.

    Attribute record of type 0xa0 and instance tag 0x3 is cross linked

    starting at 0xf76408 for possibly 0x4 clusters.

    Some clusters occupied by attribute of type 0xa0 and instance tag 0x3

    in file 0x2abdc is already in use.

    Deleting corrupt attribute record (0xA0, $I30)

    from file record segment 0x2ABDC.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf763f4 for possibly 0x10 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2abdd is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2ABDD.

    Attribute record of type 0x80 and instance tag 0x0 is cross linked

    starting at 0xf708a4 for possibly 0x48 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x0

    in file 0x2ad48 is already in use.

    Deleted corrupt attribute list entry

    with type code 80 in file 2AD48.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x8000000028fbf. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x28FBF.

    Attribute record of type 0x80 and instance tag 0x0 is cross linked

    starting at 0xf7081a for possibly 0xc clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x0

    in file 0x2ad65 is already in use.

    The attribute of type 0x80 and instance tag 0x0 in file 0x2ad65

    has allocated length of 0x7910000 instead of 0x3570000.

    Deleted corrupt attribute list entry

    with type code 80 in file 2AD65.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad66. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD66.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad67. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD67.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad68. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD68.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad69. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD69.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6a. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6A.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6b. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6B.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6c. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6C.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6d. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6D.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6e. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6E.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad6f. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD6F.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad70. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD70.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad71. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD71.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad72. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD72.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad73. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD73.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad74. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD74.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad75. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD75.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad76. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD76.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad77. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD77.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad78. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD78.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad79. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD79.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7a. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7A.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7b. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7B.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7c. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7C.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7d. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7D.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7e. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7E.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad7f. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD7F.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad80. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD80.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad81. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD81.

    Unable to locate attribute with instance tag 0x0 and segment

    reference 0x500000002ad82. The expected attribute type is 0x80.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AD82.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xff4320 for possibly 0x8 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2af2f is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2AF2F.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf708fa for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2b871 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2B871.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf708fb for possibly 0x1 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2b88f is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2B88F.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf7070b for possibly 0x7 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2b9b1 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2B9B1.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf7083c for possibly 0x20 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2bd43 is already in use.

    Deleting corrupt attribute record (0x80, "")

    from file record segment 0x2BD43.

    Attribute record of type 0x80 and instance tag 0x4 is cross linked

    starting at 0xf7085c for possibly 0x3 clusters.

    Some clusters occupied by attribute of type 0x80 and instance tag 0x4

    in file 0x2bd73 is a

    And this too:

    Chkdsk was executed in verify mode on a volume snapshot.

    Checking file system on \Device\HarddiskVolume4

    Examining 1 corruption record ...

    Record 1 of 1: Bad index "$I30" in directory "\Program Files\WindowsApps\king.com.CandyCrushSodaSaga_1.100.600.0_x86__kgqvnymyfvs32\res_output\shared\diorama\diorama07\episode20\models\interactable <0x3f,0x26685>" ...
    The multi-sector header signature for VCN 0x0 of index $I30

    in file 0x26685 is incorrect.

    73 69 6f 6e 3a 2f 2f 63 ?? ?? ?? ?? ?? ?? ?? ?? sion://c........

    corruption found.

    1 corruption record processed in 0.2 seconds.

    Windows has examined the list of previously identified potential issues and found problems.

    Please run chkdsk /scan to fully analyze the problems and queue them for repair.

    A lot more of this actually, one for windows startup menu, another for office...
     
    Hieu Vu Duy, Oct 16, 2015
    #3
  4. Windows Update is corrupt

    Cluster Head, Oct 16, 2015
    #4
  5. shotta287 Win User
    Thanks for the quick reply mate, I've tried Method 2, but when cmd tries stopping wuauserv, it just says 'stopping.....' but doesn't stop the service.
    Should I try the registry edit method?
     
    shotta287, Oct 16, 2015
    #5
  6. It`s a known issue......!

    Yes! *Smile
     
    Cluster Head, Apr 5, 2018
    #6
Thema:

Windows Update is corrupt

Loading...
  1. Windows Update is corrupt - Similar Threads - Update corrupt

  2. Windows 11 Update corrupted OS, deleted my app icons, Fn hotkeys, and OSD

    in Windows 10 Gaming
    Windows 11 Update corrupted OS, deleted my app icons, Fn hotkeys, and OSD: My computer which I've only had for like 6 months was forced into downloading/installing the latest Windows 11 update. After the computer restarted, all of my non-Microsoft app icons had disappeared. A quick online search suggested restoring to a previous save point. I...
  3. Windows 11 Update corrupted OS, deleted my app icons, Fn hotkeys, and OSD

    in Windows 10 Software and Apps
    Windows 11 Update corrupted OS, deleted my app icons, Fn hotkeys, and OSD: My computer which I've only had for like 6 months was forced into downloading/installing the latest Windows 11 update. After the computer restarted, all of my non-Microsoft app icons had disappeared. A quick online search suggested restoring to a previous save point. I...
  4. Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...

    in Windows 10 Gaming
    Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...: My computer was in the pawn shop from November 11, 2023 and I just got it back around April 12, 2024. After getting my PC back I noticed I was not able to update windows anymore and kept receiving an error of 0x800703f1. After doing some research nothing I came across was...
  5. Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...

    in Windows 10 Software and Apps
    Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...: My computer was in the pawn shop from November 11, 2023 and I just got it back around April 12, 2024. After getting my PC back I noticed I was not able to update windows anymore and kept receiving an error of 0x800703f1. After doing some research nothing I came across was...
  6. Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...

    in Windows 10 BSOD Crashes and Debugging
    Windows won't update, severe corruption. SFC Scan won't work, DISM won't work, factory...: My computer was in the pawn shop from November 11, 2023 and I just got it back around April 12, 2024. After getting my PC back I noticed I was not able to update windows anymore and kept receiving an error of 0x800703f1. After doing some research nothing I came across was...
  7. Why Did Update KB5036980 of 4/24/24 totally corrupted my dual-drive computer?

    in Windows 10 Gaming
    Why Did Update KB5036980 of 4/24/24 totally corrupted my dual-drive computer?: This update was labeled as "2024-04 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems KB5036980." One would think that since it specifically "Update Preview" users would see some of the new features of what the actual update would provide, when...
  8. Why Did Update KB5036980 of 4/24/24 totally corrupted my dual-drive computer?

    in Windows 10 Software and Apps
    Why Did Update KB5036980 of 4/24/24 totally corrupted my dual-drive computer?: This update was labeled as "2024-04 Cumulative Update Preview for Windows 11 Version 23H2 for x64-based Systems KB5036980." One would think that since it specifically "Update Preview" users would see some of the new features of what the actual update would provide, when...
  9. I cannot install new Windows updates, and my registry database is corrupted. Does anyone...

    in Windows 10 Gaming
    I cannot install new Windows updates, and my registry database is corrupted. Does anyone...: Hi,A few weeks ago I realised that my computer Windows 11 could not install new windows updates. It returns error 0x800703f1 every time. To troubleshoot this, I have:ran DISM /Online /Cleanup-Image /CheckHealthran DISM /Online /Cleanup-Image /ScanHealthran DISM /Online...
  10. I cannot install new Windows updates, and my registry database is corrupted. Does anyone...

    in Windows 10 Software and Apps
    I cannot install new Windows updates, and my registry database is corrupted. Does anyone...: Hi,A few weeks ago I realised that my computer Windows 11 could not install new windows updates. It returns error 0x800703f1 every time. To troubleshoot this, I have:ran DISM /Online /Cleanup-Image /CheckHealthran DISM /Online /Cleanup-Image /ScanHealthran DISM /Online...