Windows Updates Fails with Error 0x8024d007

I was trying to run Windows Update on one of my Windows 2003 Server and encountered the 0x8024d007 error. There are numerous posts available online with this error message and multiple solutions provided to solve the issue as well. The description of the issue is as below.

When you run Windows Update from the start menu, you would get a message suggesting you to download and install the latest version of the Windows Updating software. When you click on the “Update Windows” button on this web page it would start to download and install the software and the counter will run till 100 % and fail with [Error number: 0x8024D007].

The C:\Windows\WindowsUpdate.log file would register the following error messages.

WU client version 7.4.7600.226

WARNING: Exit code = 0x8024D007

FATAL: InstallUpdatedBinaries failed with error 0x8024d007

FATAL: UpdateClientWorker failed: error 0x8024d007

I will list down the steps which I have followed based on inputs from various posts online. Depending on your case either one or a combination of multiple steps might help solve your problem.

Solution 1: Manually install the Windows Update Agent from the Microsoft Site. Once you have download the executable please run it with the /wuforce switch to force it to install over an existing version of the Update Agent. (windowsupdateagent30-x86.exe /wuforce).

Solution 2: Re-register the following DLL files. You could put all the lines below into a batch file and run it in one go.

REGSVR32 WUPS2.DLL /S

REGSVR32 WUPS.DLL /S

REGSVR32 WUAUENG.DLL /S

REGSVR32 WUAPI.DLL /S

REGSVR32 MUCLTUI.DLL /S

REGSVR32 WUCLTUI.DLL /S

REGSVR32 WUWEB.DLL /S

REGSVR32 MUWEB.DLL /S

REGSVR32 QMGR.DLL /S

REGSVR32 QMGRPRXY.DLL /S

Solution 3: Renaming the SoftwareDistribution folder under %windir% folder. Please note that this can only be done when the Automatic Update Service is not running. You could run the commands below or do it thru the Services.msc console and the Windows explorer interface.

Net stop wuauserv

Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Net start wuauserv

Solution 4: Giving permission on certain registry keys.

Give Full Control to System and Administrators Group to wuauserv under this key.

KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wuauserv

Give Full Control to System and Administrators Group to Svchost under this key.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Svchost

Solution 5:

None of the steps mentioned above solved the issue in my case and finally I decided to apply the setup security template to the server to reset all the rights and permissions. I am glad I did. As soon as the settings were applied the windows update went and fetched a list of updates which were to be installed on the server.

Applying the Setup Security can again be done thru the MMC console or the CLI. The steps are available here for your reference.

You can also do the above using the secedit command line utility. Syntax and expamples are available here.

Once the baseline security is applied, the windows update happily started downloading the windows update from the MS site.

Reason 442 :Failed to enable Virtual Adapter

I have the Cisco VPN Client Version 5.0.03.0390 installed on fresh vanilla installation of Windows 8.

The VPN connection fails to get established and the client throws an error complaining that it was unable to enable the Virtual Adapter because it could not open the device. The log window of the client registers the error below :-

Sev=Warning/3 CVPND/0xE340000C. The Client was unable to enable the Virtual Adapter because it could not open the device.

In the network and connections page, there is a "Local Area Connection" entry with "Cisco Systems VPN Adapter" registered as the hardware adapter. 

Now it seems that the DisplayName string attribute in the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\CVirtA" location of the registry has to match the adapter name. However this value had some extra character in it (screenshot below). Once these extra characters are deleted and the value is just "Cisco Systems VPN Adapter" and "Cisco Systems VPN Adapter for 64-bit Windows" for 64 bit editions of Windows 8, the VPN connection just works fine. 

Lost access to secondary partition after Windows 8 Install ... for a few minutes.

I had to re install Windows 8 on my laptop due to some issues with the OS. I had two partitions on the local disk. So I copied all my data and installation source directories on to the secondary partition (E:) and did a fresh install of Windows 8 on to the C: Drive.

After the computer rebooted post installation, I could see both the drive letters C: and E: as they existed before the install. I clicked on the E: drive to get my software source folder and… I hear the loud Windows critical error sound effect, and a red cross with a message on the screen telling me that the drive "E:\ is not accessible" and "Access is denied".  Checked the properties of the drive and it said Zero bytes used. PANIC PANIC...I thought for a moment that I had lost all the data.

Luckily enough when I clicked on the security tab it said that I don’t have permission to view the properties of the object. Ray of Hope…. Clicked on Advanced and now it complained about being unable to display the current Owner. I took ownership of the drive and assigned my current logged in user account full access, ok, ok apply. Eureka..there was the familiar message on the drive icon, 90 GB used of 150 GB.

I believe the reason is that the local user account created immediately after install …the one which I used for logging in isn't part of the local administrators group. The ACL for the drive only has the SID for the local administrators group and hence windows refused to give access or even let me enumerate the drive contents.

If you do come across this issue please note that giving access to the local administrators group wouldn't give the newly created user access to the drive as by default it’s not part of the local administrators group. You will have to either add the current logged in user to the ACL of the Drive or add yourself to the administrators group and then log off and log back in to access the drive.

You might get an error about the recycle bin on the secondary drive being corrupted. You can just empty the bin and if required deleted the folder from the root of the drive.