Queue Servicing Report Error - Windows Update KB953297

A recent Microsoft Windows Update to .Net Framework 1.1 can cause an error message on start-up of your machine. The error is caused by a failed update installation to the Framework package - the concerned Windows Udpate is KB953297. A simple search on Google for this Update will show you it's effecting a lot of users.

The fact that Microsoft hasn't released a fix for this is a pain, but thankfully you can fix this issue yourself easily.

- Firstly, download DotNetFX for .NET Framework 1.1 to a newly created folder, for example C:DotNetFX
- Install/Extract this file to the same folder.
- Now manually download the Windows Update update KB953297 and save it in the same folder, in this case, C:DotNetFX
- Simply install the downloaded update, which is named NDP1.1sp1-KB953297-X86.exe

If it comes up with an error message, use Browse and browse to the C:DotNetFX folder that you created

That's it, you're all done.

Microsoft Outlook 2003 - Error 54. Unable to print email due to 'runtime error'

Having problems printing an email in Microsoft Outlook 2003? Getting an error and nothing being sent to your printer?

If you get an error message stating something similar to "A Runtime Error has occurred" with a title of Error 54. Clicking OK you get a message asking if you either if you "Wish to Debug?" or if you "want to continue running scripts on the page". Clicking Yes does nothing.

There are two ways to get your email to print;

1) Click "Format" in the email window and choose "Plain Text" instead of "HTML". Please note this option isn't always available and your email will look a bit different.

2) The fix: Go to your Start menu, click Run and enter the following line and then Enter - Regsvr32.exe %Windir%System32Ole32.dll

You'll get a confirmation message. Close down Outlook and all programs on your computer and restart the machine. After Windows has rebooted try printing your email again and problem solved.

Dell Security Device and Task Status encountered an error or problem

"Dell Security Device and Task Status has encountered a problem and needs to close"

Had this error come up after loading up a brand new Dell E4300 laptop up for the second time. Choosing "Send Error Report" or "Don't Send" didn't help as it just kept popping up.

Nothing showed up on Google, so I tried to look further into it myself. Not being able to make sense of any of the error report, I decided to take a guess and uninstall the "Dell Security Device Manager" in "Add/Remove Programs" ("Programs & Features" in Vista). Make sure that you don't have "Secure Logon" enabled though - you'll get a message mentioning this before uninstalling the application anyway. Basically if this feature is enabled and you remove the software, you could prevent yourself from being able to use the laptop at all!

You can check yourself by opening the "Dell ControlPoint Connection Manager" then going to "Security" and "Security Manager" and then making sure "Secure Logon" is unticked.

After removing the software, reboot your computer and the error should be gone. No thanks to Dell.

Intel Wireless Software "Device Ownership"

I was recently setting up a wireless connection on a laptop after blatting it and reinstalling the OS. I was asked to install the Intel Wireless Utility to use that for managing the wireless connections, if I had it my way I would of just used the Windows configuration utility, far simpler and uses less resources.

So after installing the Intel software, I tried connecting the laptop to the designated wireless network. However rather than being asked for a network key, it asked me for a 'Device Ownership Password'. It seems Intel are trying to make things more secure for you and your network but if you ask me this is just a major annoyance. To get round this you need to go into Control Panel, then Add/Remove Programs (Programs & Features in Windows Vista). Find the 'Intel PROSet Wireless' software and click 'Change' and then when the window opens, 'Modify'. Remove 'Intel WiFi Protected Setup' from the list of installed components and click 'Next'.

After this the problem should have gone away, might be worth restarting the computer to ensure the changes have come into effect.