News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Windows 10 2004 KB4565503 Errtor 0x8007000E

    Posted on bsfinkel Comment on the AskWoody Lounge

    Home Forums AskWoody support Windows Windows 10 Questions: Win10 Windows 10 2004 KB4565503 Errtor 0x8007000E

    Viewing 4 reply threads
    • Author
      • #2286346 Reply
        AskWoody Lounger

        Windows 10 decided to auto-install patches this afternoon on my 2004 system.  I saw a message to reboot or let Windows reboot after hours.  I was doing something with Acrobat Reader when the screen went blank, and there was lots of I/O activity (per the LED on the computer front panel).  Finally, after 25 minutes of waiting, I hit the reset button (at 14:30).  Windows started doing its updates during the reset and then auto-rebooted.  That reboot got hung on my I:-drive (CD-ROM).  About 1 in 15 reboots gets hung on this drive.  So, I hit the reset button.  Windows update finished its updates, and booted fine.  When I checked the Event Log, I saw that the .NET update KB4565627 had installed fine, but the Win 1o cum update KB4565503 failed with error code 0x8007000E (at 13:32 per the EventLog) .  I ran “sfc /scannow”, and it reported “Windows Resource Protection did not find any integrity violations”.  What does this error code signify, and how do I correct the underlying problem?  Thanks.

      • #2286347 Reply
        AskWoody MVP

        Have you tried to run the Windows Update troubleshooter and follow the suggestions offered?
        This may lead to renaming the SoftwareDistribution folder but see what happens with the troubleshooter first.

        Win8.1 Pro x64 + Linux Hybrids x86/x64 + Win7 Pro x86/64 O/L
      • #2286410 Reply
        AskWoody Lounger

        I did not try any fix-up other than the “sfc /scannow”.  After dinner (and the PBS “News Hour”) I saw another “reboot now or later” message.  I rebooted, and the KB4565503 was installed without error.  I wish that MS would document ALL of the error codes that their software generates so that the end-user would not have to hunt to get help on fixing whatever problem there was.  When I started working with IBM mainframes in 1967, there was a “Messages and Codes” manual that IBM published that had all of the operating system messages and codes.  Each message and error code was documented, so the user knew what to do to fix the error.  In those days, computer memory was expensive, so the operating system and other programs had to produce error codes instead of long descriptions of the errors.  Not so today.

        I have no idea why the first attempt at installation of this patch failed or why the second attempt succeeded without my intervention to correct anything.


      • #2286414 Reply
        AskWoody Plus

        I see your problem is resolved, but thesesteps may help next time.

        From the cmd prompt as administrator, try:

        • DISM.exe /Online /Cleanup-image /Restorehealth

        followed by:

        • sfc /scannow

        Consider a reboot, and run Windows Update again.

        G{ot backup} TestBeta
        offline▸ Win10Pro 1909.18363.959 x64 i3-3220 RAM8GB HDD Firefox79.0 WindowsDefender
        online▸ Win10Pro 1909.18363.1082 x64 i5-9400 RAM16GB HDD Firefox81.0 WindowsDefender
        • This reply was modified 1 month, 2 weeks ago by geekdom.
      • #2286516 Reply
        AskWoody Lounger

        It could be that the reboot I did (after the .NET cum maintenance) cleared the problem, which then allowed the Win 10 cum patch to install.

        1 user thanked author for this post.
    Viewing 4 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Windows 10 2004 KB4565503 Errtor 0x8007000E

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.