Windows Update Error 80244019

Question

Ever since I installed a batch of Windows updates (all security updates with the exception of .Net Framework 4.6.1) on Feb 9th, I have randomly been getting error code 80244019 when trying to search for new updates. There seems to be no pattern to it and sometimes just waiting a few minutes will put everything back to normal. Running System file checker tells me that there were corrupted files and that it either repaired them or couldn't, but even when it says it repaired them it still shows errors on the next scan. The CBS log repeatedly shows the following:

CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

CBS    Session: 30500148_3265737509 initialized by client WindowsUpdateAgent.

I have uninstalled .Net Framework and replaced both the SoftwareDistribution and Catroot2 folders, I've also run full system virus scans with two different anti-virus programs, both coming up negative. I'm not really sure where to go from here, any advice would be appreciated.

Thanks

Windows 7 Pro, SP1

Answer 1

Select Start, All Programs, Accessories, right click Command Prompt, and click Run as administrator from the drop down menu. Type or copy and paste: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" and press the ENTER key. You will find an sfcdetails.txt file on your Desktop.

Please note there are three spaces in the command: Between findstr and /c, Between [SR]"and%windirBetween CBS.log and >"%userprofile

Please upload a copy of your sfcdetails.txt file to your OneDrive as a shared file and post a link here. Enter sfcdetails.txt in the Search box above the Start button and press the ENTER key to locate the file created.

Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.

Answer 2

Hi,

Sorry if there was a misunderstanding. There is nothing being logged in Event Viewer, even the original problem was not logged there. I was just hoping to get some information on the "aeinv.mof" file located at C:\Windows\system32\wbem. Whenever I run sfc /scannow it always points to that file as corrupted, it seems that I need to somehow repair it but I have no idea what it pertains to.

Thanks

Answer 3

Please provide more information to enable your problem to be diagnosed.

Please restart your computer and allow 20 minutes for the system to run before uploading information. When examining Event Viewer log files many, not all, problems show in the period immediately after the computer has been booted.

Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. Reports in normal mode preferred. Please say if the report has been obtained in safe mode. If the report is in a language other than English, please state the language.

Please upload and share with everyone a fresh copy of your System log from your Event Viewer to your One Drive and post a link here. It helps to avoid confusion if you remove any earlier copies of the log files from your OneDrive.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do not clear logs whilst you have a continuing problem.

For help with OneDrive see paragraph 9.3:

http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

Answer 4

Hello Gerry,

Thanks for the quick response, the links you provided me gave me some ideas but did not directly address my issue. However, after fiddling around for a bit the situation seems to have changed. I remembered that Intel Rapid Storage Technology sometimes doesn't play nice with Windows Update, and that it also uses .Net Framework. So I uninstalled Intel RST, then reinstalled .Net Framework 4.6.1 and RST in that order. I'm no longer getting any errors when using Windows Update, but System File Checker is giving me a different error now. Rather than the "Failed to internally open package" that pointed to the Windows Update client, it's now repeatedly giving me:

"Repairing corrupted file [ml:58{29},l:56{28}]"??\C:\Windows\system32\wbem"[l:18{9}]"aeinv.mof" from store"

It says that it has been successfully repaired, yet I get that same message in the CBS log every time I run sfc /Scannow. And, sure enough, if I navigate to C:\Windows\system32\wbem "aeinv.mof is the only one that has been modified recently.

I know that this has taken a bit of a left turn from my original question, but I'd appreciate any insight on what this file is and how to fix it for good.

Thanks again.

Answer 5

Windows Update error code 0x80244019

Solution:

How to solve connection problems concerning Windows Update or Microsoft Update

https://support.microsoft.com/en-us/kb/818018

Windows Update Error Codes

http://answers.microsoft.com/en-us/windows/wiki/windows\_7-update/windows-update-error-codes/bd72b821-05bf-4efd-bea1-b0be08fffe54