Friday, June 27, 2008

Windows Update error 0x80004002

Below is from an email from Microsoft on how to fix a Windows Update error.




After checking the Windows Update log which was uploaded automatically when submitting the case, I found that error 0x80004002 was received.


This error is most likely caused by one of the following conditions:


1. Update Agent 3.0 is not installed properly.

2. Some DLL files are corrupted.

3. Installer 3.1 is corrupted.



We can perform the following steps to get the issue resolved. After trying each suggestion, please go to the Windows Update site to check the issue. Thanks for your cooperation.


NOTE: Some third party programs can also affect the Windows Update service. If you are running any third party applications such as Spyblocker, Internet or web accelerators (programs designed to boost the speed of the Internet connection), security or anti-virus programs (Norton, McAfee, etc.), I recommend we temporarily disable or shut them down and then try accessing the Windows Update site later. Please be sure to re-enable them after completing the update process.


Suggestion 1: Reinstall Windows Update Agent 3.0


1. Please download the file from the following link:

If the link is not valid, please copy it to the browser address bar.


2. Save the file to C: drive.
3. Click Start->Run, copy
C:\WindowsUpdateAgent30-x86.exe /wuforce and then press Enter to install the Windows Update engine.



Suggestion 2: Register DLL files


By trying this step, we can check the update engines.


1. Close all instances of Internet Explorer.

2. Click "Start" and "Run", type "REGSVR32 ATL.DLL" (without quotations) in the open box and click "OK".


Note: There is a space between REGSVR32 and ATL.DLL


3. Register the files listed below:














Note: Please register all the files. While registering each .DLL file you should get a "succeeded" message. If any error message is encountered , please let me know the exact wording.



If it still does not work, please proceed to suggestion 3 to reinstall Windows Installer 3.1.


Suggestion 3: Reinstall Windows Installer 3.1

1. Press Start and choose Run.

2. Type in "cmd" (without quotation marks) and press OK.

3. In the command line, type in the following command and press Enter:
MSIexec /unregister

4. Then, type in the following command and press Enter:
MSIexec /regserver


After finishing the above steps, please check the result again. If the issue persists, please click Start, click Control Panel, and click Add/Remove Programs to check if Windows Installer 3.1 has been installed. If it has, please highlight and remove it. After that, please reinstall Windows Installer 3.1 from the following link.


Windows Installer 3.1 Redistributable (v2)

If the link is not valid, please copy it to the browser address bar.


Please test the issue again via the Windows Update website and let me know the result. If the issue persists, to clarify the issue and provide more accurate troubleshooting steps, please assist me in collecting the following information.


How to collect the Windows Update log file
Note: Since there are two Windows Update log files with similar names, please be aware that I am requesting the "WindowsUpdate.log" file without a space in the middle of the name.


1.    Click on Start, Run and type "WindowsUpdate.log" (without the quotes)
2. Click on the OK button. We will see a file named "WindowsUpdate.log"
3. Now click on the "File" menu and then click on the "Save As" and select "Desktop" in the "Save in" option on the top of the window.
4. Click on the Save button. The file will be saved to your Desktop.




A couple other ways I have found to fix a Windows Update error is to:

Resolution 1

1.       Stop the Windows Update and BITS Services

2.       Delete or rename the SoftwareDistribution folder under C:\Windows

3.       Restart the Windows Update and BITS Services

4.       Try to run the Windows Updates

Resolution 2

1.       If you are running Microsoft Updates and getting errors go to

a.       Click on Downloads then Office Update

2.       Install all the Office Updates from the Office website

3.       Run the Microsoft Updates again


Daniel Rodriguez

Tuesday, June 24, 2008

Microsoft SharedView

Who needs GoToMeeting?


Microsoft SharedView lets you get together with up to 15 people and share the desktop of the meeting host simultaneously, just as if you were looking at the same desktop. Your first thought may be that if 15 people had simultaneous control over the same desktop, absolutely nothing but chaos would ensue, but what really happens is that control of the desktop can be passed from one member to another.

While you're the one who's in control, you can see your collaborators' mouse movements (everyone gets a personalized pointer), so they can point out items on a document or application. Unfortunately, SharedView doesn't have integrated audio capabilities, but you can use Windows Live™ Messenger's audio client or your favorite Voice over IP (VoIP) client to conference while you share the desktop.


It is very simple to use as well.  You can send an invite via email.  With that link the user can click on a link to download and join the session.


Definitely worth trying!


Monday, June 23, 2008

Sender Policy Framework (SPF) information


This site will explain what Sender Policy Framework is and how to create text files.


Wednesday, June 18, 2008

Jing Project

The Jing Project is a free application that allows you to record a video of what you do on your desktop or take a screen cap and share it.  It will create a SWF file if you record video.  You can also get a free account to post and share your images and video.  You can do sections of your desktop applications or the entire desktop.  It records audio as well.


The video recording is similar to what you can do with Macromedia (Adobe) Captivate.


At you can also install their Desktop Uploader for quick uploads of your files to share.


Daniel Rodriguez

Wednesday, June 11, 2008

Microsoft patch may stop communication with VM's on host server/PC

Security Update KB942830 when installed on a Windows XP Pro PC stopped the network communication with the Virtual Machines within the box.  The NIC inside the VM would show disconnected even though everything looked fine.


I uninstalled the security update, restarted the PC and the VM was back to normal.


This patch was automatically installed from a WSUS server which means if you have automatic updates setup on your computer, it should install it.


It does not appear to affect Server 2003 with VM’s.  This patch is installed a on at least one Server 2003 server that I know of and the VM’s still communicate fine.


More information from Microsoft at:


Daniel Rodriguez

Open, Search, Export your NK2 file

NK2 Info


Daniel Rodriguez

Tuesday, June 3, 2008

Exchange 2007 - Enable Legacy Mailbox in Backup Exec 12

From: []

The key to enable Exchange 2007 Legacy Mailbox:

Location : HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\ESE

Create Dword:  E2K7_MBOX

Hex Value:  1

Recycle BE services

Tools => BE services => Restart All Services


When backing up the individual mailboxes use GRT backup.

To disk is fastest for backup and restore.  Leave at least 2 copes on disk if there is enough space for it.

You can also create a job to disk and then an automatic to tape job.


ONLY do the following if you want to backup using the older MAPI type backup which is very slow:

Go to Tools => Options => Microsoft Exchange => Check the box which states Legacy Mailbox [Not recommended] => Click Ok